Working Through a Snagging List Without the Email Chain

Working through a snagging list is a five-step job, and none of the steps is "fix things". You triage the list within 24 hours into what is yours, what belongs to another trade, and what you dispute. You break every remaining item into a task with exactly one named owner and one dated deadline, because a defect with two owners has none. You fix in visit order, not list order, so one trip closes six items instead of six trips closing one each. You photograph each fix as you close it, tied to the item number, not dumped in a camera roll. And you deliver one remediation report — in Sweden, an åtgärdsrapport — listing every item, its status, who did it, when, and the evidence. One document, one send. The email chain is what turns a two-week snag into a two-month hold on your final payment.

Why working through a snagging list stalls

It rarely stalls on the work. Most snags are twenty minutes each: a socket sitting proud of the plaster, a missing label on a circuit, a trap that weeps, a door that catches, a certificate that was never uploaded. The work is not the problem.

The problem is that the list arrives as a PDF, and a PDF has no owner field, no status, and no way to be half-done. It lands in the site manager's inbox, gets forwarded to four subcontractors, and from that moment the only record of progress is a thread of replies saying "the ones on the first floor are done" with no reference to which ones those were.

Three failure modes follow, and you will recognise all of them:

• The orphan. Item 14 is ambiguous about which trade owns it. Everyone assumes someone else has it. It is still open at re-inspection.
• The reopened fix. You closed item 9 in week one. Nobody recorded it, so at re-inspection it is listed as outstanding and you drive back to look at your own finished work.
• The 90% hold. Nineteen of twenty items are closed. The twentieth is another trade's. Your money sits behind it, because the client is holding retention against the list, not against the item.

Every one of those is an admin failure wearing a workmanship costume.

What the inspection actually produces

Terminology first, because the same document has four names. In Sweden a formal handover inspection is a slutbesiktning, carried out by an independent besiktningsman under the standard contracts AB 04 (executed contracts) or ABT 06 (design-and-build), or under ABS 18 and the Consumer Services Act (konsumenttjänstlagen) for consumer house-building. It produces a besiktningsutlåtande containing numbered anmärkningar. In the UK the same thing is a snagging list issued at practical completion. In New Zealand and Australia it is a defects list. In the US, a punch list.

The mechanics are close enough to share one workflow, and the money works the same way everywhere: the list is what stands between you and the last slice of the contract sum. Swedish consumer law lets a customer hold back an amount as security for a claim over defects. Under UK JCT-family contracts retention is commonly 3–5%, with roughly half released at practical completion and the balance at the end of the rectification period. Check the wording in the contract you actually signed rather than the one you remember.

What matters operationally is that the inspector's list is numbered. Those numbers are the only shared vocabulary between you, the client, the other trades and the re-inspection. Keep them. Never renumber, never merge two items, and if you must split one, keep the parent visible as 14a and 14b.

Step 1: Triage the list in the first 24 hours

Before anyone picks up a tool, sit down with the list and sort every item into four buckets. This takes an hour for a hundred items and saves a fortnight.

• Mine. My trade, my defect, my cost. Get on with it.
• Not mine. Another trade's work, or the client's own supply. Reply within 24 hours naming the item numbers and stating the reason for each. Silence reads as acceptance.
• Not a defect. The installation is as specified and as drawn, or the "defect" is a change of mind. That is a variation, not a snag. Price it.
• Mine, but blocked. I cannot fix item 22 until the tiler is out of that bathroom. Flag the dependency and the date you need access.

The 24-hour window is not legalism, it is arithmetic. Every day spent deciding whether an item is yours is a day nobody is fixing it, and it is the disputed items that end up setting the re-inspection date. Write the triage down against the item numbers and send it as one message. Not a phone call. A phone call about item ownership is a rematch waiting to happen.

Step 2: Turn each item into a task with one owner and one deadline

This is the whole trick. A snagging list is not a document to be worked through. It is a set of small jobs that happened to arrive in one envelope. Treat each item as a work order. An item is properly specified when it carries all of this:

Assign to a person, never to a trade. "Electrical" is not an owner, it is a category. If your system only lets you assign to a team, assign to the team and name a lead who is accountable for the count.

Then sequence by visit, not by number. Group items by floor, by flat, by riser. Item 3, item 17 and item 41 may all be in the same cupboard. That is one visit, not three, and it is the single largest saving available in the whole process.

Step 3: Separate your items from the other trades'

