How do I run a snag list that actually ends?

First, be clear which of the two lists you are running, because they have different rules and mixing them is how lists become immortal:

Two lists, not one

The snag list at completion is the punch list of minor items around practical completion: touch-ups, adjustments, the missing cover plate. Its legal weight is limited and worth knowing: minor snags do not prevent practical completion, so this list is a tidy-up schedule, not a hostage-taking instrument, and money withheld against it has the usual notice rules.

The schedule of defects comes at the end of the rectification period, months later: the formal gathering of defects that appeared in use. Different document, different trigger, and the second half of the retention runs on closing it, not on the completion snags. A client “adding to the snag list” in month seven is actually operating the defects machinery, and naming that changes the conversation.

The four rules that give a list a bottom

1. One list, one owner. A single document, held by one named person, replacing the texts, the emails and the notes on the kitchen worktop. Items arrive by being added to it, with a date; anything else is conversation. On what belongs on it at all, half the usual candidates are not defects, and the taste items get answered, not absorbed.

2. A baseline walkthrough, once. Walk the job together, list everything, and date-stamp the list as the baseline. New items can still arrive, genuine ones do, but they arrive visibly as additions, which kills the regenerating-list trick where every visit resets the count. The baseline is also your evidence that the tail was minor, which matters for certification.

3. Dates on both sides. Every item gets your fix-by date, and closing needs their part too: access on agreed days (withheld access is its own page), decisions where a choice is needed, inspection within a stated time of your notice that items are done. A list only you have deadlines on is a leash.

4. A defined finish. Closed means: items done, confirmed in writing, and the paperwork consequence triggered, at completion, the certificate; at the period’s end, the making good certificate and the final release. A list that just peters out leaves the money stranded behind a document nobody formally ended, which is exactly how retention gets stuck for years.

On a job for someone living in the house

The process works unchanged, and matters more: a homeowner has no contract administrator imposing discipline, so the baseline walkthrough and the single owned list are things you introduce, framed as service, “so nothing gets missed”. The formal schedule of defects exists only if your contract created a defects period; where it did not, the two-list structure is still worth running informally, because the alternative is a rolling complaints channel with your final payment attached to it (section 106 meaning the county court, not adjudication, if it ever hardens).

What to do this week

1. If a live list is sprawling, consolidate it today: one document, baseline-dated, everything else superseded, and circulate it as the single version.

2. Put dates on every open item, both sides’, and diary the follow-ups.

3. Close formally: the confirmation email per batch, and the certificate request the day the last item goes.

Where the information stops

A list being used strategically, regenerated to delay a certificate or justify a withholding, has stopped being a quality process and become a payment dispute wearing overalls, and the pages that govern it are the money ones; if that is where yours has gone, the reply is notices and deadlines, not more snagging, and serious sums deserve advice before the next walkthrough.