Free scope of works

• The MapTrack scope of works contains 15 checks across 3 sections. Sections covered: WORKS AND INCLUSIONS, EXCLUSIONS AND ASSUMPTIONS, DELIVERABLES, PROGRAM AND SIGN-OFF.
• Project and parties: project name, client, contractor, and contract reference
• Site details and background to the works
• Description of the works: a clear, plain summary of what is to be built or done

Learn more about asset tracking in MapTrack.

• Clear boundary: written inclusions and exclusions set exactly what is and is not in the contractor's price before work starts.
• Fewer variations: an explicit scope reduces the assumed-included gaps that turn into disputed variations and claims later.
• Defined deliverables: listing what will be handed over sets a shared definition of what finished and complete actually means.
• Program clarity: milestones and key dates tie the works to a timeline everyone has agreed rather than a vague finish.
• Responsibility split: recording who supplies, does and approves each part removes the who was meant to do that argument.
• Payment alignment: a scope broken into deliverables and milestones supports fair progress claims tied to real completion.
• Dispute reference: a signed scope is the document both parties return to when a question about the work arises.

• Project and parties: project name, client, contractor, and contract reference
• Site details and background to the works
• Description of the works: a clear, plain summary of what is to be built or done
• Inclusions: the specific works, supply and services the contractor is responsible for
• Exclusions: the works and items specifically not part of this scope
• Standards and specifications: codes, drawings and specs the work must meet
• Materials and supply: what is supplied by whom, and any nominated products
• Deliverables: the items, documents and handovers to be provided on completion
• Program and milestones: start, key dates, and completion or practical completion
• Responsibilities, assumptions, variation process, and acceptance or sign-off

1. Describe the works in plain terms

   Start with a clear, plain-language description of what is to be built or done and why, so anyone reading the scope understands the project without needing every drawing. This summary sets the context for the detailed inclusions and exclusions that follow, and stops the scope becoming a list of items with no sense of the whole.

2. List inclusions specifically

   Set out exactly what work, supply and services the contractor is responsible for, item by item, referencing the relevant drawings, specifications and standards. Be specific rather than general, because a scope that says the works generally are covered leaves far too much room for one party to assume something is in and the other to assume it is out.

3. State exclusions just as clearly

   Write down what is specifically not part of this scope, because the exclusions prevent the assumed-included disputes that cause most variations. If a related item could reasonably be thought part of the job but is not, say so explicitly. Unstated exclusions are the single biggest source of scope arguments on a project.

4. Define deliverables, program and responsibilities

   List the deliverables and handover items, set the key milestones and dates, and record who supplies, does and approves each part of the work. Note any assumptions the scope relies on, such as access, existing conditions or client-supplied items, so the basis of the price and program is on the record if those assumptions turn out to be wrong.

5. Agree the variation process and sign off

   Set out how changes to the scope will be requested, priced and approved, so a variation follows a process rather than a corridor conversation. Have both parties review and sign the scope, and issue it with the contract, because a scope that is agreed and signed is the reference that resolves questions instead of starting them.

Practical answers about the form, record keeping and using MapTrack.

This form is a starting point. Check the current requirements that apply to your equipment, work and location. The form alone does not establish compliance.

• AS 4000-1997 General conditions of contract (construct only)
• AS 4902-2000 General conditions of contract for design and construct
• National Construction Code (NCC), incorporating the Building Code of Australia
• Security of payment legislation in each state or territory (for example the Building and Construction Industry Security of Payment Act 1999 (NSW)) for progress claims tied to scope

MapTrack publishes this template. The linked authorities publish their own guidance; they haven't endorsed this form.

• Dilapidation Report Template
• Plant Equipment Register Template
• Asset Register Template
• Risk Register Template
• Permit To Work Form
• Asset tracking
• Reporting and analytics
• Pricing