When should a contractor use this request template?
Use this template when a possible change has been identified but still needs scope, pricing, or client action.
Change Order Request Template
Use this change order request template to document a contractor request before pricing, approval, and extra work become mixed together.
When to use this
Use this template when a possible change has been identified but still needs scope, pricing, or client action.
It helps contractors document the request before it turns into extra work performed without a clear record.
What to document
- Who requested or identified the change and when it was raised.
- Original scope affected by the request.
- Requested change, reason for change, and supporting notes or photos.
- Whether pricing, schedule review, or client approval is still pending.
- Next action needed before the work continues.
Printable change order request
Use this request format before preparing the final price or approval form.
Request source
Requested by: ______________________________
Date requested: ____________________________
Project or job address: ____________________
Original scope affected: ___________________
Requested change
Requested change: __________________________
Reason for request: ________________________
Photos or attachments: _____________________
Open questions: ____________________________
Next action
Pricing needed: yes / no
Schedule review needed: yes / no
Client approval needed: yes / no
Next step owner: ___________________________
Approval boundary
Templates help you write the request. StackQuotes helps you keep the approval record tied to the job.
Change order request example
- Request
- Owner asks to add under-cabinet lighting after cabinet layout approval.
- Next action
- Contractor to price fixtures, wiring, switch location, and drywall impact.
- Boundary
- Request is not approval to proceed; approval happens after price and schedule impact are sent.
CTA
Use StackQuotes when change requests need to move from field notes to documented approval records.
How to use this
Capture the request as soon as it is raised, even if price is not known yet.
Use the request to gather pricing, schedule, and scope details before sending an approval form.
Close the loop by tying the final approval or rejection back to the original request.
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
- Treating the initial request as approval to perform the work.
- Waiting to document the request until after the work is complete.
- Failing to identify which original scope item is affected.
- Losing the request source when pricing and approval happen later.
FAQ
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.
Related resources
Construction Change Order TemplateUse the broader change order template when the request needs scope, price, schedule, and approval fields together.Contractor Change Order FormUse a simple contractor form when the change needs a client-facing approval artifact.Contractor Change OrdersReview how contractors should separate changed scope from the original proposal and approval record.Run Better resourcesSee how StackQuotes keeps job records, change requests, and approval actions organized around the job.Change Order Risk CheckerCheck whether scope, price, schedule, and client-action details are missing before work continues.Proposal Scope ScannerScan proposal scope for unclear language that can turn into change order disputes later.What Happens Without a Signed Change OrderUnderstand the operational risk when extra work is not tied to a clear approval record.Run Better resourcesUse StackQuotes to preserve the request, pricing notes, and approval trail together.