What Is a Scope of Works?

A strong scope of works leaves as little as possible to interpretation. It goes beyond a general description of the job to spell out precisely what is being delivered, to what standard, and under what assumptions.

• Specific tasks and deliverables — described in enough detail that any competent contractor would price and build them the same way.
• Standards and specifications — the codes, materials, finishes and quality levels the work must meet.
• Inclusions — everything the price genuinely covers, stated explicitly rather than implied.
• Exclusions — work the client might reasonably expect but which is not included, stated just as explicitly as the inclusions.
• Assumptions — the conditions the price relies on, such as normal working hours, existing services being in working order, or site access being available when needed.

It is tempting to focus a scope of works entirely on what is included, but the exclusions are just as important — arguably more so, because they are what protects the price when something unexpected turns up. An exclusion stated clearly in writing heads off an argument later about whether an item was “obviously” part of the job.

Common items worth excluding explicitly, even when they seem obvious to the trade preparing the scope, include design and engineering fees, council and authority approvals, removal of unknown hazardous materials such as asbestos, making good to work by other trades, and anything outside normal business hours.

• State exclusions in the same document as the inclusions, not as a footnote or a verbal understanding.
• Be specific — “excludes hazardous materials removal” protects a price far better than a general disclaimer.
• Revisit exclusions whenever the drawings change, since a redesign can quietly turn an exclusion into something the new plan assumes is included.

These three documents work together on almost every job, and confusing them is one of the more common mix-ups in construction. Each one answers a different question about the same work.

• Scope of works vs specification — the scope says what work will be done; the specification says to what standard, using what materials and methods. A scope might say “supply and install kitchen benchtop”; the specification says it must be 20mm reconstituted stone in a nominated colour.
• Scope of works vs Bill of Quantities — the scope describes the work in words; the BOQ measures that same work into priced, quantified line items. The BOQ cannot be produced accurately until the scope, and the drawings it is based on, are settled.
• Scope of works vs contract — the scope is usually incorporated into the contract by reference, becoming one of the documents that defines what the contractor is legally bound to deliver.

In competitive tendering, the scope of works is what makes bids comparable in the first place. When every tenderer receives the same scope, differences between their prices reflect differences in rates, efficiency and risk appetite — not differences in what each one assumed was included.

A poorly written scope has the opposite effect: tenderers fill the gaps with their own assumptions, and a client comparing the resulting prices is often comparing apples with oranges without realising it. A tight scope is one of the most effective things a client — or a builder issuing a scope to subcontractors — can do to get bids that are genuinely comparable and free of hidden qualifications.

Scope creep is the gradual expansion of a job beyond what was originally priced, usually through a string of small, undocumented additions that individually seem too minor to bother formalising as a variation. It is one of the most common ways a profitable job quietly turns into a loss-making one.

A precise, written scope of works is the main defence against it, because anything not described in the scope is — by definition — outside the contract and a candidate for a priced variation rather than something absorbed for free. Builders who point back to their scope when a client asks for “just one more thing” tend to protect their margin far better than those relying on a verbal understanding of what was agreed.

Most scope of works disputes trace back to a handful of recurring mistakes, all of which are avoidable with a bit more care at the drafting stage.

• Describing the job in general terms (“renovate kitchen”) instead of specific tasks and deliverables (“remove existing cabinetry, supply and install new base and overhead units, benchtop, splashback”).
• Leaving exclusions unstated, so anything not obviously excluded is assumed by the client to be included.
• Not referencing the drawing and specification version the scope is based on, so a later plan revision leaves it unclear which scope actually applies.
• Failing to update the scope when a variation is agreed, so the contract document and the actual agreed work drift apart over the life of the job.