If you are the main contractor, run one master list with a trade column and own the count. If you are a subcontractor, run your own extract and keep it reconciled to the master numbering.

The rule that saves the most grief: never fix another trade's item as a favour without recording it. An unrecorded fix has no author. Three weeks later nobody can say whether item 27 was closed, by whom, or at whose cost. If you do it, log it against the item as a recharge and let the commercial conversation happen in daylight.

And publish the split. A weekly line to the client saying "18 of our 22 items closed, 4 open with dates, and 6 items on the list are not ours, flagged on 3 July" is worth more than any amount of quiet diligence. The client is chasing a number. Give them the number before they ask for it.

Step 4: Photograph the fix, not the finish

A photo of a tidy wall proves nothing. It proves there is a wall. The photograph exists to answer one question: was this specific defect corrected? So it has to show the item's location and the corrected condition in a way the inspector can match to their own note. What a usable snagging photo contains:

• Context, then close. Two shots. One wide enough to place the item in the room, one close enough to see the work.
• Something that says where. Door number, socket label, circuit number, or a taped card with the item number on it. Anything that survives being viewed by someone who was not there.
• The measurement, if the anmärkning was a measurement. If the inspector wrote "socket not flush", the photo needs a straight edge in it. If they wrote a torque figure or an insulation value, the photo is of the reading.
• A before shot, if the fix hides itself. Anything you are about to close up gets photographed open: a cable run before plastering, a joint before boxing in.
• Attached to the item, on the spot. Not to the job. Not to a chat group. To item 14, from the phone, standing in front of it.

That last point is the one people skip, and it is the one that costs. A photo taken at 14:20 and filed at 19:00 from the van gets attached to the wrong item often enough to matter, and you find out which one at the re-inspection.

Which is where a field app that works offline earns its keep. Snagging happens in stairwells, plant rooms and basements with no signal. If the app cannot capture a photo against item 14 with no bars and sync it later, your technicians will use the camera roll and you are back to the email chain. OdinTask handles it the boring way: the field app is offline-first, so the photo, the note and the status change queue on the phone and replay when signal returns, still attached to the right item.

Step 5: One åtgärdsrapport, not an email chain

The deliverable is a single document, sent once, when the list is closed. In Sweden that is an åtgärdsrapport, a remediation report. In the UK you send a completed snagging schedule with sign-offs. Same object. It contains, in the inspector's own numbering:

1. Every item, with the inspector's original wording quoted.
2. The status: closed, disputed, not ours, or outstanding with a date.
3. What was actually done, in one line. "Socket refitted flush, back box packed out" beats "rectified".
4. Who did it, and on what date.
5. The evidence, per item: the photo, and where relevant the test reading or certificate.
6. Any items the inspector should not re-inspect because they were never yours, with the date you said so.

Send it as one PDF to the inspector and the client at the same time. Do not send it in instalments. Every partial update invites a partial reply, and a partial reply is how a closed item quietly reopens.

This is not a new kind of document. It is the same shape as a Swedish egenkontroll or protokoll: numbered rows, a status per row, evidence per row, a name and a date at the bottom. If you already build self-inspection protocols digitally — OdinTask has a protokoll builder that produces exactly this as a PDF — the snagging report is that template with the inspector's list as the rows. If you do not, a spreadsheet with a photo-link column still beats a PDF and forty emails.

The re-inspection, and what it usually costs you

In Sweden a re-inspection is an efterbesiktning. Under AB 04 and ABT 06 the general position is that the contractor carries the cost of an efterbesiktning of items that were validly noted: you pay to have your own snags looked at twice. Where an item was noted wrongly, the cost can fall the other way. Read the clause in the contract in front of you rather than running on folklore.

The commercial consequence is simple. Call the efterbesiktning once, when everything is closed. Not when you are close. Two re-inspections cost roughly twice one, and the second carries a message you cannot un-send: this contractor does not know what state their own work is in.

Before you make the call, walk the site yourself with the list open. Finding your own last defect is free. The inspector finding it is not.

If you take one thing from this

The list is not a document. It is a set of jobs that arrived without work orders. Give each one a number, an owner, a date, a status and a photo, and working through a snagging list stops being a fortnight of chasing. It becomes what it always should have been: twenty small jobs, six visits, one report, invoice paid.

If you want the whole thread — enquiry, quote, job, protocol, snags, invoice — on one record instead of in six inboxes, start a free trial of OdinTask or read more on the blog.