Scope of Works

The scope of works is the document that defines what the contractor is actually building. It's the bridge between the architect's drawings and the contractor's price. Without a clear scope, you're not comparing tenders — you're comparing guesses. And those guesses will haunt you through the entire construction phase in the form of variations and disputes.

A good scope of works is specific. It doesn't say "install kitchen" — it says "supply and install 2-pac kitchen cabinetry to joinery drawings J-01 to J-04, with 20mm Caesarstone benchtops in Osprey, Blanco undermount sink, and Dorf Maximus mixer tap." The more specific the scope, the less room for interpretation, and the fewer variations you'll deal with later.

Equally important is what's excluded. A scope document should explicitly state what's not included. Is site clearing in the builder's scope? Are authority connection fees? Is landscaping? If these aren't addressed, both parties will assume the other is responsible — and by the time you figure it out, it's a variation.

For developers managing multiple consultants and contractors, scope coordination is critical. The architect's scope needs to align with the engineer's scope, which needs to align with the builder's scope. Gaps between scopes mean work that nobody has priced. Overlaps mean work that's been priced twice. Neither is good for your budget.