Good Plan/Great Result
Stop Estimating By Feel: How to Use a Work Breakdown Structure to Run Better Pool Repair Jobs
If you've been in the pool business long enough, you've eaten the cost of a job that went sideways because conditions on site weren't what you expected. The pool was bigger than the customer said. The drain was blocked. The equipment pad wasn't accessible. The filter turned out to be a different model than what was on the work order.
You handled it — you always do — but somebody paid for it. Either the customer got a surprise on their invoice, your tech worked two unpaid hours to make it right, or the job came in under margin and nobody could explain exactly why.
This happens not because your team doesn't know how to do the work. It happens because most pool service companies estimate jobs the same way they always have: a line item for the outcome, a price based on what it cost last time, and a prayer that conditions on site look like what the estimator imagined.
There's a better way. It comes from project management, it's been standard practice in construction for decades, and it translates directly to pool repair. It's called a Work Breakdown Structure — WBS for short — and the part of it that will immediately change how you run jobs is something called the WBS Dictionary.
Here's how to build one.
What a WBS Actually Is
Forget the jargon. A WBS is just a complete list of everything a job requires, organized from top to bottom.
At the top is the project — the job itself. Below that are the phases: pre-mobilization, site preparation, the core repair work, system restoration, and closeout. Inside each phase are the specific deliverables — the things that have to exist before the phase is done. And inside each deliverable are work packages: the individual units of work that get assigned to a person, scheduled, and tracked.
The rule is simple: if it isn't in the WBS, it isn't in the job. Nobody owns it, nobody budgeted for it, and there's a reasonable chance it doesn't happen — or happens and doesn't get billed.
The Part That Actually Fixes Your Estimating Problem
The WBS on its own is just an outline. The WBS Dictionary is what makes it useful.
For every work package that has variable resource requirements — and in pool repair, that's most of them — the dictionary defines exactly what the job looks like under different site conditions. Not a best guess. Not "it depends." A defined table of conditions, resources, and expected durations that every person on your team reads the same way.
Here's what a dictionary entry looks like for one of the most common work packages in pool repair: draining the pool.
Work Package: Water Removal
What it includes: Complete removal of pool water to a level that permits safe access to the work area, including pump setup, active pumping, and pump breakdown.
What it doesn't include: Drain system inspection (that's a separate work package) and any chemical handling of the removed water.
How you know it's done: Water is at or below working depth at the deepest point of the pool. No active flow from return lines. Equipment pad is accessible and dry.
What it requires — depending on what you find:
Site Condition Pumps Crew Estimated Time Residential, ≤ 50,000 gallons, direct drain access 1 electric submersible 1 tech 45–90 minutes Commercial OR 50,000–150,000 gallons 2 pumps (electric or gas) 1 tech 2–4 hours > 150,000 gallons OR no direct drain access 3 gas pumps + discharge hose run 2 techs 6–8 hours Drain system compromised or configuration unknown Stop work — escalate to supervisor — —
What has to happen first: Site assessment complete. Discharge point confirmed. Customer notified of pump noise and site access restriction during draining.
Who owns it: Lead Repair Technician
That entry does something a line item on a quote never does. It tells the estimator which configuration to price based on what the site assessment found. It tells dispatch whether to send one person or two. It tells the tech what they're walking into and what to do if the site doesn't match any of the defined conditions.
That last part — what to do when conditions don't match — is where the dictionary connects to the other document your operation is probably missing.
When the Dictionary Connects to a Change Order
Every experienced pool tech has been in this situation: you show up, look at the job, and immediately know it's not what was quoted. Maybe the pool is twice the size described. Maybe there's no accessible drain and nobody mentioned it. Maybe the equipment that was supposed to be replaced is a non-standard configuration that requires parts you don't have on the truck.
Right now, what happens next is probably a phone call. You explain the situation, someone makes a decision, the job either gets done differently or gets rescheduled, and none of it gets documented in a way that improves the next estimate.
The dictionary fixes the first part of this by defining what "expected" means for each work package. When a tech can look at the dictionary and say "the site is a Category 3 situation and we quoted Category 1," the problem is immediately clear, immediately quantified, and immediately communicable.
The Change Order handles the second part. When field conditions fall outside any defined configuration, the process is:
Tech documents what was found — condition, photo, written description
Tech submits a Change Order identifying the revised resource requirement and cost impact
Office or supervisor authorizes the revised scope
Customer authorizes if additional charges apply
Tech proceeds and documents what was actually used at completion
That's it. No improvised decisions that nobody remembers later. No surprise line items on the invoice. No jobs that came in under margin for reasons nobody can explain.
The dictionary tells you what was expected. The Change Order documents when reality is different. Together they create a paper trail that improves your estimates every time you use them.
How to Build Your Dictionary: Start Here
You don't need to document every possible job type before this becomes useful. Start with the five jobs your team runs most often. For most commercial pool repair operations that's going to be something like:
Sand and media changes
Filter component replacement (laterals, O-rings, multiport valves)
Leak detection
Pump and equipment replacement
Renovation prep (draining, surface preparation)
For each job type, work through the phases and deliverables, identify every work package that has variable resource requirements, and write a dictionary entry using the format above.
Do this with your team — not just your estimators. The techs who do the work know things that don't show up in estimates: which filter models are harder to get into, which sites have access problems, which job types almost always turn up secondary issues. The dictionary only works if it reflects what actually happens in the field, and the people who know what actually happens in the field are the ones doing the work.
From Document to System
Once your dictionary is written and your team has validated it, something useful happens: the work packages and their conditions become the building blocks of a better dispatch and estimating system.
The condition categories become the questions on your site assessment form. The resource configurations become the inputs your dispatcher uses to schedule the right crew with the right equipment. The escalation paths become the trigger for a Change Order record rather than an informal phone call.
You don't need new software to start. The dictionary is a document. A spreadsheet works. A shared Google Doc works. What matters is that everyone — estimators, dispatchers, techs, and account managers — is reading the same definitions and using the same language.
The pool industry doesn't have a published standard for this the way construction does with MasterFormat or PMBOK. That means the companies that build their own dictionaries aren't working from a template — they're building institutional knowledge that doesn't walk out the door when a tech moves on, doesn't get lost when an estimator retires, and doesn't have to be rebuilt from scratch every time a new job type comes in the door.
That knowledge, written down and shared across your team, is what turns a good pool company into one that scales.
