Free statement of work template

A statement of work is usually one layer of the contract

In most professional services relationships the paperwork comes in two layers. A master services agreement carries the legal terms that do not change from project to project: who owns what, confidentiality, warranties, insurance, liability caps, how disputes get resolved. The statement of work carries the project: objectives, deliverables, acceptance criteria, dates, who does what, and the price. One master agreement, many statements of work. That split is worth keeping, because it is what lets a new project start in a week instead of a month. It also means the SOW needs to say which layer it belongs to. Clause 1 of the template is a strike-one election: either this SOW sits under a named master agreement and takes its terms, in which case clauses 14 to 18 switch off, or there is no master agreement and those clauses supply the intellectual property, confidentiality, warranty, liability and termination terms the project cannot do without. Get that election wrong in either direction and the gap shows up at the worst moment. A SOW signed with no master agreement and no fallback terms has no liability cap, no confidentiality obligation and no clear owner of the deliverables. A SOW that duplicates the master agreement's terms creates two versions of each one, and then an argument about which applies. Clause 2 settles the ranking: the master agreement wins unless the SOW names the section it is varying and says so expressly. Other templates make a different choice, and our software development agreement lets its statement of work win on technical specification, so check the precedence wording in whatever master agreement you are signing under.

How to fill it in

Schedule B is the document. Everything else supports it. Write the deliverables and their acceptance criteria first, and write them before the price is agreed, because the price depends on them.

• Clause 1: strike one. If there is a master agreement, put in its date, check it is between the same two legal entities rather than a parent or sister company, and read it for the five things clauses 14 to 18 would otherwise cover: ownership, confidentiality, warranties, liability and termination. A thin master agreement that is silent on one of them leaves a gap, because choosing the master-agreement option switches all five off.
• Schedule A: the objective in business terms, the background, and how success gets measured. This is what a court or an arbitrator reads first if the project goes wrong, and it is what tells a new team member what the project is for.
• Schedule B Part 1: one block per deliverable, with criteria that can be tested by someone who was not in the room. "Report delivered in Word, covering the five sites listed, with a recommendation and a cost estimate for each" works. "Professional-quality report" does not.
• Schedule B Part 2: the out-of-scope list. The checklist under it is a prompt, not part of the list, so write in the ones that apply to your project.
• Schedule C: every assumption the dates and prices rely on, and every dependency with a named owner. An assumption with no owner is a risk the provider has accepted without pricing it.
• Schedule D: tick one pricing model and fill in only that part. For time and materials, the ceiling is not optional, and clause 13 makes work above it the provider's risk.
• Schedule E: the client's responsibilities with dates, the named decision-maker, and the review turnaround. Clause 7 defaults to five business days where Schedule E is silent.
• Clause 10: set the acceptance window to something the client's testers can actually meet. Ten business days is the default, and a window nobody can meet leads straight to deemed acceptance, which helps nobody.
• Schedule F: leave the change order form in the document. A change process that requires finding another form is a change process that gets skipped.

Acceptance criteria decide who wins the argument

Most services disputes come down to one question: was the work finished? A statement of work answers it in advance or not at all. Federal contracting worked this out decades ago and wrote it down. Under FAR 37.602, agencies are told to describe work in terms of the required results rather than how the work is to be accomplished or the number of hours to be provided, and to enable assessment of work performance against measurable performance standards. That is a good description of what Schedule B is for. Results, measurably stated, so that finished becomes a question of fact. Three things in clause 10 matter most. It gives the client a fixed window to test against those criteria and nothing else, so a deliverable cannot be rejected for missing a requirement that was never written down. It deems acceptance if the window passes in silence, or if the client puts the work into production, which stops a project hanging unfinished while the client uses it. And after two resubmissions it puts the client to a choice: accept with a fee reduction, direct further corrections at the provider's cost, or end that deliverable and pay for the rest. If you take one thing from this page: write the acceptance criteria before you agree the fee. A fixed price against vague criteria is an open-ended commitment wearing a number.

Assumptions carry the dates

A schedule is a conditional promise. It assumes the client's data is in the format described, that the three approvals arrive on time, that the third-party vendor delivers its part in week two, and that the people named are available. Write those conditions down in Schedule C and the schedule means something. Leave them out and the provider has promised a date while depending on things it does not control. The discipline that makes Schedule C work is giving every dependency a named owner and a date. "Client provides test data" is a dependency. "Client provides test data in the agreed format by 14 March, owned by the client's data lead" is a dependency you can manage, and the one that supports a day-for-day extension under clause 12 when it slips. For the client there is a fair trade here. An assumption-heavy SOW shifts risk back onto you, so read Schedule C as carefully as the price. Anything in it that you cannot actually commit to should be renegotiated now, not discovered in month three.

Fixed fee, time and materials, or milestones

