Statement Of Work Review For Canberra Contractors

You have finally landed the project, or you're close. Then the client sends through a statement of work and asks you to sign before kickoff.

If you're a Canberra consultant, IT contractor, designer, project manager or specialist supplier, that document can decide when you get paid, what you're responsible for, who owns your work and what happens if the project changes. It's worth slowing down before you commit.

A statement of work review in Canberra is often less about local ACT rules and more about the commercial deal sitting inside the document. This is especially true if your work is government-adjacent, involves sensitive information or sits under a larger head contract you haven't seen.

Do I Need A Lawyer To Review A Statement Of Work?

Often, yes - especially if the SOW sets a fixed price, fixed deadline or high-value deliverables. A statement of work can look operational, but it usually carries legal obligations that affect your cash flow and risk.

A good statement of work contract review should check more than spelling and formatting. It should test whether the document matches how you actually plan to deliver the project.

For example, your review should look at:

• Scope: exactly what you're delivering, and what you aren't delivering.
• Milestones: whether dates depend on the client giving feedback, access or materials on time.
• Acceptance: how the client approves deliverables, and what happens if they stay silent.
• Payment: whether invoices line up with real work and project costs.
• IP and confidentiality: who owns new work, existing tools, templates and know-how.
• Liability: whether your exposure is capped and whether exclusions are reasonable.
• Termination: whether you still get paid for work done if the client ends the project early.

You might not need a full contract review and redraft every time. Sometimes a focused SOW review lawyer can mark up the risky clauses, give you negotiation wording and explain what is worth pushing back on.

The bigger the project, the more this matters. Without clear terms, you may end up doing unpaid extra work, waiting too long for approval or carrying risk for delays that weren't your fault.

What Should A Canberra Contractor Check Before Signing An SOW?

You should check whether the SOW matches the commercial deal you agreed, not just whether it sounds professional. Many disputes start because the contract uses neat wording for a messy project.

Canberra contractors often work with Commonwealth agencies, universities, defence-adjacent suppliers, consulting firms and technology vendors. These projects can involve extra layers, such as security requirements, confidentiality rules, privacy obligations and strict reporting.

Before signing, work through this practical checklist:

• Parties: confirm the correct legal names, ABN or ACN details and who has authority to sign.
• Start date: check whether work starts on signing, purchase order approval or another trigger.
• Deliverables: make sure each deliverable is described clearly enough that both sides can tell when it's finished.
• Dependencies: list what the client must provide, such as access, data, personnel, approvals or equipment.
• Assumptions: spell out the assumptions your price relies on, such as the number of workshops or rounds of feedback.
• Out of scope work: explain how extra work will be quoted, approved and charged.
• GST: confirm whether fees are inclusive or exclusive of GST.
• Order of documents: check whether the SOW overrides or sits below a master services agreement, supplier terms or head contract review process.

If a client says the SOW is standard and can't be changed, you can still ask for clarifications by email or add a schedule of assumptions. A short clarification can make a big difference later.

A Simple SOW Outline To Fill In

If you're preparing comments or asking for changes, this outline can help you organise the key points. It isn't a finished legal document, and a lawyer should tailor it before you use it.

1. Project Summary: write a short description of the project and business objective.
2. Deliverables: list each item you'll deliver, with enough detail to avoid guesswork.
3. Milestones And Dates: set realistic dates and link them to client inputs where needed.
4. Acceptance Process: state how the client reviews, approves or rejects each deliverable.
5. Fees And Payment: set invoice triggers, payment timing, GST and expenses.
6. Assumptions And Dependencies: list what the client must provide for you to perform the work.
7. Change Control: explain how scope changes are requested, priced and approved.
8. IP, Confidentiality And Data: state who owns what and how confidential information is handled.
9. Liability And Insurance: set any liability cap, exclusions and required insurance.
10. Termination: explain when either side can end the SOW and what payments are due.

How Do Scope, Milestones And Acceptance Work In A Contractor Statement Of Work?

Scope, milestones and acceptance are the engine room of a contractor statement of work. If they're vague, the client can expect more than you priced, and you may struggle to invoice on time.

Your scope should be specific, but not so narrow that it becomes unusable. Aim for language that a new project manager could read and apply without needing to know the backstory.

Milestones should tie payment to fair project events. For fixed-price work, avoid leaving too much money until the final milestone unless you can carry the cash flow risk.

Acceptance clauses are just as important. You want a process that tells the client how to give feedback and stops open-ended review periods.

A practical acceptance clause usually covers:

• how many business days the client has to review a deliverable
• what counts as a valid rejection, such as not meeting agreed specifications
• how many rounds of revisions are included
• whether a deliverable is accepted if the client uses it in production
• whether silence after a set period counts as acceptance

Worked Example: The $90,000 Canberra Data Project

Priya runs a Canberra data consultancy. A client sends her a 12-week SOW for $90,000 plus GST, payable only after final delivery. The scope says she will deliver a dashboard, stakeholder workshops and documentation, but it doesn't say how many workshops or when the client must provide access to its systems.

