Snag and Punchlist Management: The Measurements Worth Keeping
Most facility teams can close a punchlist without ever deciding what they are measuring. Lines get ticked, photographs go into a folder, a contractor asks for a sign-off, and the estate moves on. The disagreement surfaces later — at a handover, an audit or a chargeback — when two parties read the same folder and see different things. This arena sets four approaches to snag and punchlist management measurement side by side and asks which still carry weight when a line is disputed.
Direct answer. The one-line answer — snag and punchlist management measurement is the working record for snag and punchlist management measurement. snag and punchlist management measurement is worthless until snag-and-punchlist-management is attached to it as evidence. A snag and punchlist management measurement is the operating-life view. It starts after the invoice. snag and punchlist management measurement is the first interval of snag and punchlist management measurement to measure.
- Agree the cadence — define how often snag and punchlist management measurement is inspected
- Agree the condition — name the condition that forces a change to snag-and-punchlist-management
- Watch the value — keep one metric that shows four ways is healthy
- For snag and punchlist management measurement, the order below is fixed and snag and punchlist management is the reference point.
Every measure below is one you compute from your own records. No service level, response interval or closure rate is supplied on your behalf; your plan sets the target and your file supplies the evidence. Where a specific unit, a supplier process or a local rule drives the decision, the question to ask and the evidence to demand are set out instead of an answer.
Four ways to count a closed punchlist
A punchlist is a list, so the cheapest measure is arithmetic: lines closed against lines raised. It is fast to produce and easy to misread, and estates often mix several approaches in one file without noticing which column came from where. The table sets out what each approach can be made to prove, and what it cannot. The catalogue side of this is the smart door locks.
| Approach | What it counts | What it hides |
|---|---|---|
| Item count | Lines closed against lines raised | Severity, effort, and whether the door changed |
| Elapsed time | Report raised to closure recorded | Which items waited, and the long tail |
| Evidence attached | Items closed with observation, check and signer | Doors that nobody raised an item against |
| Door outcome | Doors operable with no repeat visit for the same symptom | The reasoning behind the repair |
The first three are cheap to collect. The fourth is the one an occupant feels. Each challenge later in this article is answered by one of them.
Candidate one — closing on the item count
The count is a denominator problem before it is a numerator problem. Items get raised late by trades who were not on site at handover, the same defect can be raised twice by two different people, and an item reopened after closure disappears from a file that only counts current status. Each of those quietly moves the figure.
Severity disappears too. One line may describe a door that cannot be secured; another may describe a scuff on the escutcheon. A raw count treats them as equal, so a portfolio with two hundred cosmetic items can report a healthier punchlist than one with eight access faults. Use the count to follow direction of travel inside one building and one period. Do not use it to compare buildings, score a contractor, or sign off a close-out.
Candidate two — closing on elapsed time
Resolution time records answer a narrower question: how long from a fault being reported to the door working again. The target belongs to your service plan, and the record is the evidence that the plan was met. Two weaknesses are well known. A mean hides the tail — one door left inoperable for weeks sits inside an acceptable average. And population: a door never reported through the agreed channel never enters the calculation, so the measure flatters the estate that reports well rather than the estate that works well.
Report the distribution rather than the average, report it separately by door class, and fix the point at which the clock starts. If it starts at close-out sign-off, you have measured paperwork rather than doors.
Candidate three — closing on evidence
Evidence-based closure is slower to produce and much harder to argue with. An item counts as closed only when the file carries the door identifier from the object schedule rather than a room name, the observation made at the door, the checks run in order with what each one ruled out, the action taken, and the name of the person who accepted the closure.
The third element is the one most files omit, and its absence is why snag item evidence often looks weaker than it is. A list of actions says someone tried something. A list of exclusions says why the next option was chosen, and it separates a technician who found the cause from one who guessed, swapped a unit, and waited to see whether the fault returned.
flowchart TD
A[Item raised against a door] --> B{Observation recorded}
B -->|Yes| C[Checks written with what each ruled out]
B -->|No| D[Item stays open with a named owner]
C --> E[Photograph or reading attached]
D --> E
E --> F[Named signer accepts the closure]
F --> G{Door reopens without a repeat visit}
G -->|Yes| H[Measurement feeds the close-out file]
G -->|No| I[Item reopens against the original reference]
I --> C
That is also why evidence survives an audit months later: it can be read without the person who wrote it.
Candidate four — closing on the door outcome
Outcome measures look at the door rather than the file. A visit that ends with the door operable and no repeat visit for the same symptom is a first-time fix; the share of failures returning inside a stated window is the repeat rate. Both are computed from your own record, and both are easy to misstate.
State the population and the window before the figure, because a repeat rate without its window says nothing. First-time fix measurement is also blunt in one direction: it tells you the door worked, not why it worked. A visit that passes because a temporary workaround was applied counts the same as a visit that passes because the cause was removed. Keep the outcome number beside the evidence record and let the two disagree when they disagree.
Side-by-side: what each measure survives
A snag and punchlist management measurement earns its place by surviving a challenge.
| Challenge | Item count | Elapsed time | Evidence attached | Door outcome |
|---|---|---|---|---|
| Audit of the close-out file | Weak | Weak | Strong | Partial |
| Occupier reports the door still faults | Weak | Partial | Strong | Strong |
| Chargeback for defective work | Partial | Weak | Strong | Partial |
| Supplier asks why a unit was returned | Weak | Weak | Strong | Partial |
| Roll-up across several sites | Partial | Partial | Strong | Partial |
Read the row that matters to you before the average. The item count tracks progress, elapsed time tracks the plan, and the door outcome tracks what people experience in the building. Only the evidence record is defensible: when a line is disputed, a chargeback is raised or a supplier challenges a return, the file that answers is the one carrying the observation, the checks and the signer.
The fields that make the measurement defensible
Eight fields make the evidence record readable later. They are cheap to capture at the door while the part is still in hand, and expensive to reconstruct weeks later from memory and photographs.
| Field | What goes in it |
|---|---|
| Door identifier | Object schedule identifier and the door label as found |
| Model and variant | Read from the label, with the dated product page |
| Two timestamps | Reported, and operable again |
| Symptom and observation | Technician's words, then the measured observation |
| Checks and exclusions | Order run, and what each one ruled out |
| Parts and unit | What was fitted or swapped, old unit retained |
| Credential state | Before and after, where a credential was involved |
| Photo or reading | The image or value behind the conclusion |
Model and variant details are read from the label on the unit, and any specification relied on should be confirmed on the dated product page for the specific SKU rather than carried forward from memory. Field service record quality is mostly capture discipline: eight fields written during the visit cost minutes; the same eight rebuilt in an office cost a day and produce a weaker record.
Measurements that start before the punchlist opens
Most measurement friction in a punchlist is created earlier. The identifiers used to close items come from the object schedule, and the variant recorded against each door is what lets anyone trace a fault back to a unit. Door acceptance criteria agreed at survey are the same criteria the close-out file will be judged against, so the survey and the punchlist should share one set of values. The Office Smart Lock Site Survey and the Smart Lock Retrofit Site Survey cover that step; what matters here is that the identifier and variant written at survey are the values used on every later line.
What to ask the supplier and the contract
CONFIRM-PER-SUPPLIER: what the supplier's written support asks for before authorising a return, and what its claim route requires as evidence, is a supplier-specific process — request it in writing before the first fault, not during one.
Three questions belong in the contract schedule rather than in an email thread: what a fault record must contain for the supplier to act without a return, what the supplier needs to see before a unit is replaced, and which dated product page applies to the units in your estate. A ready-made set of clauses is in Snag and Punchlist Management: Contract Clauses that Make It Work, and the same ground is covered as a pre-purchase check in Snag and Punchlist Management Evidence to Request Before You Buy.
Running the close-out meeting in order
Close-out meetings are quick and bad when the file is read line by line. Five moves fix that.
- Start from the outcome file: doors still open, doors reopened, doors never reported.
- Walk the evidence record for every repeated or disputed item, in the order the checks were run.
- Put elapsed time beside severity class, so the long tail is visible.
- Name an owner and a signer for every line that stays open.
- Release the file only when door, record and schedule agree.
The Working Snag and Punchlist Management Without a Second Site Visit covers items that cannot be re-tested on site, and Snag and Punchlist Management When the Estate Has More Than One Site covers the roll-up question. The paperwork itself is collected in Snag and Punchlist Management Documentation Set, and the printable record form sits in A Printable Snag and Punchlist Management Record for the Site Log.
Where local rules and site practice still decide
Several things that sound like measurement are settled elsewhere: how long site records are kept, what an access log may be used for, which hours a technician may work on a secured door, and what a landlord or tenant is entitled to receive at handover. These are per-site and per-jurisdiction questions, and the answers sit with your own advisers.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL-AUTHORITY: which authority signs off on retention of site and access records for this estate, what evidence they expect, and which rules apply to the doors in scope.
Write the question down and store the answer beside the punchlist file, so that a later reader can tell whether an answer was verified or assumed.
The short list, and what to do with it
Four measures compete here, and the winner is not the one carrying the most decimal places. Keep the item count for trend, elapsed time against your own plan, the door outcome for the people who use the building, and the evidence record for everything that can be argued. That fourth one is also the cheapest, because it is eight fields written at the door while the part is still in your hand.
The practical counterpart to this point is the smart lock installation requirements. That is the same question snag and punchlist management measurement has to answer here.The next step is not a new system. Take the last punchlist file for one building, mark each line with the field it lacks, and the gaps become the punchlist for the record itself. If you want that measurement model turned into a template for your estate — the field list, the challenge grid and the sign-off column ready to copy into your own close-out pack — ask our project desk for the snag and punchlist measurement worksheet, or bring the last close-out file and we will mark the gaps with you. The same field set holds for a single site and for a multi-site estate, and it is the set a field technician will actually use.
Ask for the offer against the same requirement: request a quote.

