A scope of work format template, filled in as a sample.
Scope of work templates are easy to find online. What's missing from nearly all of them is the format itself, the file type, the length, the order of sections, not just the fields to fill in. This one covers that, with a full example already filled in and ready to copy.
A scope of work format works when three things are fixed before you start typing: the file type, the length, and the order the sections come in. Use an editable format such as Google Docs or Word rather than a PDF until the document is signed, keep it to two to four pages for a single project, and run the sections in the same order every time, so a client who reads three of your scopes in a year never has to relearn where anything lives. The filled-in example below follows that exact format, ready to open as a Google Doc and copy.
Most of the templates you can download stop at the section names. You get a blank box labeled "Deliverables" and another labeled "Exclusions," with the file type, the page count and the order left entirely up to you, which is exactly the part that decides whether the finished document reads like professional paperwork or a draft somebody rushed together the night before. A few templates throw in a filled-in example, but it's usually for a project so different from yours that it only shows you the shape, not the format decisions that actually matter.
What file format should a scope of work actually be in?
Use an editable document, Google Docs or Word, for every scope of work until the moment it gets signed, and save the PDF export for that signed copy alone. A PDF looks finished, which is exactly the problem. The client can't suggest a change to a line without emailing you a paragraph describing where it is, you retype it in the source file, and you export a second PDF nobody can easily tell apart from the first.
A shared Google Doc, or a Word file with track changes turned on, lets the client comment directly on the sentence they're questioning, and you both watch the document settle into its final version in real time instead of trading attachments named final, final2, and final-actually-final. That single switch, from a static file to an editable one, removes most of the back-and-forth that makes a scope of work take two weeks to close instead of two days.
Excel earns a place only in the appendix, never in the body. A rate card, a list of milestone dates, or a matrix of what's included by project phase reads better as a table your client can filter than as a paragraph they have to parse. But the scope itself, the section explaining what you're building and why, belongs in a document, not a spreadsheet. Keep the two files separate and reference the appendix by name inside the scope, rather than merging everything into one workbook nobody wants to open on a phone.
How long should a scope of work be, and what order do the sections go in?
Two to four pages for a single project, built from the same seven sections in the same order every time, because consistency is what makes the format reusable instead of something you reinvent for every client.
- Background and objective
- Deliverables, numbered and countable
- Timeline, with the client's own dependencies named
- Exclusions, each one with a price attached
- Revision limit, and the rate that applies once it runs out
- Change-control paragraph
- Approval line, with a named signer and a date
Longer than four pages, and most clients stop reading before the exclusions section, which is the one paragraph in the whole document actually protecting your margin. Shorter than two pages, and you've probably folded the timeline into the deliverables or skipped exclusions altogether, and both of those show up as disputes in month two rather than as a shorter read now.
The order matters as much as the length. A client who signs three scopes from you over a year starts to recognize the shape of the document the way they recognize an invoice, and that familiarity is doing quiet work: they read the exclusions section on the second scope because they remember it mattered on the first one. Reorder the sections every time and you lose that entirely, and every scope reads like the first one again.
What does a properly formatted scope of work look like, filled in?
Here's the format above with real content in every line, not just described: a complete scope of work for a $6,400 brand style guide project, small enough to fit here in full rather than trimmed for space. Anything in brackets belongs to this specific engagement and gets swapped for your own. Every other line is a working default, not a blank left for you to fill in.
Client: Bramble & Rye Coffee Co.
Project: Brand style guide
Version: v1
Date: [date this version was sent]
Status: [draft / sent for review / signed]
1. BACKGROUND AND OBJECTIVE
1.1 Bramble & Rye is opening its ninth location, and the identity built for the first store in 2019 no longer holds up across signage, packaging and a growing social presence.
1.2 The objective is a single style guide the in-house team can apply to new locations without calling us for every one.
2. DELIVERABLES
2.1 Updated primary and secondary logo lock-ups, delivered as vector files.
Done when: both lock-ups are approved in writing.
2.2 A color palette with hex, CMYK and Pantone values for five colors.
Done when: the palette is approved in writing.
2.3 A typography system naming two typefaces and their use across headings, body text and signage.
Done when: approved in writing.
2.4 A 12-page style guide PDF covering logo usage, color, type and one packaging mockup.
Done when: delivered and approved in writing.
3. TIMELINE
Kickoff: [date]. Four working weeks, contingent on [client] supplying existing brand assets and any prior guidelines at kickoff.
Palette and type approved: end of week two.
Full guide delivered: end of week four.
A late approval from [client] moves every later date by the same number of business days.
4. EXCLUSIONS
4.1 Packaging production files beyond the one mockup in 2.4 are $450 per item.
4.2 Signage production files are $600 per location.
4.3 Photography and stock licensing aren't included.
5. REVISION LIMIT
Two rounds of feedback are included across every deliverable in section 2. A third round is billed at $135 an hour, quoted before we start.
6. CHANGE-CONTROL PARAGRAPH
Anything not listed in section 2 is a change, however it arrives. We reply within two business days with the price and the schedule effect, and work starts once the named approver accepts in writing.
7. APPROVAL (starts on its own page)
I approve version [v#] of this scope of work for the work described in sections 1 to 6.
Name: ______________________
Title: ______________________
Date: ______________________
Version approved: ______________________
Signature: ______________________
The document control header at the top is the piece every downloadable template leaves out entirely, and its six lines do more work than they look like they should. A scope with a version number on it tells a client exactly which copy they're looking at when three drafts have gone back and forth over two weeks. A scope without one is the reason agencies end up arguing over whether the client signed version two or version three of a document that looks identical either way.
Formatting carries down to the sentence level too. A deliverable written as "brand style guide" is a section name, not a formatted line, the same way "homepage design" would be. Section 2.1 above works because it can be numbered, dated and priced: if a line in your own scope can't do at least one of those three things, it hasn't been formatted yet, it's only been typed. The same document, ready to edit and reuse for your own client, is one click away as a Google Doc.
Where do the signature, date and version lines go?
Section 7 starts on its own page at the very end, never squeezed in under the change-control paragraph, and it carries four fields stacked under the sentence being agreed to: the signer's name, their title, the date, and the version number they're approving, with the signature line last.
Putting the approval block on its own page matters more than it sounds like it should. A client who has to scroll past the tail of another section to reach the signature line often signs without rereading what's directly above it, and the clause they skipped is the one that becomes an argument in month three. A page with nothing on it but the sentence and those five lines forces a pause, and that pause is doing real work.
A scope without a version number is the reason agencies argue over which draft the client actually signed.
The version approved field is what closes the loop the document control header opened. A client who writes "v3" on that line leaves no room to later claim they signed a different draft, because the number sitting above their signature matches the number in the header on page one. None of the popular downloadable formats include that field. They stop at name, signature and date, which is enough for the document to look signed, but not enough for it to settle a disagreement about which version was actually agreed.
Does the scope of work format change for a marketing, software or website project?
The seven-section shape above stays fixed across every vertical. Only the content inside deliverables, exclusions and the change-control paragraph changes with the kind of work.
A marketing retainer scope keeps the same document control header and the same signature page, but swaps the deliverables section for monthly counts and adds a clause naming who owns the ad accounts, filled in against a real $9,400-a-month engagement in the marketing scope of work template. A software build keeps the format and adds acceptance criteria to every feature line, filled in against a $64,000 internal tool in the software development scope of work template. A website rebuild adds a breakpoint list and separates template count from page count, filled in against a $38,500 fourteen-page site in the website development scope of work template. Each one is the same format wearing different content, which is the entire point of fixing the format first: once the shape is set, filling in a new vertical is an afternoon of writing rather than a redesign.
For a general project scope with deliverables and priced exclusions but no vertical-specific clauses, the project scope template carries the fullest worked example, and how to write a scope of work clients can't misread covers the sentence-level wording inside each section in more depth than a format piece has room for.
The version line every format is missing
Everything above serves one field on the last page, the one where the client writes which version they're approving directly above their signature. Every other format decision, the file type, the page count, the section order, the document control header, exists to make that single line true and unambiguous once a client signs it.
Skip the version number, and the other six sections can be flawless while the document still can't answer the only question that matters once a dispute starts: which copy did the client actually agree to. Add it, and paperwork built from a free downloadable template with none of this in it turns into something that actually settles the argument instead of restarting it. That single line is worth more than the other six sections combined, and it costs nothing to add to a document you're already writing. Docket keeps that version number and the approval attached to a permanent record automatically, which is the same job this format performs on paper, just harder to lose.
Frequently asked questions
What is the right scope of work format, Word, PDF, or Google Doc?
Use an editable format, Google Docs or Word, while the document is still being reviewed, and export the signed version to PDF only at the very end. A PDF looks finished, but it blocks the client from commenting directly on the line they're questioning, which slows down exactly the conversation you want to move quickly.
How many pages should a scope of work be?
Two to four pages for a single project scope. Shorter usually means the exclusions or the timeline got folded into another section, and longer usually means the document has drifted into proposal language instead of staying a scope. A marketing or software scope with more clauses can run slightly longer, but the seven-section shape should still fit inside four pages before any appendix.
What order do the sections of a scope of work go in?
Background and objective first, then deliverables, then the timeline, then exclusions with a price on each one, then the revision limit, then the change-control paragraph, and the approval line last on its own page. Keeping the order fixed across every client scope means you're never redesigning the document, only refilling it.
Where does the signature go on a scope of work?
On its own final page, never sharing space with the end of another section, under four fields: the signer's name, their title, the date, and the version number of the document they're agreeing to, with the signature line last. Naming the version in that block is what lets you prove later which draft was actually signed.
Does the scope of work format change for different types of projects?
The seven-section shape stays the same. What changes is the content inside deliverables and exclusions, for example ad account ownership on a marketing retainer or acceptance criteria on a software build. The format is the constant, and the clauses inside it are the variable.
Can I reuse the same scope of work format for every client?
Yes, and reusing it is the entire benefit. A fixed format means every scope you send takes less time to draft than the last one, and a client who has read one of your scopes recognizes the shape of the next one immediately, which reads as more professional than a document redesigned from scratch each time.