Change Order Log Template

Use this change order log template to document contractor change requests, pricing, client action, approval evidence, invoices, and unresolved gaps.

Use StackQuotes for the approval record

When to use this

Use this log when several change orders are open, pending, approved, rejected, or invoiced on the same job.

The log helps contractors see the job record, but each row still needs underlying request and approval evidence.

What to document

  • Change order number, title, source, request date, and original scope affected.
  • Price, schedule impact, sent date, client action, and record location.
  • Approval evidence, rejection response, revision history, and invoice reference.
  • Open documentation gaps and who owns the next action.
  • Notes that distinguish tracking labels from actual approval records.

Change order log fields

Use these fields as a log table for active and completed change orders.

Identification

CO number
Short title
Request source
Date opened
Original scope affected

Financial and schedule

Proposed price
Approved price
Schedule impact
Pricing backup link
Invoice reference

Record evidence

Request document link
Client action link
Revision or rejection note
Open documentation gap
Next action owner

Approval boundary

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

Change order log example

CO-007
Add attic access trim after inspection request.
Record
Request document, pricing worksheet, client approval email, and invoice reference saved.
Gap
Inspection note attached; final photo still needed for closeout record.

CTA

Use StackQuotes when each log row needs supporting request, pricing, and approval records.

How to use this

Create the row when the request opens, then connect actual documents as they are created.

Use the log to identify missing approvals, pricing backup, or invoice references.

Do not rely on the log alone if a payment or scope question comes up.

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 a log status as proof that the client approved the work.
  • Not linking the log to actual forms, emails, photos, or pricing records.
  • Mixing proposed prices and approved prices in the same field.
  • Ignoring rejected or revised requests when billing the job.

FAQ

When should a contractor use this log template?

Use this log when several change orders are open, pending, approved, rejected, or invoiced on the same job.

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.