Change event vs. change order: two records, two owners, two clocks

Two words get used as if they were the same thing, by GCs, by software, and inside your own office. They are not the same thing, and the difference is not vocabulary. It is who owns the record and which clock is running.

A change event is yours. It is a dated internal record that something on the job changed. You create it, you control it, and it costs you nothing but two minutes.

A change order is theirs. It is an amendment to your contract, with a number and a dollar value, executed by the party who owes the money. You cannot create one. You can only ask for one.

Everything that goes wrong with extra work on a commercial job goes wrong in the gap between those two sentences.

Who makes each one, and when

A change event gets made by whoever was standing there. A foreman finds a wall dimension that will not work, a duct route fighting steel, a panel schedule that was redrawn, another trade sitting in his area. He logs it the same morning: what happened, where, the date, photos, who directed it if anyone did.

A change order gets made weeks later, by the GC, after your priced request has been reviewed, argued about, revised and approved. By then the wall is closed, the super who gave the direction may be on another job, and the only version of the facts that survives is the one written down at the time.

That asymmetry is the entire reason to keep two records instead of one.

Why the split exists at all

It would be simpler to have one document. Two exist for two good reasons.

The person with the facts has no time to price anything, and the person with the rates was not there. A foreman can tell you exactly what happened and will not build a priced proposal. Your office can build the proposal and was forty minutes away. Forcing one person to do both means you either get a slow document or a thin one.

A record made on the day is evidence; a record made later is reconstruction. A change event logged the morning of, with photos and a date, is contemporaneous. A change order request assembled six weeks later from memory and a text thread is an argument, and you will be having it with somebody whose own records are better than yours.

Where the confusion comes from

Three places, mostly.

The GC’s platform has a container called a change event too — upstream of their own potential change order — and it exists to track their exposure, not yours. When a project engineer says “I opened a change event,” nothing has happened to your contract and no money has moved toward you.

Then there is the superintendent’s version: “just write it up.” Write what up? If that means log it, you do it today. If it means submit a priced request, you need quantities, rates, markup and a decision about whether to proceed first.

And finally, the words in your own office drift. Half the company calls everything a change order; the other half calls everything an extra. Pick the two words above and use them consistently for a month and you will be surprised how many arguments stop happening.

Three roads out of a change event

A change event is not a change order waiting to be born. It is a fact with three possible endings.

It becomes a priced change order. The scope is definable, you can quantify it, so you price it, submit it and chase a decision. The normal path, and the one the subcontractor change order process walks end to end.

It becomes signed T&M tickets, which become one change order. The scope is not definable yet — nobody knows how much of that slab is rotten — so the work runs on time and material, each day’s tag signed on site as you go, and the signed tags roll up into one change order at the end instead of eleven small arguments. That is covered in how to price a T&M ticket.

It becomes nothing. You read the contract and it was always your scope. Or it was your own rework. Or the cost was twenty minutes and not worth the postage.

That third road matters more than it looks. A change-event log where everything converts is not a disciplined log — it is a log that is only used when somebody already smells money. The events that die are what make the ones that live credible, because they prove you record conditions rather than claims.

Many events, one change order

The most expensive habit in this area is a one-to-one reflex: eleven events on the same condition become eleven change order requests, each small enough for the GC to defer and none big enough for anyone to own.

Group them instead. One change order for “coordination rework on level three, nineteen locations, dated and photographed,” carrying all nineteen events as its support, is a conversation with the project manager. Nineteen separate requests for a few hundred dollars each is a stack nobody will process, and you will end up negotiating the total anyway — just with less evidence and more aging.

The reverse mistake also exists: bundling unrelated conditions because they happened in the same month. If the GC rejects one line they can use it to color the rest. Group by cause, not by calendar.

The vocabulary that actually costs money

COR versus CO. A change order request is yours — the priced document you submit. A change order is the GC’s instrument that comes back. Your log should show both, because the date you asked and the date they answered are the two numbers that tell you whether you are being processed or stalled.

“Approved to proceed” is not a change order. It is direction to do the work with the paperwork still to come, and it is the single most dangerous state on the board. You are now spending money against a promise. Do it when you must, but mark it as its own state, in writing, and keep the clock on it.

A no-cost change order is still worth chasing. A time extension, a sequence change, a scope swap at zero dollars — it protects you from the delay claim or the back charge arriving six months later for something you were told to do.

A change directive is not a negotiation. It is an instruction to proceed while price and time stay open. Log it as an event, reference the directive number, and start the T&M clock the day you mobilize on it.

What a change event has to contain to be worth anything

A year from now the event is only as good as what is in it.

• The date it was discovered, which is usually the date that decides the notice argument.
• Where on the job, down to the floor, room or area.
• Who directed it, by name — or a clear note that nobody did, and you found it.
• The directive reference: the ASI, RFI, field order, bulletin or sketch number that caused it. One number saves an hour of searching later.
• What it hit: the phase, activity or area of your own work, so the cost and the schedule effect can be traced.
• Rough labor and material, as days by trade and a material description — not a priced proposal, just scale.
• Photos. The only part of the record that cannot be reconstructed, and the part that ends most disputes.

How SubMark runs it

SubMark keeps the two records separate on purpose, and connects them in one direction.

• A foreman logs a change event on the job — description, photos, labor days by trade, material description and cost, a directive reference, and the phase it hit when phase tracking is on. Foremen are free seats, so the foreman who saw it can be the one who records it. See how pricing works.
• Events age visibly: amber after a week, red after two, and a banner calls out the ones that have already cost you something and still have no change order.
• Events a subcontractor you invited files on your job land in a review queue, so nothing from outside your company counts until someone in the office accepts it.
• Several events bundle into one change order. Group the events that share a cause, convert the bundle, and the change order carries all of them as support with a single number on it.
• One click converts an event, or a bundle, into a change order. The photos, labor by trade, phases and directive reference travel with it, the event stays linked to the change order, and with the AI change order assistant switched on it can draft the description and justification from the evidence already in the project — which you then edit, because it is your claim and your language.
• The change order has real stages: estimate, pending approval, revise and resubmit, approved to proceed, CO issued, rejected, and void. “Approved to proceed” is its own stage, exactly as it should be.
• Every decision is logged with who decided, the date, and whether it came back signed through the review link, plus an aging report over the stages above.
• Once a change order is approved it is added to the job’s schedule of values automatically, so it is on the next draw without anyone retyping it.

The honest limits. SubMark is not connected to your GC’s platform — there is no Procore or Textura integration, so a change event here is your own record and your own submission is still made the way your GC demands it. T&M hours are billing, not cost, so they appear on the tag and the change order and not in job-costing actuals. And the phase breakdown needs phase tracking switched on; it ships on in the drywall pack and is a settings switch for every other trade.

Change order management covers the office side, and T&M tickets cover the other road out of an event.

What to do this month

1. Say the two words correctly in your own office for one month: event for what you record, change order for what they sign.
2. Make logging an event cost two minutes, from a phone, by whoever found it — and tell your foremen explicitly that an event they log is not a claim they are making.
3. Review open events weekly, and force one of three outcomes on each: price it, run it on T&M, or close it as your scope.
4. Group before you submit. One request per cause, with every event attached as support.
5. Give “approved to proceed” its own line on your log, with the date you started spending, and review that line before anything else.

The pattern worth remembering: you control the record, they control the amendment. Every dollar of extra work you have ever lost went missing in the weeks between the two.