What Should a Software Statement of Work Include?
A software statement of work should define the delivery commitment between buyer and supplier: deliverables, exclusions, responsibilities, dependencies, acceptance criteria, payment triggers, change control, and termination arrangements. It should reference an agreed version of the requirements document and identify which requirements the supplier is committing to deliver. Use the software development statement of work checklist below to check whether both sides can tell what completion means before work begins.
What should your software statement of work checklist cover?
Use this table when reviewing a draft. For each row, look for a specific commitment, an owner, or a decision rule.
| Area | What to include |
|---|---|
| Purpose | The business outcome and the work this engagement covers |
| Requirements reference | The agreed document version and included requirements |
| Deliverables | Software, designs, documentation, and handover materials |
| Exclusions | Related work and services outside the agreed price |
| Responsibilities | What the buyer and supplier must each provide |
| Dependencies | Required access, decisions, data, and outside services |
| Schedule | Milestones, sequencing, and conditions for starting |
| Acceptance | Review method, evidence, reviewers, and defect handling |
| Payment | Amounts or charging basis and clear invoice triggers |
| Change control | How scope changes are assessed and authorised |
| Termination | How work stops, charges are settled, and handover happens |
Also identify the parties and the people authorised to approve scope, acceptance, and spending. Make clear how this statement of work fits with any wider agreement covering ownership, confidentiality, liability, and other commercial terms.
How should it reference the requirements document?
Use the requirements document to describe what the product must do. Use the statement of work to identify which of those requirements form the delivery commitment, together with the price, schedule, and review process.
Reference the document by title and version. Avoid a reference to a live document that anyone can edit without changing the agreed scope.
If the requirements include future ideas, mark the included sections explicitly. A requirement's presence in the document should not leave the reader guessing whether it belongs in this engagement.
State how conflicts between documents will be resolved. For example, identify which document controls the delivery scope and which controls the acceptance detail. Agree this order rather than relying on whichever wording seems more convenient later.
For practical ways to organise these records, see documentation best practices in software projects.
How specific should deliverables and exclusions be?
Describe deliverables as things the buyer can inspect. “Build the reporting module” leaves too much open. A clearer description names the reports, supported filters, access permissions, export formats, and accompanying documentation.
Include the materials needed to operate and maintain the result: source code, setup instructions, account access, deployment instructions, and any agreed training. Specify the delivery format and destination for each.
Write exclusions alongside the relevant deliverable. If importing existing records is included but cleaning those records is excluded, say both. Other boundaries to consider include content writing, translation, ongoing hosting, outside service charges, and support after handover.
Avoid broad promises such as “production ready” unless the document explains the checks and responsibilities behind them. Name what will be tested, delivered, and handed over.
Who owns responsibilities and dependencies?
Assign an owner to each input the project needs. “The client will provide support” is too vague to schedule against.
Name who supplies sample data, approves designs, provides access, answers product questions, and coordinates outside vendors. Give each input a required milestone and a clear description of what counts as usable.
For every important dependency, record:
- What must be available before the affected work begins.
- Who must provide it and who checks it.
- What happens if it arrives late or proves unsuitable.
- How any resulting schedule or cost change is approved.
Do not treat every delay as automatic permission to increase the price. Require the supplier to explain the impact and follow the agreed change process.
How should milestones reflect the delivery approach?
Tie milestones to visible outcomes: an approved design, a working workflow, an accepted release, or completed handover. Give each milestone entry conditions, deliverables, and review steps.
Where later work depends on discovery, define the discovery commitment separately. State what it will produce and what decision authorises the build. Avoid presenting an uncertain build scope as a settled fixed-price promise.
For iterative delivery, define how work is selected, who sets priorities, the spending limit, and what each review can change. Distinguish a commitment to provide team capacity from a commitment to deliver a fixed feature set.
The same questions apply across delivery methods. Agile software development methodologies explained provides context for discussing how work will be planned and reviewed.
What makes acceptance clear enough to use?
Connect acceptance to observable behaviour and agreed evidence. For each deliverable, identify the reviewer, test environment, required test data, review period, and way to record approval or rejection.
Explain how defects are reported, assessed, corrected, and retested. Define which defects block acceptance and how remaining items will be tracked. Specify how a disagreement about the result will be escalated.
Decide explicitly what happens when the buyer does not respond. Do not leave silence open to competing interpretations.
Illustrative acceptance example: For a customer-record import, acceptance might require valid records to appear correctly, duplicate records to follow an agreed rule, invalid rows to produce understandable messages, and unauthorised users to be denied access. Attach the sample data and expected results.
Acceptance should check the agreed outcome, while the supplier's quality checks cover the implementation. Discuss both using the questions in software testing and quality assurance.
How should payment triggers work?
Make each invoice trigger verifiable. If a payment depends on acceptance, identify the accepted deliverable. If it depends on time worked, specify the rates, authorised roles, reporting method, spending limit, and approval needed to exceed it.
Separate the invoice trigger from the payment deadline. Explain the process for disputed charges and whether undisputed amounts remain payable.
Account for approved expenses, outside subscriptions, and ongoing charges. Identify who contracts with each provider and who controls the account.
Check that the payment schedule covers handover as well as development. Where ownership or access depends on payment, make the relationship explicit and consistent with the wider agreement.
How should scope changes be approved?
Require a written change request that describes the proposed change and its effect on deliverables, exclusions, acceptance, price, schedule, and dependencies.
Name who may approve it and how approval is recorded. State whether the affected work pauses while a decision is pending.
Distinguish a defect from a scope change using the agreed requirements and acceptance criteria. Behaviour that fails an included requirement should follow the defect process. A request for additional behaviour should follow change control.
For iterative work, allow agreed priority swaps where appropriate, but record what leaves the scope when something enters it. Reordering work and expanding the commitment are separate decisions.
What should happen if the engagement ends early?
Define the process for ending work, including notice, any opportunity to resolve a problem, and the point at which work stops.
Explain how completed work, work in progress, approved commitments, and disputed items will be assessed and charged. Specify what the buyer receives and any conditions attached to that handover.
List the exit materials: current source code, designs, documentation, known issues, relevant data, and an explanation of unfinished work. Assign responsibility for transferring accounts, revoking access, and handling retained data.
Keep these arrangements consistent with the wider agreement. Do not leave the exit process dependent on informal cooperation.
What common mistakes should buyers catch?
- Signing against an unfinished scope. Separate discovery from the later build commitment when key requirements remain unresolved.
- Listing features without boundaries. Include permissions, failure cases, exclusions, and handover.
- Using subjective acceptance language. Replace “easy to use” with agreed tasks and observable results.
- Assuming buyer inputs will arrive on time. Assign owners and define the impact-review process.
- Approving changes in casual messages. Record the commercial and delivery effects before work proceeds.
- Leaving support undefined. State what is covered after acceptance, for how long, and how additional work is commissioned.
Before signing, ask both sides to explain the same milestone independently. Compare what each expects to receive, approve, and pay.
What else do buyers ask about software statements of work?
Does it need to repeat every requirement?
No. Reference an agreed version and identify the included sections. Repeat detail only where it clarifies a delivery boundary or acceptance condition.
Can it cover an evolving product?
Yes. Define the capacity or outcomes being purchased, the budget boundary, prioritisation authority, and review process. Be explicit about which commitments are fixed and which remain open.
Is a proposal enough?
Check its contents. If it leaves scope, acceptance, payment, change control, or exit arrangements unanswered, resolve those gaps in the signed documents.
Should support be included?
Make it an explicit choice. Define any included defect correction, maintenance, response expectations, and ongoing charges so the buyer can plan beyond handover.