Change Order Tracking Spreadsheet

Use this change order tracking spreadsheet structure to track contractor requests, pricing, client action, approval records, invoices, and documentation gaps.

Use StackQuotes for the approval record

When to use this

Use this spreadsheet when a job has multiple change requests and the contractor needs a clear log.

It helps track work-in-progress documentation, but the spreadsheet status column should not be treated as approval proof.

What to document

  • Change order number, request date, source, affected scope, and person responsible.
  • Price, schedule impact, sent date, client response, approval evidence, and invoice reference.
  • Open documentation gaps that must be resolved before work continues or before invoicing.
  • Links to photos, worksheets, emails, forms, or StackQuotes records.
  • A clear distinction between tracking status and actual client approval evidence.

Spreadsheet column template

Use these columns in a spreadsheet or copy them into your job tracking system.

Core columns

CO number
Date opened
Request source
Affected original scope
Changed scope summary
Owner/client contact

Pricing and schedule

Estimated price
Approved price
Added working days
Pricing worksheet link
Assumptions or exclusions

Approval and billing

Request sent date
Client action received
Approval evidence link
Invoice number
Documentation gaps

Approval boundary

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

Tracking row example

CO-004
Owner requested cabinet hardware upgrade after original selections.
Tracking note
Request sent May 10; approval evidence saved; invoice reference INV-118.
Documentation gap
Supplier quote attached, but schedule impact still needs client-facing note.

CTA

Use StackQuotes when the log needs supporting records, not just a row that says a change is approved.

How to use this

Add a row when a change is raised, not after the job is already invoiced.

Update the row only from actual records: request sent, client action, worksheet, field note, or invoice.

Use the spreadsheet to find gaps, then keep the underlying approval evidence 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

  • Using a status column as the only proof of approval.
  • Not linking rows to actual emails, forms, photos, or approval records.
  • Combining pending requests and approved changes without clear evidence.
  • Waiting until final billing to reconstruct the change order history.

FAQ

When should a contractor use this spreadsheet columns?

Use this spreadsheet when a job has multiple change requests and the contractor needs a clear log.

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.