Change orders
SOW exclusions for freelancers
A clear in-scope list and a short exclusions list. Extra asks become change orders instead of unpaid work.
More guides sit on the guides index.
Short answer
What should a freelance SOW exclusions list include?
List what you will deliver, then list what you will not. Common exclusions: extra revision rounds past a cap, new stakeholder restarts, source files, rush weekends, meetings past a set number, and third-party costs. Say that anything not listed needs a written change order before work starts.
Why exclusions belong in the SOW
Clients fill silence with assumptions.
A short exclusions list sets the edge before kickoff.
Write in scope first
Name deliverables, formats, and revision rounds included.
Name meeting count if you cap meetings.
Then write what is out
Examples: extra pages, extra revision rounds past two, new brand directions after approval, source files, stock licenses, weekend rush, unlimited stakeholder workshops.
One line: anything not listed needs a written change order first.
Link to the change-order path
When an exclusion is requested, use how to write a change order and how to price it.
Cap meetings separately with meeting caps in the SOW.
Related pages
Change order template · Scope creep examples · Change orders hub
If you want tools later
You do not need these to use the guide. One-time files.
Also: change-order email page · blank change-order template · Payhip store
FAQ
Is an exclusions list hostile?
No. Clear edges protect the relationship.
How long should the list be?
Short enough to read. Cover the asks you see most often.
Not legal advice. Match your contract and local rules. This is a process aid, not a lawyer.