How to Write a One-Page Scope of Work Clients Can Say Yes To

What a scope of work is for

A scope of work says exactly what you'll deliver, what "done" means for each item, what's not included, what you need from the client, and how changes are handled. It's the page you both point to when a question comes up.

It's a different job from the proposal. The way I see it, the scope is separate from the brief, which is strategic, and the proposal, which sells. Many small businesses put the scope inside their fixed-scope proposal. That works as long as the scope section is complete.

A clear scope prevents misunderstandings. It won't prevent every dispute, and it isn't a legal contract. Keep legal terms in a separate document.

Write the outcome and the deliverables

Start with one sentence: what the client will have when the work is done. Then list each deliverable with:

• Quantity and format. "Five pages of website copy, delivered as an editable document."
• Done means. "Done means two review rounds completed and final copy approved by email."
• Review rounds. The number included, stated once.

How detailed? Detailed enough that someone could tell what you will and won't deliver. If a line can be read two ways, rewrite it. If it lists your internal tasks, cut it back to deliverables.

If you sell a productized service, most of this page already exists in your always-in list.

Write the not-included list

Clients skim and assume. A short not-included list turns a later argument into a pointer to a line you both saw. If you're thinking "of course that's not included," write it anyway.

Common exclusions to consider:

• Adjacent work that sounds close but is a separate job.
• Open-ended support after handoff.
• Extra revision rounds.
• Content the client supplies. I'd write "Client supplies all content" into almost every scope.
• Third-party costs such as software, stock assets, or ads.

Kit & File's services page shows exclusions written without apology. One reads: "No unlimited revisions or fulfillment of the client's own service."

Name what you need and how changes work

List the client's side of the work. Most of it should already be in your discovery call notes.

• List the inputs and files, with dates.
• Name the accounts or tools you need, and who grants access.
• Name who approves each deliverable.
• Set the review windows. Even the smallest scope needs a timeline with review windows. Add one line saying late feedback moves the delivery date.

Then the change rule, in one sentence: "Requests outside this scope are quoted separately before work starts." When a request does arrive mid-project, the out-of-scope guide covers the reply.

Add the price reference and a written yes

Reference the price and payment schedule in one line. The terms themselves belong in your payment terms.

End with one plain acceptance step: "Reply 'approved' to confirm," or a signature. Don't start work until it comes back. Kit & File runs the same order: written scope, accepted in writing, then the invoice, and work after cleared payment.

The one-page template

• Outcome: one sentence.
• Deliverables: item, quantity, format, done means.
• Not included: three to six lines.
• Client provides: inputs, access, approver, dates.
• Timeline: stages, review windows, and the late-feedback line.
• Revisions: rounds included.
• Changes: quoted separately before work starts.
• Price: reference and payment schedule.
• Acceptance: "Reply 'approved' to confirm."

Illustrative example (fictional)

A bookkeeper scopes a cleanup. The outcome is "twelve months of transactions categorized and reconciled". Done means "reconciled reports sent and walked through on one call". Not included: "tax filing, payroll, and ongoing monthly bookkeeping". The client provides "bank access and receipts by the 5th".

Once it's approved, the scope is what you restate when you onboard the client and what you hand off at closeout.

Fill the gaps on paper before the client fills them with assumptions.