Subcontractor business

How subcontractors should track change orders

Log every change the moment it is directed, give it a number and status, price it inside the notice window, track cost on its own code, and do not let approved or pending changes fall off the pay app.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

Subcontractors should track change orders in one log per job that captures every change from the moment someone directs it, not from the moment it is approved. Each entry gets a number, the date and person who directed it, a status (directed, priced, submitted, approved, rejected, billed), the amount requested and approved, and its own cost code. Review the log weekly with the PM and foreman, and reconcile it to every pay app. The changes subs lose money on are rarely the big ones. They are the dozen small verbal requests that never made it onto paper.

Subs face two problems GCs do not. You often learn about a change from a superintendent in the field, with no paperwork at all. And your approval depends on the GC getting its own approval from the owner, which can take months. A good log handles both.

What a subcontractor change order log should track

Fields for a subcontractor change order log
FieldWhy it matters
Sub CO number and GC referenceLets you match your log to the GC's numbering on every pay app.
Date directed and by whomProves when notice clocks started and who authorized the work.
Type of directionWritten change order, change directive, RFI response, field direction, or drawing revision.
Description and locationShort and specific: 'Add 4 floor boxes, rooms 210 to 214, per ASI 7.'
StatusDirected, priced, submitted, approved, rejected, billed.
Amount requested and approvedShows the gap between what you asked and what you got.
Time requestedDays added, if any. Leave it blank only on purpose.
Cost code and actual costProves the cost and shows whether your pricing holds up.

Step by step: a change order system for subs

1. Capture every change at the source

Your foreman is usually first to hear about a change. Give them one fast way to report it: a form on the phone, a text to the office, a line in the daily log. The office opens a log entry the same day, even if the price comes later. The guide on verbal change requests covers how to confirm direction in writing.

2. Confirm in writing and know your notice deadline

Send the GC a short confirmation: what you were asked to do, by whom, and that you will submit a price. Then find the notice period in your subcontract. On federal jobs, the prime's Changes clause, FAR 52.243-4, says an adjustment for a change not ordered in writing cannot include costs incurred more than 20 days before the contractor gives written notice, and the contractor must assert its right to an adjustment within 30 days after receiving a written change order or giving that notice, unless the government extends it. A subcontract usually gives you less time so the GC can meet those dates.

3. Price it while it is fresh

Submit a change order request with labor, material, equipment, lower-tier sub costs, and markup as the subcontract allows. Include time if the change affects your schedule. Break it down so the GC can forward it upstream without rework. See how to price a change order.

4. Code the cost separately

Open a cost code for each change or group of related changes. Have the foreman code hours to it. If the work is time and materials or the price is still open, this is your proof. It also tells you after the job whether your change pricing was profitable.

5. Chase approval on a schedule

Review open items with the GC's PM every week or at each job meeting. Ask for a status on each one by number. If a change sits pending for more than a pay cycle, ask in writing whether it is with the owner and when a decision is expected. Pending changes have a habit of becoming disputes at closeout. The change order disputes guide explains why.

6. Bill approved changes on the next pay app

Add each approved change as its own line on the schedule of values and bill progress on it like base scope. Reconcile your log to the pay app every month: approved, billed to date, retainage, and balance. See how to invoice change orders without delays.

7. Watch your waivers and closeout

When you sign a lien waiver, change order, or final release, list any pending change orders as exceptions. Before closeout, send the GC a final change order summary so nothing is left unresolved.

Worked example: an HVAC sub on a $1.1 million office fit-out

Here is an illustration. An HVAC sub has a $1,100,000 subcontract. By month five its log shows these changes.

Example: change order log, month five (illustrative)
CODescriptionRequestedStatus
01Relocate 6 diffusers per RFI 14$3,900Approved $3,600, billed 100%
02Add supplemental unit, server room, ASI 3$28,400Approved, billed 40%
03Reroute duct around new beam, field direction$7,250Submitted, pending owner
04Overtime to meet accelerated turnover$11,800Directed, pricing in progress

Approved changes total $32,000. Pending and unpriced items total $19,050, about 1.7 percent of the contract. On a subcontract with thin margins, that can be a large share of the profit left on the job. Without the log, CO 03 and CO 04 would live in the foreman's memory. With it, they appear on every weekly agenda and on the pay app as exceptions until settled.

Who should own the change order log

One person owns the log on each job, usually the project manager or, in a smaller shop, the office manager. The foreman feeds it from the field, the estimator or PM prices entries, and the bookkeeper uses it to build the pay app. When everyone can add to it but nobody owns it, entries stall at "directed" and nobody notices until closeout.

Set a short weekly routine. The owner of the log checks each open entry, updates its status, sends one follow-up email covering every pending item, and flags any entry close to a notice deadline. On a busy job that takes 20 minutes. Across several jobs, a combined view of all open changes shows the owner how much unbilled work the company is carrying.

Mistakes to avoid

  • Doing the work first and asking for paper later, especially on small items.
  • Tracking only approved changes, so pending work disappears.
  • Using the GC's log as your only record.
  • Coding change work to base scope, so the cost cannot be proven.
  • Signing waivers that release pending changes.
  • Forgetting to request time with the money.

Templates, terms, and tools

Start with the change order log template and the construction change order template. Related terms: change order, field order, and deductive change order. Smart Business Automator logs changes from the field, tracks status through approval, and carries approved changes onto the next pay app, through change order approval automation.

Frequently asked questions

Should a subcontractor do extra work without a signed change order?

Avoid it when you can. If you must proceed, get the direction in writing, even by email, send notice inside your subcontract's deadline, and track the cost on its own code.

How long does a sub have to give notice of a change?

Whatever the subcontract says, which is often shorter than the GC's deadline with the owner. On federal jobs, the prime's Changes clause FAR 52.243-4 uses a 20-day cost limit and a 30-day assertion period, so subcontracts are often tighter.

Can I bill a change order before it is approved?

Usually not on the pay app itself. Most GCs only accept approved changes as SOV lines. Track pending work separately and list it as an exception on waivers.

What should I do when a change order is rejected?

Ask for the reason in writing, check the subcontract and documents, and decide whether to resubmit, negotiate, or preserve it as a claim. Keep tracking the cost either way.

Sources

  1. Acquisition.gov: FAR 52.243-4, Changes
Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment