BuildProofFree tool

Change Order Generator

Who it is between

Project

This change order

What changed

DescriptionAmount

Credits and deleted scope go in as negatives. A change order that removes work is still a change order.

Contract to date

Leave prior changes at zero if this is the first one.

Time

Days are calendar days. Enter a negative number to pull the date in.

Your work

Saved on this device only. Save a file to keep it or move it to another computer.

Change Order

Change order no.
Date
Project
Owner
Contractor
Reason for the change
No.DescriptionAmount
Total this change order
Contract sum
Original contract sum
Net change by previous change orders
Contract sum before this change order
This change order
New contract sum
Current completion date
Time extension
Revised completion date
Accepted for the owner. The contract sum and contract time are changed only as stated above.
Owner
Date ______________________
Accepted for the contractor. This change order includes all costs and time associated with the change.
Contractor
Date ______________________

A free change order template that does the arithmetic

Itemise what changed, and this produces the change order with the new contract sum and the revised completion date worked out. It runs in your browser — no signup, no email.

The two things a change order has to settle

Every change order answers exactly two questions, and a change order that answers only the first is the reason schedule disputes happen months later.

What does it do to the money?
Original contract sum, plus every previously approved change, plus this one. Stating all three is what lets the other side reconcile it against their own records in a few seconds rather than an afternoon.
What does it do to the time?
If the change adds days, they belong here. Time not claimed in the change order is time you have given away — signing a change order that is silent on schedule is generally taken as agreeing the change had no schedule impact.

Why deductive change orders are entered as negatives

A change order that removes scope is still a change order and still needs signing. Entering the credit as a negative keeps the arithmetic honest: the new contract sum falls, and the document shows exactly why. Splitting a change into separate "add" and "deduct" documents is how a contract sum stops matching anyone's records.

Approved, and the word that matters

A priced change order is not an approved change order. Until it is signed by both parties it is not part of the contract sum, cannot be billed on an application for payment, and will be removed from one if it appears there. If you are proceeding on a verbal instruction because the work cannot wait, get it in writing as soon as you can and keep your own record of when the instruction was given and by whom.

What it does not do

This produces one change order at a time. It does not track a change order log across a project, tie a change to the requisition that bills it, or tell you when the cumulative change on a contract has crossed a threshold that needs someone else's approval. That is the paid product.

More free tools