Change Order Documentation Checklist

Use this change order documentation checklist to make sure a contractor captures scope, cause, price, schedule, client action, and approval record details.

Use StackQuotes for the approval record

When to use this

Use this checklist before sending a change order, before starting extra work, or before invoicing a changed scope item.

It helps contractors catch missing documentation while the facts are still fresh.

What to document

  • The original scope, the changed scope, and the reason the change exists.
  • Photos, field notes, messages, measurements, selections, or supplier information.
  • Pricing basis, schedule impact, assumptions, exclusions, and client action requested.
  • Approval response and where that response is stored in the job record.
  • Any unresolved dispute, rejection, or revision that must not be treated as approval.

Printable documentation checklist

Use this checklist as a pre-send or pre-invoice review for change order paperwork.

Before sending

[ ] Original scope identified
[ ] Changed scope described
[ ] Reason for change documented
[ ] Photos or field notes attached

Pricing and schedule

[ ] Labor and materials priced
[ ] Subcontractor costs attached if used
[ ] Markup or overhead included
[ ] Schedule impact stated

Client action

[ ] Approval request sent
[ ] Client response saved
[ ] Revision or rejection documented
[ ] Final approved version tied to job record

Approval boundary

Templates help you write the request. StackQuotes helps you keep the approval record tied to the job.

Checklist review example

Missing item
Client selected upgraded fixture, but the selection message was not attached.
Correction
Attach the selection message before sending the price for approval.
Record impact
The final approval references the selected fixture, price, and added lead time.

CTA

Use StackQuotes when the change order record needs to outlast inbox threads, text messages, and verbal field updates.

How to use this

Run the checklist before asking for approval so missing facts do not create a weak request.

Run it again before invoicing a change order if the work, price, or schedule changed after approval.

Save the completed checklist with the job record when the change carries payment risk.

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

  • Checking only the price and ignoring why the scope changed.
  • Saving photos without connecting them to the change order request.
  • Treating a completed checklist as approval.
  • Waiting until payment is disputed to collect field notes.

FAQ

When should a contractor use this checklist?

Use this checklist before sending a change order, before starting extra work, or before invoicing a changed scope item.

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.