A scope of works template only sets the format; what makes the document usable is a consistent, evidenced record built item by item, not the column headers you start with.
What a scope of works template actually gives you
A scope of works template is usually a spreadsheet or Word document with columns for item, description, trade and sometimes cost. It gets you a shape to fill in. It does not get you the thing that makes a scope of works useful on a live job: a consistent, evidenced record of what is actually there, where it is, and who is responsible for it.
The template is the format. The scope of works is the content. Confusing the two is why so many scopes of works end up vague, inconsistent between authors, or stripped of the detail a subcontractor or QS actually needs to price or act on.
The real unit is the item, not the document
Every useful scope of works, whatever it’s called on your job (defects list, snagging list, works schedule), is built from the same unit: a single item tied to a location, a trade and evidence. Swap the template and the unit doesn’t change. Get the unit wrong (vague location, no photo, ambiguous trade) and no template will save the document.
- Location: room or elevation, specific enough that two people would point at the same spot
- Trade: the party actually responsible for fixing or completing it
- Description: what’s wrong or what’s required, in plain terms
- Evidence: a photo, ideally one that shows the defect clearly against context
- Status: open, in progress, closed, with a date
A blank template with those column headers does nothing until someone fills it in consistently, on site, against the actual property. That’s the harder part, and it’s where most scopes of works fall down, not in the choice of template.
Where the template breaks down in practice
On a live site, scopes of works get filled in by different people at different times: a site manager doing a walk-round, a sub picking up a defect, a client’s rep at handover. Each brings their own shorthand. Locations get described differently (bathroom vs en-suite vs first floor WC). Trades get skipped or guessed. Photos get taken separately and never linked back to the row they belong to.
The result is a document that looks complete, rows filled, columns populated, but isn’t usable, because a subcontractor pricing the work or a PM chasing a trade can’t tell exactly what’s being referred to without going back to site.
New build handover: what actually governs the process
If the scope of works is a defects list at new build handover, there are a couple of frameworks worth knowing rather than relying on a generic template.
Under NHBC Buildmark, the builder warranty period runs for two years from legal completion, after which eight years of insurance cover specified structural defects; NHBC also runs a free resolution service during the first two years.
The New Homes Quality Code (Version 2, March 2026) gives buyers a right to a pre-completion inspection. You can appoint a professional from a recognised body (CABE, CIOB, ICWCI, RICS or RPSA) with professional indemnity insurance, or carry it out yourself using the NHQB checklist. Where issues breach warranty technical standards, the developer is expected to address them, ideally before legal completion or within 30 days.
A professional snagging survey typically costs £300 to £600 depending on the size of the property. None of this dictates what template you use, but it sets the frame the scope of works has to work within, which is worth checking before you build one from scratch.
Building the scope of works without starting from a template
Instead of downloading a template and filling it in after the walk-round, capture each item at the point you find it. That’s the difference between a document assembled from memory later and one that’s accurate the day it’s produced.
- 1Photograph the defect or item, close enough to identify it and wide enough to show context
- 2Mark or circle the specific point on the photo so location isn’t ambiguous
- 3Record the trade responsible and a plain description of what’s needed, on the spot
- 4Group by room first, then by trade, so a subcontractor gets only their items
- 5Track status against each item until it’s closed, not just listed
This is the structure SayScope is built around: you photograph the defect, circle it, hold a button and say what’s wrong, and it leaves you with a report already grouped by room and by trade. It doesn’t replace judgement about what counts as a defect, but it removes the gap between a walk-round and a usable document, which is where most templates fail.