How to Track Contingency on a Pool Build Without Losing the Job
A simple framework for setting, tracking, and protecting contingency on custom pool builds before change orders and surprises eat the margin.
Contingency Exists Because Pool Jobs Are Never Perfectly Predictable
Every custom pool build carries risk that doesn't show up until the ground is opened: rock, high water table, unmarked utilities, a permit reviewer who wants a spec change, an owner who upgrades the tile mid-build. Contingency is the budget line that exists to absorb exactly those surprises without the job losing money.
The problem isn't that contingency exists — it's that most builders track it informally. It lives in someone's head, or a note on a whiteboard, or a mental buffer built into a bid. Informal tracking means nobody knows exactly how much contingency is left until it's already gone, usually right when a real problem shows up and there's nothing left to absorb it.
How much contingency should a pool builder carry?
Set Thresholds, Not Just a Total
The real value of tracking contingency isn't the total — it's knowing when to react. A useful pattern:
Without thresholds, contingency tracking becomes a lagging indicator — a number you check after the job is already in trouble, not a warning system.
Why This Has to Live With the Budget, Not Next to It
Contingency tracking only works if it's part of the same system as the job budget and the change-order log — not a separate spreadsheet someone updates when they remember. The moment contingency tracking lives apart from where POs, bills, and change orders are actually entered, it drifts out of date within a week.
Keeping change orders, the budget lines they touch, and the job's contingency balance in one place — and reviewing that balance against your thresholds at a regular cadence, such as every weekly job review — is what turns contingency from a mental buffer into an actual early-warning system.
A worked example
Example only. On an $80,000 pool, the builder carries 6% contingency, or $4,800. Excavation hits rock and costs $1,900 more than planned, leaving $2,900. During plumbing, a longer gas run adds $700, leaving $2,200.
The builder has used 54% of the contingency, and only two of six phases are done. That ratio, contingency used versus job completed, is the number to watch. Using contingency faster than the job is progressing is the early signal that margin is at risk.
What is contingency not?
Who should see the contingency line?
Some builders show contingency to the client as a line item; others keep it inside the line prices. Both work if you're consistent. If it's visible, put in the contract how unused contingency is handled at the end — returned, credited or retained — so it isn't argued about at final payment.
A monthly review that takes ten minutes
For each open job, list: budget, actual to date, percent complete, contingency remaining. Flag any job where contingency used is more than percent complete plus ten points. Review those jobs with the project manager that week, while there's still time to change something.
Where BidBuild fits
In BidBuild, contingency is a line in the job budget, so costs recorded against the job show how much is left. Reviewing it is still a person's job. Set a recurring time to look, rather than waiting to be told.