The pricing models carry different risk, and the federal rules describe them more plainly than most commercial contracts manage. A firm-fixed-price arrangement, in the words of FAR 16.202-1, provides for a price that is not subject to any adjustment on the basis of the contractor's cost experience, which places on the contractor maximum risk and full responsibility for all costs and resulting profit or loss. That is the honest description of a fixed fee. It suits well-defined work with testable criteria, and it is the wrong model for discovery work, because the provider prices the uncertainty and the client pays for it whether the risk materializes or not. Time and materials goes the other way. FAR 16.601 allows it only when it is not possible at the time of placing the contract to estimate accurately the extent or duration of the work, and requires a ceiling price that the contractor exceeds at its own risk. Both halves of that matter commercially. Use it when nobody can scope the work honestly, and always with the ceiling, which clause 13 and Schedule D build in. Milestone payments sit between the two and are the usual answer for a longer project: a fixed total, released in stages tied to accepted deliverables rather than to dates or elapsed effort. Tie each payment to acceptance under clause 10 rather than to submission, or the milestone measures the calendar rather than the work.

Change control, or the project quietly loses money

Scope creep is rarely a single large request. It is a sequence of small favors, each one too minor to raise an invoice about, and together the reason a profitable project ends up underwater. The template is deliberately strict about it in clause 11. A change takes effect when both sides sign a change order, or, for an urgent change, when both named approvers confirm it by email under clause 11(d). Each change order states the effect on scope, fees and dates, and work the provider performs outside the SOW without one is its own cost and risk unless the client asked for it in writing. That last sentence protects both sides. The client is not presented with a surprise invoice for work it never approved, and the provider has a clear reason to say that a request needs a change order before work starts rather than after. The clause is rarely the problem. The habit is. Providers skip change orders because raising one feels confrontational early in a friendly project. Make it routine from change order number one, keep the form in the document as Schedule F, and allow the email approval route in clause 11(d) for genuinely urgent changes so the process never becomes the reason work stops.

Who owns the deliverables

Where there is a master agreement, it usually answers this, and the SOW should not try to answer it again. Clause 14 therefore switches off in that case. Where the SOW stands alone, ownership has to be dealt with, and one federal statute governs how. Under section 204(a) of the Copyright Act, a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights conveyed. A handshake, a paid invoice, or a clause saying the client "will own" the work at some future point does not transfer copyright. That is why clause 14 is drafted as the signed written instrument itself, transferring on payment. The other half is what the provider keeps. No consultancy can assign the methods, templates and tools it reuses on every engagement, so clause 14 keeps those as Provider Materials and licenses them to the extent they are embedded in a deliverable. For clients that is the normal position, and the thing to check is that the license is broad enough to use, modify and keep using the deliverable without going back to the provider. If you are buying software, start with our software development agreement instead, which uses a statement of work as its own exhibit and deals with escrow, open-source components and code ownership in more detail.

SOW, work order, or service agreement

These are layers, and each one has a job. A master services agreement or a service agreement holds the legal terms for the relationship. A statement of work defines one project under it, with deliverables and acceptance criteria, which is this template. A work order authorizes a specific job, usually operational or field work priced by visit or by hour, and our work order template covers that. A purchase order commits budget and gets the invoice paid, and it replaces neither, for the reasons in the purchase order FAQ below. The quick test: if the question is what finished looks like, you want a statement of work. If the question is whether a job was done and at what rate, a work order fits. If the question is who carries which legal risk across all the work, that belongs in the master agreement.

Do not let the SOW undermine contractor status

A statement of work for an independent contractor or consultancy has to describe results without taking over the method. That distinction is not drafting fussiness. Worker classification often turns on control: who decides how the work is done, in what hours, with whose equipment, under whose supervision. The tests are not identical, and some state tests do not rely on control at all, so treat this as a reason to keep the SOW clean rather than as the whole of the law. So a SOW that specifies deliverables, acceptance criteria, milestones and a named project lead is on safe ground. A SOW that sets working hours, requires attendance at internal team meetings unrelated to the project, puts the provider's staff under a client manager's day-to-day direction, or forbids other clients is building a record that the relationship is employment. Clause 8 and clause 21 are written for the safe version: the client states the results it needs through Schedule B, the provider controls how they are achieved. This matters most where one contractor works for one client over a long period through repeated SOWs. If what you actually want is a person rather than an outcome, hire them or use a staffing agency. Dressing employment up as a statement of work is the version that produces a back-taxes assessment.

A note on what this page is

This is a general-purpose template and general information, not legal advice. The federal acquisition rules quoted here apply to government contracting and are used on this page because they describe the concepts unusually clearly. They do not bind a commercial deal. Where a master agreement exists, its terms and its governing law control, and this SOW should be read against it. The rules referred to on this page were checked in October 2026. The standalone version deliberately stops short of several terms a full master agreement would carry, including insurance, data protection and security, dispute escalation, and non-solicitation, so add them where the project needs them. For a project of real size, or a first engagement with a new counterparty, have a lawyer read the master agreement and the first SOW together.