Priya asks for three milestone payments of $30,000 plus GST each: on project plan approval, prototype delivery and final handover. She also adds four workshops, two rounds of feedback per deliverable and a five business day acceptance period.

The result is still commercially friendly for the client, but much safer for Priya. If the client delays system access for two weeks, the milestone dates shift. If the client wants six extra workshops, that becomes a paid change request instead of unpaid scope creep.

What Should Government Contractors Watch For In An SOW?

Government contractors should watch for flow-down obligations, confidentiality, security, IP and audit rights. Even if you're contracting with a prime contractor rather than an agency directly, the SOW may pass government requirements down to your business.

Canberra projects often sit close to Commonwealth procurement, public sector policy or regulated data. The Commonwealth Procurement Rules can shape how government entities buy services, but your practical obligations will usually appear in the contract documents you're asked to sign.

Common government-adjacent SOW risks include:

• Unseen head contract terms: the prime contractor may say you must comply with agency terms you haven't been given.
• Security requirements: the SOW may require clearances, secure systems, access controls or incident reporting.
• Confidential information: the definition may be wide and last beyond the project end date.
• Privacy: if you handle personal information, the Privacy Act 1988 and the Australian Privacy Principles may affect how you collect, store, use and disclose it.
• Data location: the client may restrict offshore storage, cloud hosting or subcontractor access.
• Audit rights: the client may want to inspect records, systems or compliance processes.
• Modern slavery and workplace compliance: larger clients may ask for policy confirmations or supplier declarations.

If you can't comply with a requirement, say so early. For example, don't sign a clause saying all staff hold a particular clearance if only your project lead does. Instead, propose wording that matches reality, such as naming the roles that require clearance or setting a pathway to obtain it.

A government contractor SOW review should also check whether you need approval before using subcontractors or a subcontractor agreement. If you rely on a specialist developer, designer or analyst, make sure the contract lets you use them and that your subcontractor terms line up with your client obligations.

Who Owns The IP Created Under A Statement Of Work?

It depends on the contract, so you should never assume you keep ownership just because you created the work. Under Australian copyright law, contractors often own copyright in works they create unless there's a written assignment, but contracts commonly change that position.

For many contractors, the real issue is separating new project IP from pre-existing IP. New project IP might be a report, design, integration, code module or training material created for the client. Pre-existing IP might be your templates, frameworks, libraries, know-how, processes or tools you use across many clients.

If the SOW gives the client all IP, check whether that accidentally captures your background materials. Losing control of your reusable assets can make it harder to serve future clients or build your business.

A balanced IP clause might say:

• the client owns the final deliverables once you're paid
• you keep ownership of your pre-existing IP, tools, templates and methods
• the client receives a licence to use those background materials as part of the deliverables
• you can reuse general skills, ideas and know-how that aren't confidential
• open-source software or third-party materials are handled under their own licence terms

If your work includes trade marks, product names or brand assets, you may also need to think about IP Australia trade mark registration filings. If you're licensing software, training content or creative work rather than assigning ownership, the SOW should say that clearly.

Confidentiality also matters here. You might own your methods, but you still can't reuse the client confidential information you learned during the project.

What Should You Do If The SOW Has Already Gone Off Track?

You should pause, document what has changed and avoid doing extra work without written approval. Most project issues are easier to fix while the work is still underway.

Start by checking the signed documents. Look at the SOW, any master services agreement, purchase order, email approvals and change request process. Confirm what the contract says about scope, timing, payment, acceptance and termination.

Then get your records in order:

• the signed SOW and any later versions
• emails or messages where the client requested changes
• meeting notes and decision logs
• timesheets or work records, even for fixed-fee projects
• draft deliverables and delivery dates
• client feedback, approvals or delays
• invoices, payment reminders and purchase order details

Next, raise the issue clearly and commercially. You might say: The requested reporting module is outside the agreed dashboard scope. We can deliver it as a change request for an additional fee and a two-week extension, or we can keep the original scope and timeline.

If payment is delayed, check the payment clause, invoice requirements and any unfair contract terms. Some larger clients require a purchase order number, specific invoice wording or portal submission. A technically valid invoice process can be the difference between payment this month and payment in the next cycle.

If the client won't engage or the project risk is growing, get help before you terminate, suspend work or send a strong letter. Those steps can affect your own obligations, and the best approach depends on the contract and the facts.

Key Takeaways

• A statement of work can create serious legal and commercial obligations, even if it looks like a project document.
• Canberra contractors should pay close attention to scope, milestones, acceptance, payment triggers, IP ownership and liability caps.
• Government-adjacent SOWs often include extra requirements around confidentiality, privacy, security, audits and subcontractors.
• Clear assumptions, dependencies and change control wording can protect you from unpaid scope creep.
• If the project changes, document it early and get written approval before doing extra work.
• Templates can be useful for structure, but your SOW should be tailored to your project, client and risk profile.

If you'd like help with reviewing your statement of work, negotiating project terms, protecting your IP and setting up clear contractor agreements, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.