A scope of works is written by walking the job in a fixed sequence, recording what you see against what should exist, and specifying each item precisely enough that two different people would price it the same way.
Why templates fail you on site
Most scope of works templates are built around a blank structure: sections for each trade, a column for description, a column for cost. That structure is fine once you already know what you are specifying. It does nothing to help you work out what belongs in each line in the first place.
The actual skill in writing a scope is not formatting. It is the method you use to walk a property, decide what is in scope, and describe it so precisely that a quantity surveyor, a client, and a subcontractor would all read the same line and picture the same work.
Walk the job in one fixed sequence
Pick a route through the property and use it every time: structure first, then envelope, then first-fix, then second-fix, then finishes, then externals. Working trade by trade in a fixed order stops you doubling up on items and stops you missing rooms because you got distracted mid-walk.
- Structure and fabric: foundations, walls, roof, structural openings
- Envelope: windows, doors, render, cladding, damp proofing
- First-fix: electrics, plumbing, heating pipework, studwork
- Second-fix: sockets, radiators, fittings, ironmongery
- Finishes: plaster, paint, flooring, tiling, joinery
- Externals: drainage, paving, boundaries, drives
Photograph every defect or item as you go and circle the exact point on the photo. A written note that says ’crack in wall, living room’ is far weaker evidence than a photo with the crack marked and a voice note recorded on the spot describing length, direction and likely cause. Apps built for site visits, including SayScope, let you do this in one motion: photograph, circle, speak, and the item is logged against the room and trade without you writing anything down later from memory.
Specify so there is nothing left to interpret
A scope line fails the moment it needs a phone call to clarify. Every item should carry enough detail that a different contractor, reading it cold, would quote the same job.
- Location: room, elevation, or grid reference, not just ’kitchen’
- What is wrong or what is required, stated as a fact, not an opinion
- Trade responsible for the work
- Standard or reference it should meet, where one applies
- Access or sequencing notes that affect how it can be done
Avoid vague verbs. ’Make good’ and ’tidy up’ mean different things to different trades. Say what the finished state looks like instead: ’fill and sand to flush finish, ready for two coat emulsion.’
Group by room and by trade, not just one or the other
A scope grouped only by room is hard for a subcontractor to price, because their items are scattered across every page. A scope grouped only by trade is hard for a client to read, because they think in rooms, not trades.
The fix is to record each item once, tagged with both a room and a trade, then output two views from the same data: a room-by-room report for the client walkthrough, and a trade-by-trade report for pricing and instruction. Doing this by hand means duplicating every line twice and keeping both copies in sync by eye. A tool that tags each item once and generates both views removes that duplication.
Where a scope sits against a warranty or a code
On a new build still inside its NHBC Buildmark period, items that breach warranty technical standards are not the same as general snagging. NHBC Buildmark runs a two year builder warranty from legal completion, followed by eight years of insurance cover for specified structural defects, with a free NHBC resolution service available in the first two years. Separate the two categories in your scope so the client knows which items can be raised through that route.
Where the New Homes Quality Code Version 2, from March 2026, applies, a buyer has the right to a pre-completion inspection. They can appoint a professional from a recognised body such as CABE, CIOB, ICWCI, RICS or RPSA with professional indemnity insurance, or carry out the inspection themselves using the NHQB checklist. Where issues breach warranty technical standards, the developer addresses them, ideally before legal completion or within 30 days. A scope written before that inspection can be used as the working document for it.
Keep the scope alive after the first walk
A scope of works is not finished the day you write it. Items get resolved, new ones surface during the works, and the client needs to see what changed without you reissuing the whole document each time. Build it so items can be marked closed, reopened if the fix fails, and dated, rather than editing one static file that nobody can trust is current.
