Statement of Work Template for Consultants: Write the Deliverables Like You'll Be Disputing Them

A statement of work template for consultants is only worth using if you fill it in as if you will one day have to point at it in a disagreement. Most people fill it in as if they won't, and the template ends up as a polite paragraph that both sides read differently.

The statement of work, or SOW, is the document that says what you will deliver, by when, for how much. It usually sits under a master agreement that covers the legal terms. Consultants often skip the split and put everything in one contract, which is fine for small engagements. The SOW content still needs to be separate in your head, because it is the part that changes with every client.

Deliverables: nouns, not verbs

The most common mistake is describing activity instead of output. "Support the client's marketing strategy" is an activity. Nobody can tell when you are done. "A 12-page written marketing plan covering channel mix, budget allocation and a 90-day calendar, delivered as a PDF" is a thing. You can hand it over, and the client can say yes or no.

For each deliverable, write four things: what it is, its format, its approximate size, and who on the client side receives it. The size matters more than people think. "A report" can be 6 pages or 60. If the client is expecting 60 and you scoped 6, you will have a conversation about it in the final week.

Acceptance: how the client says it's done

This section is the one most templates have as a single line, and it deserves a paragraph. State how long the client has to review a deliverable, say five business days, and what counts as acceptance. Then state what happens if they say nothing. A clause like "if no written feedback is received within five business days, the deliverable is considered accepted" prevents the slow drift where a finished piece sits in someone's inbox for six weeks while your invoice sits unpaid.

Also state how many rounds of revisions are included. Two is typical. Say what a round is: one consolidated set of comments from the client, not a trickle of notes over a week. Without that, "one revision" can mean fourteen emails.

Timeline and dependencies

Dates alone are not enough. Most late consulting projects are late because the client did not hand over something they promised. Interviews not scheduled, data not exported, access not granted.

List what you need from the client and when you need it. Then add one sentence: if client inputs arrive late, the delivery dates move by the same number of days. That sentence feels a bit aggressive when you write it. It reads as completely reasonable to the client, and it saves you from absorbing someone else's delay.

Fees and how they are billed

State the number, the structure, and the trigger. Fixed fee of $9,000, billed 50 percent on signing and 50 percent on delivery of the final report. Or hourly at $150, capped at 60 hours without written approval. Or a monthly retainer of $3,000 covering up to 20 hours.

The trigger is what people forget. "Billed on delivery" is vague if a deliverable can be delivered and then revised. "Billed on delivery of the first draft" is clear. Pick the event and name it.

Expenses go in a separate sentence. Say whether they are reimbursed, whether you need pre-approval above a certain amount, and whether you bill them at cost.

Out of scope, written down

An explicit exclusions list does more than it seems to. It sounds defensive. In practice, it is a conversation you have once, calmly, at the start. "This engagement does not include implementation, vendor selection, or training of client staff." If the client reads that and says, "Wait, I thought you'd help with vendor selection," you have found a gap before it turns into unpaid work.

We wrote about the clause that handles unscoped requests in the post on consulting contract templates and scope creep. The short version is that the SOW should say how new requests get handled, not just what is excluded.

The change order clause

A change order is a short written addition to the SOW. The client asks for something outside the scope. You write one paragraph describing it, its price, and its effect on the timeline. They sign it. Then you do it.

Put the process in the SOW itself: changes must be agreed in writing before work starts, and the consultant is not obligated to begin work on a request until the change order is signed. Then actually use it. A change order clause that you waive three times teaches the client it is optional.

Keep the paperwork light. A half-page email thread that both sides confirm is a change order, if your SOW says so. Nobody needs a formal amendment for four extra hours.

What a template cannot do

A template gives you the headings. It cannot tell you whether "a strategy deck" means 15 slides or 40. That is your judgment, and it comes from having done the work before. If you have run three similar engagements, go back to them and look at where the friction was. Then add a line to your template for each one.

Also, a signed SOW is only useful if you can find it. Plenty of consultants have a signed PDF somewhere in an email thread and no clear link between the document, the hours logged against it, and the invoices that followed. When a question comes up in month four, you want the scope, the time entries and the billing in front of you at once.

That is the part FocalVA for consultants and creatives tries to cover: the contract, the e-signature, the logged hours and the invoices in one place for each client. It does not write your deliverables for you. That bit is still your job, and it is the part that matters most.