A waterproofing contractor applies systems that keep water out of terraces, basements, wet areas, tanks, podiums and retaining structures, usually as a specialist subcontractor and sometimes directly for owners and societies. Contract values are small relative to the projects they sit inside. The obligation attached to them is not. With Pentoggle, a waterproofing business can describe its systems, coverage criteria and warranty exposure and generate the starting application around them.
Two features shape the whole operation. The product being sold is a guarantee that outlives the project team by years. And its performance can be affected by conditions created by other trades, both before the work and after it.
Warranty periods, manufacturer requirements, applicator conditions and test protocols differ by system, specification and supplier, so build around what your own contracts and material warranties actually require.
Key takeaways
- The contract is short and the liability is long, which makes the record more valuable than in almost any other trade.
- Waterproofing performance can be affected by substrate condition before application and by damage or subsequent work after application, much of which may be outside the waterproofing contractor's control.
- Coverage rate, meaning material consumed per square metre treated, is both the main quality control and the main piece of evidence.
- A leak callback is a diagnosis problem before it is a repair problem, and attending without diagnosing is how contractors absorb other people's defects.
- A useful number is actual coverage rate against specified coverage rate, by application and by crew.
You are selling a ten year promise on a two week job
This is the structural fact of the business.
A terrace is treated in a fortnight. The bill is raised, retention is deducted, and the crew moves to the next project. The guarantee then runs for years, during which a single leak brings you back at your own cost, with a client who has forgotten everything except that you did the waterproofing.
Several consequences follow and they are all about time.
The people who did the work will not be available when the claim arrives. The supervisor may have left the company. The client's engineer certainly has. Whatever was agreed verbally about the substrate, about the slope, or about who would protect the membrane is gone.
Retention and any guarantee held against the warranty period sit outstanding for years, and for a business with small contract values and many jobs, the aggregate of those amounts is a substantial receivable that nobody is tracking. The RA billing guide covers the mechanics of holding retention as a tracked item with a release date, which for this trade is not a refinement but a core requirement.
And the only thing that will decide a warranty dispute in your favour is the record made at the time. Not the argument you make later, which will be correct and unpersuasive, but the photograph, the acceptance signature and the test result created before anybody had a reason to disagree.
Much of what affects your work is somebody else's
Waterproofing is applied to a surface prepared by others and then covered by work done by others. Both ends are largely outside your control and both can affect how the system performs.
Before application, the substrate has to be right. Honeycombing, laitance, dampness, cracks, wrong slope, standing water, projecting reinforcement, unsealed penetrations. Applying over a defective substrate produces a system that fails, and the failure looks exactly like bad waterproofing.
After application, the membrane has to survive. A protection screed laid by the civil contractor. Plumbers drilling. Scaffolding. Reinforcement being dragged. Foot traffic. Storage of material on a treated terrace. Any of these can breach a membrane that was applied correctly, and the breach is invisible once covered.
The commercial position this creates is uncomfortable. You are the last name attached to the function, so a leak is yours by default, and disproving it requires evidence you either created at the time or did not.
That is why the two acceptance records are the actual product of a well run waterproofing business. A substrate acceptance before application, with photographs, the condition noted and ideally a signature from the main contractor. And a handover after application and testing, recording that the system was intact and complete when responsibility passed to whoever was laying protection over it. Each takes a few minutes on site. Together they convert every future dispute from an argument into a document.
Most waterproofing contractors know this and do it inconsistently, because it depends on a supervisor doing paperwork on a day when the crew is waiting to start. A form on a phone with photographs attached removes most of that friction.
Coverage rate is your quality control and your evidence
For many waterproofing systems, the project specification or manufacturer requirements define application criteria such as material consumption, coating thickness, number of coats or coverage. Where such criteria apply, they are not advisory. They are typically what the performance of the system, and any material manufacturer's warranty attached to it, depend on.
Applying less than the specified requirement can create a significant performance risk, and it is rarely deliberate. Material is spread further than it should be because the area was larger than estimated, because the substrate absorbed more than expected, or because a crew was working to finish a terrace before rain. The result looks complete and performs badly, and it will not be apparent for a season or two.
Recording what was actually applied makes it visible immediately. Material consumed against area treated, or coats and thickness achieved, computed per application and compared against what the system requires. A crew consistently falling short of the specified criteria is a problem that can be corrected this week rather than discovered in a monsoon.
The same record does double duty as evidence. Where a manufacturer's warranty is conditional on application meeting specified criteria, being able to show what was achieved on a particular area on a particular date is what keeps that warranty available to you when you need it. A contractor who can produce coverage records is in a far stronger position with both the client and the material supplier than one relying on the assertion that the work was done properly.
Recording it requires area treated and material consumed to be captured together at application, which is one entry rather than two records reconciled later.
Testing is the moment your work becomes provable
Where the specification calls for it, ponding or flood testing after application and before protection is laid is the point at which a system demonstrates that it works. Which validation applies, what it involves and for how long depends on the system and the specification, and some systems and applications are verified by other means.
Operationally, this is a narrow window and it is frequently compressed, because holding water on a terrace for a day or two delays the trades waiting to follow. Pressure to shorten or skip it is routine and it comes from the programme rather than from anybody's bad intent.
Where a test is required, two things are worth protecting. The test happening at all, and the test being evidenced. A dated record with photographs of the area under water, the duration, the result and preferably the main contractor's or consultant's presence is one of the strongest documents this business can hold. It provides evidence of the system's condition and the test result at a specific point in time, which is what allows any later failure to be discussed against a known starting position.
Where a test is waived or shortened at somebody's request, that too is worth recording at the time, with who asked. It is an awkward record to make and it is exactly the record that matters three years later.
A callback is a diagnosis problem first
A leak is reported during the warranty period. The instinct is to send a crew and fix it, because responsiveness protects the relationship.
The risk in that instinct is that a good proportion of reported leaks are not waterproofing failures. Plumbing leaks, structural cracks, condensation, failed sealant at joinery, drainage blocked and overflowing, and water entering through a source nobody has looked at. Attending and repairing without establishing the cause means absorbing the cost of other people's defects, repeatedly, for years, on a contract that was priced with none of that in it.
The discipline is to diagnose before repairing and to record the diagnosis either way. Where the cause was yours, that is a defect and the record helps identify whether it is a pattern in a system, a crew or a site. Where the cause was not yours, the record is what allows you to say so, and to charge for attendance if the contract permits.
Over a few years this accumulates into something valuable: which systems fail, on what kind of structure, how long after application, and how often the reported cause was not the actual cause. That is the information that should be setting your prices and your warranty terms, and almost no waterproofing contractor has it, because each callback is handled and forgotten.
The workflows a waterproofing contractor runs
- Measurement and Quantity Tracking, on area treated, with the added feature that the treated area is also the area under warranty.
- RA Billing and Retention, where retention is held for unusually long periods relative to contract value.
- Construction Material Management, where consumption against area is a quality control rather than only a cost control.
- Construction Quality and Inspection, covering substrate acceptance, testing and handover.
- Subcontractor Management, seen from the position of the firm being engaged.
Why waterproofing contractors choose Pentoggle
Substrate acceptance before you start
Photographs, condition and signature captured on a phone, which is what a later dispute is most likely to turn on.
Coverage rate per application
Material consumed against area treated, computed as the work happens rather than months later.
Test records that prove a moment
Dated ponding and flood test evidence held against the specific area it covers.
Warranty and retention by job
What is held, when it releases, and which jobs are still inside their guarantee period.
Callback history that teaches you something
Diagnosis and outcome recorded per callback, building into a picture of what actually fails.
A useful number for a waterproofing business
What was actually applied against what the specification requires, by application and by crew.
For systems specified by consumption this is material used per square metre. For others it may be thickness, coats or another criterion. Whichever applies, it is unusual in being simultaneously a quality measure, a cost measure and a defence, because it tells you whether the system was applied as specified, whether material is being lost or spread thin, and whether any warranty conditions were met.
Read it by crew as well as by job. Coverage is a habit and it varies between teams more than between sites, so a crew running consistently light is a training conversation rather than a site problem.
Read it before the job is handed over, not at month end. The value of catching a shortfall is that the area can be reworked while access exists and nothing has been laid over it. A week later it is a warranty exposure instead of a correction.
The number needs the area treated and what was applied to it captured in the same entry at application. Where they are recorded separately, in a measurement sheet and a stores register, the comparison rarely happens at all.
Ready to build software for your waterproofing business?
You will be asked to prove your work was sound long after everyone who watched it has gone.