Free scope & change-order generator
Lock the scope. Bill the extras.
Write a scope of work with a real out-of-scope list, get it signed, then generate a priced change order the moment the client asks for more. No account, no sign-up wall.
Live preview
Scope of Work
Scope of Work
[Project name]
- Provider
- [Your name / business]
- Client
- [Client name / business]
- Date
- 9 September 2026
Overview
[One or two sentences on what this project delivers and why.]
In scope
- [List each deliverable on its own line.]
Out of scope
- [List what this project explicitly does not cover, so a later request is clearly a change.]
Fee and payment
Changes to this scope
Anything not listed as in scope is out of scope. A request that adds to or changes the scope is handled with a written change order, priced and agreed before the work starts.
Provider
Signature · Date
Client
Signature · Date
The downloaded PDF carries a small line noting it was generated with StitchInvoice, and that it is a starting template, not legal advice. Nothing here is saved or sent anywhere. Your draft stays in this browser until you download the PDF.
Keep scope and change orders next to the invoice
In StitchInvoice a signed scope becomes the reference every change order points back to, an approved change drops onto the next invoice automatically, and a tracker flags when a client request has crossed the line.
What to include
What actually belongs in a scope of work.
An overview a client can read in ten seconds and know what they are buying
In-scope items listed one by one, not folded into a paragraph
An out-of-scope list, the half most scopes skip and the half that stops arguments later
A timeline, even a rough one, so "late" has a reference point
The fee and payment terms on the same document as the scope, not in a separate email
A sign-off block, so an agreed scope is a signed scope
Why bother
Scope creep is ten small asks, not one big one.
Each request feels too minor to bill for, so it gets absorbed, and a profitable project quietly turns into a break-even one. A named out-of-scope list makes every one of those a clear change order instead of a favour.
Questions
Common questions about scopes and change orders.
What belongs in a scope of work?
An overview, a list of in-scope deliverables, an explicit out-of-scope list, a timeline, the fee and payment terms, and a place for both parties to sign. The out-of-scope list is the part most templates leave out, and the part that prevents the most disputes. A change order then handles anything that list turns up later.
What is the difference between a scope of work and a contract?
The contract sets the legal terms: payment, liability, IP, what happens if it ends. The scope of work says exactly what is being delivered. They often travel together: the contract references the scope, and a change order amends the scope without touching the contract.
When should I raise a change order instead of just doing the work?
The moment a request falls outside the in-scope list. A change order is not a confrontation. It is a short document that says what is being added, what it costs, and what it does to the deadline, so the extra work is agreed and paid rather than absorbed.
Why does an out-of-scope list matter so much?
Because scope creep is rarely one big ask. It is ten small ones, each of which feels too minor to bill for. An explicit out-of-scope list turns each of those into a clear, unarguable change, which is the difference between a project that stays profitable and one that does not.
Is this a legal document?
It is a business document that becomes binding when both parties sign it, especially where a contract already references it. It is a solid starting template, not legal advice, so read it against your own engagement.
Where is my data stored?
Your draft stays in your own browser. When you download a PDF, the details are sent to StitchInvoice only to render the document, which is streamed straight back. Nothing is saved on our side.
A change order is only useful if it reaches the invoice.
In StitchInvoice the signed scope is the reference every change order points back to, and an approved change drops onto the next invoice automatically, so nothing agreed gets forgotten at billing time.