You finished the project on a Tuesday. The brief said two pages. You ended up shipping six. The client paid the original number and you sat there at 9pm trying to remember when "two pages" became "the full thing".
You promised yourself the next contract would be tighter. The next one slipped the same way.
Quick honest note before we start. I am not a contracts lawyer, and I am not selling you a legal template. I am a dev who builds DocsAura, and I keep watching freelancers sign documents that look airtight and then bleed for six weeks. So I asked a few agency owners and consultants what they actually write in their SOWs to stop the bleed, and I put the nine most useful checks on one page.
This is for the freelancer or small studio who signs fixed-scope deals and quietly absorbs the overrun. You will leave with a checklist you can run through in 10 minutes before any kickoff, and nine copy-paste lines you can drop straight into the SOW or the kickoff thread.
Check 1 — Pin the count and the format on every deliverable
The proposal says "a website". A website is a black hole. Three pages, eight pages, a sitemap, a CMS, a landing page funnel — all of these are "a website" in the client's head.
Write the count and the format on every line. Pages, screens, posts, emails, revisions, file types. Concrete nouns the reader can point at.
Deliverables: 5 page designs (Figma, desktop + mobile), 1 brand stylesheet PDF, 1 component library handoff (Figma file). Anything outside this list is a paid change order.
Let's say the client comes back two weeks in: "Can we also do the careers page?". You point at the line. "Happy to — that is page 6, here is the change order." No drama. Five seconds.
Check 2 — State the source-file rule on day one
Half of scope creep is invisible — it happens after the project ends. The client asks for the editable file. You hand it over. Three months later they redesign half of it themselves, then email you when it breaks.
Decide in writing whether source files are included, locked, or paid extra.
Source files: final Figma file delivered on full payment. Editing and post-handover support is billed at the hourly rate listed in section 4.
Let's say a logo project ends and the client wants the AI file. If you priced for the design, not for the file, charge for the file. It is a separate thing, and the contract says so.
Check 3 — Cap the rounds, define what counts as a round
"Two rounds of revisions" sounds firm. It is not. A round is whatever the client says it is — a Friday email with seventeen comments, a Tuesday Slack thread with three more, a Wednesday note about the footer.
Write what a round is and what closes it.
Revisions: 2 rounds per deliverable. A round is one consolidated feedback document from the client per deliverable, sent within 5 business days of delivery. Comments sent after a round is signed off are treated as a new round and billed at the change rate.
Let's say you deliver the homepage on Monday. The client sends three notes Monday, two more Wednesday, four more Friday. Without a definition that is three rounds of you re-opening the file. With the rule it is one — wait, consolidate, send it back.
Check 4 — Name the feedback-givers by name
You priced the project for one decision-maker. The kickoff happens. By week three you are on a call with the founder, their co-founder, their head of marketing, and someone called Marcin who "is great with words". You are now redesigning for four taste profiles.
Write the names of the people who can give feedback. Cap the number.
Approvers: feedback consolidated by [Client Name], delivered as a single document per round. Up to 2 stakeholders may contribute notes. Any additional reviewer requires a written change order.
Let's say a fifth voice shows up on Slack on Tuesday with redesign opinions. You message back: "Happy to fold these in — can [Client Name] confirm this as a new round? Otherwise I will send back the agreed version Friday." The boundary is on paper, not in your head.
Check 5 — Write the "not included" line
What is in scope is half the contract. What is not in scope is the other half. Most SOWs only write the first half.
Add a 3 to 5 line "not included" section right under the deliverables. List the things the client will probably ask for and assume.
Not included: copywriting for any page, SEO research, asset sourcing (stock photos, icons), legal copy, CMS build, hosting setup, ongoing maintenance. Any of these can be added as a paid scope addition.
Let's say two weeks in the client writes "while we are at it, can you write the about page". You reply with the not-included line and a price. No argument — it was on the page they signed.
Check 6 — Set the asset delivery window
You priced a 4-week project. Week 1 you wait for the brand guidelines. Week 2 you wait for the product copy. The project runs for 9 weeks and you still hit the original deadline because the client expected to.
Write when the assets are due, and what happens when they are late.
Asset window: client provides brand assets, copy, and approvals within 5 business days of request. Delays beyond 5 days extend the project deadline day-for-day and may incur a re-engagement fee if total delay exceeds 14 days.
Let's say the client takes 3 weeks to send the copy. Your delivery date moves 3 weeks. You did not eat the slip — the contract did. And the re-engagement fee covers the cost of context-switching back into a paused project.
Check 7 — Set the approval window the same way
Asset window protects the start. Approval window protects the middle and the end. Without it, the client can sit on round 1 for three weeks and then ask why the project is late.
Approval window: client signs off on each round within 5 business days of delivery. Rounds left unsigned beyond 5 days are considered approved and the project moves to the next phase.
Let's say you ship round 1 Monday. Friday comes, no response. Next Monday — still nothing. The clock runs out, and you can move on to round 2 without burning a week of your calendar waiting. Tell them upfront so it is not a surprise.
Check 8 — Define the change-order trigger
"It is just a small tweak" is the most expensive sentence in your project. Without a trigger written down, every request lives in a grey zone, and the grey zone is where you lose money.
Write what triggers a change order in concrete terms.
Change order trigger: any request that (a) adds a deliverable not listed in section 2, (b) changes a deliverable after sign-off, or (c) requires more than 4 hours of additional work. Triggered changes are quoted in writing within 2 business days and require client approval before work begins.
Let's say the client asks to "tweak" the homepage hero — and the tweak is a full redesign of three sections. You write: "This falls under (b) — change to a signed-off deliverable. Quote attached, 6 hours. Confirm and I will start Friday." No frustration, no friction. Just a line of paper.
Check 9 — Define what "done" looks like, in writing
Most projects end on a vibe. The client stops replying, you stop chasing, and three months later they email about something you thought was wrapped. Write the close.
Sign-off: project completes when (a) all deliverables in section 2 are delivered, (b) the client sends written sign-off, or (c) 7 business days pass after final delivery with no response. After sign-off, any further work is billed at the post-project hourly rate.
Let's say you deliver the final round Friday. The client goes quiet. Seven business days later, the project closes itself per (c) and you send the final invoice. No awkward "are we done" email — it is already done.
A worked example, end to end
Let's say you are signing a $9,000 brand identity project. Logo, stylesheet, three social templates, one pitch deck template.
You run the 9 checks. The SOW comes out looking like this:
- Deliverables: 3 logo concepts → 1 chosen → final logo in 4 formats (.ai, .svg, .png, .pdf). 1 stylesheet (PDF). 3 social templates (Figma). 1 pitch deck template (Figma + PowerPoint export).
- Source files: final Figma file delivered on full payment.
- Revisions: 2 rounds per deliverable, 1 consolidated feedback per round, 5 business day window.
- Approvers: [Client] consolidates feedback; up to 2 stakeholders contribute.
- Not included: copywriting, stock asset sourcing, motion variants, video, animated logo, additional formats beyond the 4 listed.
- Asset window: 5 business days for client deliverables.
- Approval window: 5 business days per round.
- Change-order trigger: any new deliverable, post-sign-off change, or anything over 4 extra hours.
- Sign-off: all deliverables delivered + written approval, or 7 business days post-final with no response.
Three weeks in, the client asks for an animated version of the logo. You reply: "That is not in section 2 and falls under the change-order trigger. Quote: 3 hours, $X. Confirm and I will deliver Friday." They confirm. You bill the change.
The project finishes on schedule. The final invoice clears in 8 days because there is no grey-zone work left to argue about.
What to avoid
Trying to handle scope creep with personality. "I am sure we can figure it out" is not a clause. Friendly negotiation works for one or two asks. The fifth ask compounds. Paper handles compounding; goodwill does not.
Writing the SOW after the proposal is approved. The SOW is the proposal. If your proposal does not have these 9 lines in it, the client has already imagined a different scope by the time you send the contract.
Leaving "scope" as a single noun in the doc. "Project scope" is too abstract for the client to push back on. Break it into the 9 boxes above. Then push happens line by line, not at the whole project.
Skipping the "not included" section because it feels negative. It does the opposite. Clients prefer reading what is not included because it tells them where the edges are — silence is what makes them wander past the edge.
Treating sign-off as a vibe instead of a clause. If you cannot point at the moment the project ended, neither can the client — and neither can your accountant when chasing the final invoice.
A 10-minute checklist before you send the contract is cheaper than a 60-hour overrun after.
Ready to stand out?
Your competitors are still sending plain-text proposals and Word docs. You don't have to. Drop a brief, get a beautiful HTML document — free, no signup required.