Change Order Scope Description Example
Use this change order scope description example to write contractor documentation that separates original scope, changed work, exclusions, price, and approval action.
When to use this
Use this example when a change order is weak because the changed scope is too vague.
It helps contractors write the scope description so the client can see exactly what is changing.
What to document
- The original scope item being changed.
- The new or revised work in concrete jobsite language.
- What is excluded, assumed, or dependent on selections or field conditions.
- Price and schedule impact tied to the changed scope.
- The approval action needed before the changed work begins.
Scope description structure
Use this structure to turn vague change language into a clearer contractor scope description.
Before writing
Scope wording
Client action
Approval boundary
Templates help you write the request. StackQuotes helps you keep the approval record tied to the job.
Clear scope description example
- Weak wording
- Add plumbing changes in bathroom.
- Better wording
- Relocate vanity water supply and drain lines approximately 36 inches to align with owner-selected vanity layout.
- Boundary
- Excludes drywall patching beyond opened wall area unless concealed conditions require additional access.
CTA
Use StackQuotes when scope wording, pricing, and approval action need to stay connected.
How to use this
Write the changed scope before pricing it so the price matches a defined piece of work.
Use exclusions and assumptions to keep the change from absorbing unrelated work.
Attach the scope wording to the approval request and keep the approved wording with the job record.
Approval boundary
Templates help you write the request. StackQuotes helps you keep the approval record tied to the job.
StackQuotes does not guarantee payment or prevent every dispute. It helps contractors preserve the request, pricing context, client action, and job record in one place.
This is general business documentation guidance, not legal advice. For legal disputes, lien rights, or contract enforcement questions, talk with a qualified construction attorney in your state.
Common mistakes
- Writing changed scope as a short label instead of a work description.
- Leaving exclusions out because the contractor assumes they are obvious.
- Approving a price without preserving which scope version the price covers.
- Mixing original scope and extra work in the same sentence.
FAQ
When should a contractor use this scope example?
Use this example when a change order is weak because the changed scope is too vague.
What does it help document?
It helps document changed scope, price or schedule impact, supporting facts, and the client action needed before work continues.
What goes wrong if this is not documented?
The contractor may be left reconstructing scope, price, timing, or approval from memory, messages, and invoices after the job has already moved on.
Is this legal advice?
This is general business documentation guidance, not legal advice. For legal disputes, lien rights, or contract enforcement questions, talk with a qualified construction attorney in your state.