Scope of Works
A scope of works is a detailed document defining exactly what work is included in a construction contract — materials, methods, quality standards, and exclusions — forming the basis for pricing and delivery.
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, disputes, and budget blowouts.
Why does specificity matter so much? Because every ambiguity in a scope document is a future variation waiting to happen. A scope that says "install kitchen" leaves everything open to interpretation — what cabinetry material, what benchtop brand, what sink, what tapware, what finish? A proper scope 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." When the spec is that precise, there's no room for argument about what was included in the price. The contractor priced exactly what was described. If you change it later, that's a variation and you both know it.
The scope document should address materials, methods, quality standards, and performance requirements. For materials, specify brands and models or provide an "or equivalent approved" clause with clear criteria for what constitutes equivalent. For methods, reference relevant Australian Standards (e.g., AS 3700 for masonry, AS 1684 for residential timber framing). For quality, define acceptance criteria — what level of finish is expected, what tolerances apply, what testing or inspection is required. Vague quality language like "to a high standard" is meaningless in a contract. Define what "high standard" means in measurable terms.
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? What about temporary fencing, survey set-out, or the removal of existing structures? Is landscaping included, or does it fall under a separate contract? If these items aren't clearly allocated, both parties will assume the other is responsible. By the time you figure it out on site, it's a variation — and variations cost more than they would have if they'd been priced in the original tender.
Provisional sums and prime cost items deserve special attention in any scope document. A provisional sum is an allowance for work that can't be fully defined at tender stage — maybe you don't have the final engineering design for the retaining wall, so you include a provisional sum of $80,000. The actual cost gets reconciled during construction. Prime cost items work similarly but for specific products — you might include a PC sum of $5,000 for a front door, to be selected later. Both create scope uncertainty, and both are common sources of cost variation. Minimise them where possible by completing your design before you tender.
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 — and someone will have to pay for it when the gap is discovered on site. Overlaps mean work that's been priced twice, which inflates your costs unnecessarily. A scope coordination review before you issue the tender package takes a few hours and can save tens of thousands.
A poor scope doesn't just cause variations during construction. It undermines the entire tender process. If your scope is vague, each tenderer will interpret it differently, price different things, and exclude different items. You'll receive bids that look wildly different in price but are actually incomparable because they're pricing different work. The cheapest bid might be cheap because it excluded half the work. The most expensive might be the only one that actually priced everything. Without a tight scope, you can't evaluate tenders fairly — and you'll almost certainly end up with a contract that doesn't cover what you need built.
How UpScale Handles This
UpScale helps you manage the procurement process from scope definition through tender evaluation to contract award. Each tender package captures the trade, scope description, and estimated value. When submissions come in, you can compare them against the same scope baseline — making it clear where bids differ and where exclusions or qualifications need to be resolved. The platform tracks the full lifecycle from draft through award, ensuring that the scope you tendered is the scope you contracted.
Related Terms
Tender Process
The tender process is the structured method of inviting, receiving, evaluating, and awarding contractor bids for construction work packages.
Variations (Construction)
A variation is a change to the original scope, cost, or timeline of a construction contract, formally documented and requiring approval before work proceeds.
Preliminaries (Construction)
Preliminaries are the time-related overhead costs of running a construction project — site establishment, supervision, insurance, temporary services, and project management — that aren't tied to specific building work.