Notes for owners · Industry-Specific Software Guides
How to Track Waterproofing Treatment Records and Warranties
Record the system, each coat with its date and crew, the ponding test and the handover date against every treated area. The warranty end date follows from those. GullySystem’s Waterproofing Contractor Management Software holds them together, so a callback can be checked against the original treatment.
Ganesh HS, Strategy and Technology, GullySystem · · 3 min read
What a treatment record should hold
The unit of record is the treated area, not the whole job. A single contract may cover a terrace, two bathrooms and a sump, and each can have a different system and warranty.
For each area, keep the inspection note, the system chosen and the measured square feet. Add each stage as it is finished: surface preparation, primer, coats, mesh and protection screed.
Every stage entry carries a date and the crew that did it. The record stays with the job and can be read years later.
- Inspection note and photographs
- System and coats applied
- Stage dates and crew
- Material issued against the quotation
The ponding test and the handover signature
The ponding test is the evidence that a treated area held water. Record the start time, the end time and the result.
How long the test runs is decided between you and the client, and the system stores whatever period you set. Keep the result next to the coats applied, so the two can be read together later.
The client’s signature at handover closes the record for that area. The handover date is the date the warranty starts. Without it, the end date has no firm starting point.
Warranty terms stored against each area
A warranty register lists every treated area with its system, handover date, period and what the warranty covers. Terms often differ by system, so they are stored per area and not per client.
Reminders are set from the end date. The owner sees warranties ending soon, grouped by client and area, and can decide whether to offer a renewal or an inspection visit.
Share the terms in writing with the quotation. The register then matches what the client was told.
Linking callbacks to the original treatment
A leak complaint after handover is logged against the area that was treated. The entry records the revisit, the cause found and the repair done.
The register shows whether the complaint falls inside the warranty. The owner can then decide whether the repair is chargeable.
Over time, callbacks grouped by treatment system and supervisor show where problems repeat. That report reads from stage records, so missing entries weaken it. Log the cause found on every revisit, even when the repair is minor.
Where paper registers are enough
A contractor handling a handful of jobs and giving no written warranty can keep a register in a notebook. The records matter most when warranties run for years and several supervisors work at once.
Before choosing software, decide what you promise. Fix the warranty period for each system, what it covers and what voids it. The software stores those terms but does not set them.
Book the free technology audit if you want a second opinion on whether today’s waterproofing records would answer a callback.
Treated area warranty card
A card for each treated area listing the system, coats with dates, ponding test result, handover date, warranty period and end date, and a column for callbacks. Fill ten past jobs into it to see how many callbacks you can trace.
Open a blank worksheet to printQuestions owners ask
When does a waterproofing warranty period start?
The terms are yours to set, but the usual anchor is the handover date. It is recorded with the ponding test result and the client’s signature, and the end date and reminder are worked out from it.
Can a warranty register show which callbacks are covered?
Yes. A complaint is logged against the treated area, and the register shows whether it falls inside the warranty period. Whether the repair is chargeable remains the owner’s decision, based on the terms given.