How to Write a Change Order (Step-by-Step Guide + Free Template)

Verbal change approvals are one of the fastest ways for a contractor to lose money and create a dispute. The owner remembers a quick hallway conversation. The client remembers a rough price. Nobody remembers the exact scope, the schedule impact, or whether the extra work was supposed to be included. That is why a written change order matters.

A proper change order protects both sides. It documents the scope change, states the revised price, shows how the schedule moves, and proves authorization. If you are serious about getting paid for added work, you need a repeatable process instead of improvising an email every time conditions change on site.

What every change order must include

A usable change order needs five core elements: a clear description of the added or revised work, the dollar amount or pricing method, any schedule impact, signatures or approval language, and a reference back to the original contract or job. If any one of those is vague, the document becomes weaker in a dispute.

It also helps to include the date, job name or address, and who requested the change. That sounds basic, but it prevents a lot of confusion months later when the paperwork pile gets thick.

Step 1: Identify scope change

Start by describing exactly what changed from the original agreement. Be specific. Instead of writing "add electrical work," write "add two GFCI receptacles on the east patio wall and reroute existing conduit around new window opening." Precision is what turns a change order into a defensible record.

If the change comes from hidden conditions, owner requests, plan revisions, or inspector corrections, say that too. The source of the change often matters when you explain pricing and time impact.

Step 2: Price the change

Break the price into something understandable: labor, materials, equipment, subcontractor cost, markup, and tax where appropriate. You do not always need to show every internal cost detail, but you do need a price you can justify if the client pushes back.

Use real production assumptions. If the added work will trigger another site visit, permit revision, or material order, include it. Small misses on change-order pricing can quietly kill margin.

Step 3: Document in writing

Put the scope, price, and timing in a formal document before the extra work starts whenever possible. Text messages and email threads are not a reliable replacement for a standardized form.

If you use accounting software like FreshBooks, attach the approved change to the job record so the billing side stays clean. The document should be easy to find when it is time to invoice.

Step 4: Get client signature

Do not treat approval as implied. You want a signature, formal digital acceptance, or at minimum a written approval process defined in the contract. The best time to get approval is before extra labor or materials are committed.

This is the point where many contractors cave because they want to keep the project moving. That shortcut often turns into a collections argument later.

Step 5: Update project schedule

Every meaningful change order affects the schedule, even if the impact is small. Note whether the completion date changes, whether another trade is affected, or whether material lead times now control the next milestone.

If you do not document time effects, the client may expect the original completion date to hold even after adding work.

Step 6: File it

Once approved, save the change order with the contract, estimate, invoices, and project communication. The goal is not paperwork for its own sake. The goal is a complete record you can reference when questions arise.

This is also why packs like the GC Starter Kit help. They create a standard paper trail across the entire job, not just the change event.

Why change orders matter legally

In a dispute, the contractor with a signed, dated, job-specific change order is in a much stronger position than the contractor relying on memory and text screenshots. Courts, arbitrators, and owners want documentation. Even when a claim does not become formal litigation, written change orders make collections conversations shorter because the paper trail is obvious.

They also help internally. A written change order tells the field what was actually approved, tells the office what to bill, and tells the client what to expect. That alignment is often more valuable than the legal protection alone.

Real-world example of clean wording

A strong description sounds like this: "Add 120 square feet of base cabinet installation on north wall per owner request, including labor, trim adjustments, and one return trip for final fit. Add $1,250. Project completion extended by two calendar days." That language is better than "extra cabinets - $1,250" because it explains what the money and time are buying.

The exact format matters less than completeness. If you consistently include scope, price, time, and authorization, your change orders will hold up much better.

Frequently asked questions

Can a contractor enforce a verbal change order?

Sometimes a contractor can still argue for payment, especially if the client clearly accepted and benefited from the work, but it is a much weaker position. Written approval is the standard you want every time.

What if the client refuses to sign but wants the work done?

Explain that extra work changes cost and schedule and needs written approval before you proceed. If you move forward anyway, you are accepting more collections risk than you should.

Should change orders be separate from invoices?

Yes. A change order is the approval document. The invoice is the billing document. They can be tied together, but they serve different legal and operational purposes.

Documentation habits that protect your margin

The strongest document in the world fails if your team cannot find it, sends it late, or uses the wrong version. Build one folder structure, one naming convention, and one approval process so the office and field know exactly where signed paperwork lives. That alone prevents a surprising number of payment and closeout disputes.

It is also smart to connect documents to workflow milestones. For example, change orders should be approved before extra work starts, waivers should match payment stage, and closeout forms should be tied to substantial completion instead of remembered at the end. Good timing makes ordinary documents much more powerful.

Paperwork control checklist

Keep the process simple enough that the whole team can follow it:

• Use one current template version and archive old ones instead of editing random copies.
• Require signatures or written approvals before money-sensitive work proceeds.
• Store signed documents with invoices, photos, and key correspondence for the same job.
• Review closeout paperwork before final billing so nothing important is missing.

Final takeaway

Use the advice in this article on a live job or active workflow instead of treating it as theory. The contractors who improve fastest are the ones who test, measure, and standardize what works after the first real-world use. Pick one estimate, one active customer, or one crew week and run the process exactly as written. Then review what improved, what still felt clumsy, and what needs to become part of your permanent standard operating procedure. That short feedback loop is where practical improvement happens.

In other words, do not just bookmark the article. Turn it into a repeatable habit, assign an owner, and review the results after the next real job closes. Even a small improvement in estimating speed, paperwork quality, labor tracking, or customer communication compounds across dozens of jobs over a season.

Next-action checklist

Use this short action plan immediately:

• Pick one live job or workflow to test first.
• Write down the exact metric you want to improve.
• Train the person responsible for using the process.
• Review the result after the job closes and keep what worked.

* This post contains affiliate links. Wingman Protocol may earn a commission from qualifying purchases at no extra cost to you. We only recommend tools and software we'd use on a real job.