Field and customer operations
Construction deficiency tracker: from observation to verified closure
Track every deficiency from the moment someone notices it to the moment someone else confirms it is fixed, with a template you can use today.
For: Contractors, site supervisors, warranty and customer-service staff who manage deficiency lists on residential or commercial work.
- Format
- Process guide + editable tracker (CSV)
- Published
- September 9, 2026
- Last checked
- September 9, 2026
- Written by
- Dryvn AI editorial
- Edited by
- Dryvn AI editorial
- Reviewed by
- Not yet reviewed by a named person
- Read as
- Editorial (Dryvn's practical method)
Why deficiency lists fail
Anyone who has run a residential project knows the shape of the problem. A homeowner walks through with a clipboard and finds twenty things. A trade comes back, fixes twelve, says all twenty are done. Three weeks later the homeowner emails about the eight that were never touched, plus two of the twelve that were touched badly. Now nobody trusts the list, the trade is annoyed, and the site supervisor spends a Saturday re-inspecting everything.
The list did not fail because people were lazy. It failed because it only had two states: open and done. A deficiency needs more than that. It needs to hold the difference between "someone saw it", "we agree it is ours to fix", "the trade says it is fixed" and "we checked and it is fixed". Those are four different facts, held by four different people, on four different dates.
Public punch-list templates, such as Procore's, capture item, responsibility and completion [S09]. That is the right starting point. What this guide adds is the process around the template: who moves an item between states, what evidence each move needs, and what happens when the normal path breaks.
The four states, plus one
Text version of this diagram
- Observed (start; someone noticed it) → go to In our scope?
- In our scope? (decision; confirm responsibility) → yes: go to Accepted; no / unclear: go to Disputed
- Accepted (step; owner, due date) → go to Corrected
- Corrected (step; trade says fixed (claim)) → go to Verified?
- Disputed (escalation to a person; owner decides with the customer) → agreed ours: go to Accepted
- Reopened (step; back to the trade) → retry: go to Corrected
- Verified? (decision; someone checked) → pass: go to Closed; fail: go to Reopened
- Closed (end; evidence attached)
| State | What is true | Who moves it there | What is recorded |
|---|---|---|---|
| Observed | Someone saw something and wrote it down. Nothing else is settled. | Anyone: homeowner, inspector, crew, office. | Observation date, description, location, evidence reference. |
| Accepted into scope | The business has agreed this is a deficiency it will correct, and has named an owner. | The person with authority to accept work, usually the site supervisor or project manager. | Assigned owner, category/trade, priority basis, due date. |
| Corrected | The trade or crew claims the work is done. | The assigned owner or the trade. | Completion claim with date and, ideally, a photo. |
| Verified closed | Someone other than the person who did the work looked at it and confirmed it. | Supervisor, inspector or customer, depending on the item. | Verification outcome, verification date, closed date. |
| Reopened | Verification found the correction incomplete or wrong. | Whoever verified. | Reopened flag, what was found, new next action. |
The fifteen fields
Here is the full set. If a field feels like overhead, look at the failure it prevents before you drop it.
| Field | What goes in it | Failure it prevents |
|---|---|---|
| Item ID | A unique number that never changes, e.g. D-0042. | Two people talking about different items with the same description. |
| Project / location | Generic project name plus a location inside it: unit, room, elevation. | Trades arriving at the wrong place. |
| Observation date | When it was first seen. | Losing track of how long an item has been open. |
| Description | What was observed, in plain words. Not the cause, not the fix. | Arguments about what the item actually was. |
| Category / trade | Paint, plumbing, drywall, electrical, exterior, and so on. | Sending the wrong trade. |
| Assigned owner | One named person responsible for getting it corrected. | Items that belong to everyone and therefore nobody. |
| Priority basis | Why it has the priority it has: safety, water, occupancy, cosmetic. Not just "high". | Everything being urgent, so nothing is. |
| Due date | When correction is expected. | Open-ended items. |
| Appointment / access status | Booked, confirmed, refused, no answer, keys held. | Blaming the trade for an item the homeowner would not let them in to fix. |
| Evidence reference | Photo number, file name or note reference for the observation. | Verifying against memory instead of a record. |
| Last update | Date of the most recent change to the row. | Stale rows nobody has looked at. |
| Next action | The single next thing that has to happen, and by whom. | Rows that are open but have no movement. |
| Completion claim | Date and source of the claim that it is fixed. | Treating a claim as closure. |
| Verification outcome / date | Pass or fail, who checked, when. | Closing on trust. |
| Closed date | Set only after verification passes. | Items closed by the person who did the work. |
Three fictional rows
These rows are invented to show how the fields work together. They are not from any real project.
| Item | Location | Description | Trade | Owner | Priority basis | Access | Completion claim | Verification | Status |
|---|---|---|---|---|---|---|---|---|---|
| D-0041 | Unit 2B, kitchen | Cabinet door under sink does not close; hinge loose. | Millwork | J. Site super | Cosmetic, occupied unit | Booked Tue 10:00, confirmed | Trade: fixed Tue | Pass, Wed, super | Verified closed |
| D-0042 | Unit 4A, ensuite | Water staining on ceiling below shower above. | Plumbing | J. Site super | Water, possible active leak | Refused, tenant travelling | None | None | Accepted, waiting on access |
| D-0043 | Building exterior, north stair | Handrail bracket loose at landing. | Metals | J. Site super | Safety, common area | No access needed | Trade: fixed Mon | Fail, Tue: bracket tight, second bracket now loose | Reopened |
When the normal path breaks
A tracker earns its keep on the items that do not go smoothly. Three cases come up on nearly every project.
Illustrative example · fictional
Access failure
D-0042 is a water stain in an occupied unit. The plumber is booked twice; the tenant cancels once and is away the second time. In a two-state list this item looks like a plumber who is not showing up. In the tracker, the access status says "refused, tenant travelling" with dates, and the next action is "office to contact property manager for alternate access by Friday". The item stays in accepted-into-scope. Nobody is blamed for the wrong thing, and the priority basis (water) keeps it at the top of the review.
Illustrative example · fictional
Disputed scope
A homeowner logs a scratch on a hardwood floor as a deficiency six weeks after move-in. The site supervisor is not sure whether it was there at handover. The item is recorded as observed, with the homeowner's photo as the evidence reference, and the next action is "compare against handover photos, decide by Thursday". It is not accepted into scope until someone with authority decides, and the row records who decided and on what basis. If the decision is no, the item is closed as "not accepted" with the reason, not deleted. A deleted item is an argument waiting to happen.
Illustrative example · fictional
Reopened item
D-0043 is a loose handrail bracket. The metals trade reports it fixed on Monday. On Tuesday the supervisor checks: the reported bracket is tight, but the next one along is now loose, probably from the same movement. The verification outcome is a fail with a specific note, the reopened flag is set, and the next action goes back to the trade with the new detail. The original completion claim is kept. Over time, the count of reopened items per trade tells you something no completion rate can.
How to verify closure
- 01Separate the checker from the doerWhoever corrected the item does not verify it. On a small crew that can be the supervisor, the office, or the customer.
- 02Check the description, not the claimRead what was observed, then look at that. If the trade fixed something else, the item is not closed.
- 03Record what you sawOne line and a photo reference. "Pass, hinge tight, door closes flush" is enough. "OK" is not.
- 04Close or reopen, with a dateThe closed date is set by the verifier, never by the person who did the work.
- 05Review the waiting states weeklyAnything accepted but not corrected, or corrected but not verified, gets a look every week. That is where lists go stale.
Templates
Two files: a blank tracker with the fifteen columns, and the same columns filled with the three fictional rows above so you can see how a completed row reads. Both open in any spreadsheet. The columns match the table on this page, so you can also add them to the tool you already use. The field report guide covers how to write the observation and evidence fields well, and the customer request workflow covers the same closure discipline for non-construction work.
Downloads · no email required
- Download .csv
Deficiency tracker (blank)
The fifteen columns with three empty rows, ready to fill in or paste into your own spreadsheet.
- Download .csv
Deficiency tracker (fictional sample)
The same columns with the three fictional rows from this page, showing an access failure, a verified closure and a reopened item.
Questions people ask
- What fields belong in a construction deficiency tracker?
- Item ID, project/location, observation date, description, category/trade, assigned owner, priority basis, due date, appointment/access status, evidence reference, last update, next action, completion claim, verification outcome and date, and closed date. The fields most often skipped are priority basis, access status and verification outcome, and those are the ones that stop disputes.
- How do I verify a deficiency is actually closed?
- Someone other than the person who did the work checks the item against the original description, records what they saw with a date and a photo reference, and only then sets the closed date. If it fails, the item is reopened with the new detail rather than left as done.
- Is this the same as a punch list?
- A punch list is usually a single walkthrough at a milestone. A deficiency tracker holds items from any source over the life of the project and its warranty period, with states and evidence. You can use the same fields for both.
- Does the tracker tell me whether an item is covered under warranty?
- No. It records that you accepted an item into scope and who decided. Coverage and responsibility depend on your contract and warranty terms. Get that answer from the right source and record it in the row.
Related resources
- Turn field photos and voice notes into an actionable reportGet from a pile of site photos and a rambling voice memo to a report someone can act on, using a five-step sequence and a template you can fill in on the spot.
- Customer requests: track the work until it is actually resolvedRun every customer request through the same nine stages, so nothing is marked done until the customer's problem is gone and you can show it.
- Where is work getting stuck between your tools?Find the handoffs in your business that still depend on copying information, remembering follow-ups or chasing people, and get one next action for each gap.
- BlogWhy Is AI Adoption in Construction Still So Low?Construction does not have an information shortage. It has a fit problem. Most AI tools start with writing and analysis. Trades businesses need information to survive messy field input, connect to the right job, move through approved steps and come back when the outcome is still unfinished.
Sources
Dates are when each source was last checked by the editor. Sources support specific claims; they are not endorsements.
- S09Punch List Template · Procore · checked September 9, 2026Public example of a punch-list template. Cited for category context only: it shows that item capture, responsibility and completion are standard fields. The process and template on this page are Dryvn's own.
R06 · Published September 9, 2026 · Next scheduled review December 9, 2026 · Teaches process management; not legal, warranty, safety or engineering advice. Examples are fictional unless stated. Part of the Dryvn resource library (17 resources).