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.

A Simple Framework for Setting Contingency

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.

Building that connection — every change order automatically drawing against both its budget line and the job's contingency balance, with alerts at the thresholds that matter — is what turns contingency from a mental buffer into an actual early-warning system.