Read a statement of work and know exactly what was agreed
A statement of work describes a specific project under a broader services agreement: what is in scope and out of scope, the deliverables, the acceptance criteria, the milestones, the fees and the assumptions the price depends on. Disputes often start in the gaps between those parts. Upload the SOW and the master agreement, ask about each part in plain language, and read the cited passage before you commit to a date.
Creating an account needs no payment.
Last updated October 2026
How to review a statement of work with Search+
- Upload the SOW with the master agreement
Add the statement of work and the master services agreement it sits under, plus any change orders. SOWs are often negotiated in Word, so upload the draft you are working from. The master agreement usually controls payment, liability and termination.
- Set your role in Workspace Context
Write something like "We are the vendor; flag scope that is vague, acceptance that has no deadline and assumptions that shift risk to us." That instruction is applied to every question.
- Ask about scope, then acceptance, then money
Ask what is out of scope, how deliverables are accepted, and how fees are triggered. Each answer cites the passage it relied on.
Questions people ask about a statement of work
What does this SOW say is out of scope, and how are extra requests handled?
List each deliverable with its due date and the milestone it belongs to.
How is a deliverable accepted, and what happens if the client does not respond?
Which assumptions does the price depend on, and who carries the risk if they turn out wrong?
Is this fixed fee or time and materials, and when is each invoice due?
If the SOW and the master agreement conflict, which one controls?
What reading a SOW carefully involves
A clear SOW lists what is excluded as well as what is included. Vague scope words like "support" or "assist" are a common source of disputes.
Acceptance rules decide when a deliverable is finished and often when it can be invoiced. Check for a review period and what happens if it lapses.
Many SOWs price the work on stated assumptions, such as client access or timely feedback. Those clauses quietly allocate risk.
Liability limits, intellectual property and termination usually sit in the master agreement. Read the SOW with it, and check the order of precedence clause.
Search+ can answer across the SOW, the master agreement and change orders at once, citing each excerpt it uses.
Typical sections of a statement of work
| Section | What it usually covers | A question to ask Search+ |
|---|---|---|
| Background and objectives | Why the project exists | What outcome is the project meant to achieve? |
| Scope of services | Work included and excluded | Is data migration in scope? |
| Deliverables | What will be handed over | What is the second deliverable and when is it due? |
| Acceptance | How deliverables are approved | How long does the client have to reject a deliverable? |
| Schedule and milestones | Dates and phases | Which milestones trigger payment? |
| Fees and expenses | Pricing model and invoicing | Are travel expenses billable? |
| Assumptions and change control | Conditions and how changes are made | How is a change request approved? |
What is a statement of work?
A statement of work, or SOW, is a document that defines a specific project's scope, deliverables, schedule, acceptance criteria and fees, usually issued under a master services agreement that sets the general terms.
Statement of work questions
Can Search+ list every deliverable and due date in a SOW?
Can it tell me what is out of scope?
Will it check the SOW against the master agreement?
Can I track change orders over time?
Is reading a SOW with Search+ the same as legal review?
Agree on scope before the work starts
Start a workspace, upload the SOW and the master agreement, and ask what each side must deliver.
Start a workspace