FIELD NOTE · CHANGE ORDER

The disputed change order nobody closed

A change order flipped to disputed and never closed — the product does not take a side, it just keeps looking at the row.

What it reads: Procore's own status field on the change-order record.
What triggers it: Somebody sets the change order to disputed.
What it needs from you: Nothing to raise it — it reads a field you already have. Closing it needs someone to change the record.

Every figure, date, and party in this article is illustrative — drawn from a fictional "Project A" case built to be realistic, not a real client, GC, or project.

Nothing on the log changes. One layer gets added.

This is Project A's real change-order log. Flip the layer on — the rows do not move.

What you already see

Project A change-order log — without the cross-reference layer
CO	Title	Amount	Status
CO #044	Level 1 wayfinding, added directory and code signage	$71,250Illustrative figure	approved
CO #041	Acceleration and premium time to recover elevator equipment release	$208,750Illustrative figure	disputed
CO #046	Additional hoistway entrance door protection and sill infill at levels 2–4 during construction phasing	$38,900Illustrative figure	pending

With the cross-reference on

Project A change-order log — with the cross-reference layer
CO	Title	Amount	Status
CO #044	Level 1 wayfinding, added directory and code signage	$71,250Illustrative figure	approved
CO #041	Acceleration and premium time to recover elevator equipment release ↳ RFI #0147 (31 days open) and submittal #E-14-002 (23 days in review) already sit behind this row. Nothing here is new — it was just never assembled.	$208,750Illustrative figure	disputed
CO #046	Additional hoistway entrance door protection and sill infill at levels 2–4 during construction phasing	$38,900Illustrative figure	pending

The exhibits

Four exhibits, in the order they would have to be pulled by hand. The last one does not resolve anything — that is the point.

The record

CO #041 — $208,750 — set to disputed, and it has not moved since.

Procore · Change Orders

CO #041, issued against Project A: "Acceleration and premium time to recover elevator equipment release." Somebody set its status to disputed. That status field is the entire trigger — nothing else about the row has to change.

The RFI it rests on

RFI #0147 has been open well past the default threshold, with a known schedule impact already on file.

Procore · RFIs · RFI #0147

RFI #0147, "Machine room ventilation: confirm louver location and code path," has been open 31 days — well past the 14-day default threshold on this project. Ball in court: the design team. A known schedule impact is already on file, which is why this one reads as more than paperwork.

The submittal it's blocking

Submittal #E-14-002 has sat in review more than twice its SLA, holding a long-lead clock at zero.

Procore · Submittals · #E-14-002

Submittal #E-14-002, "Elevator shop drawings and cab finishes," has been in review 23 days against a 10-day SLA on this project. The procurement clock for the elevator equipment does not start until this submittal is approved — so right now it is still at zero.

The exposure while it runs

The executed subcontract's own payment term decides who is carrying the exposure while the dispute runs.

DOC-1 — page 14 · §11.4

DOC-1, the executed subcontract, sets a pay-if-paid term at §11.4: the GC pays the elevator sub only after the GC itself has been paid by the owner. While CO #041 sits disputed, that clause is what decides who is carrying the exposure in the meantime.

The ladder stops here. Nothing above it decided the dispute.

The check, in full

One status field, and everything that was already sitting around it before anyone looked.

Procore's change-order record carries a status. Somebody set one of them to disputed.
The product did not decide that. It does not weigh the merits and it does not take a side.
What it adds is that it does not stop looking at that row after everyone else has scrolled past it.
It stays raised until the record itself changes.

What does NOT trigger it

A change order in any other status.
The merits of the dispute — never assessed.
Anything about who is right.

This is a deterministic check — the same inputs produce the same result every time. No model decides it.

See how every change order is cross-checked

What this does not do

It does not decide: It puts the status in front of you. It does not tell you who is right, and it will not.
The blind spot: A disputed change order is not a wrong one. This does not adjudicate the dispute, does not estimate who owes what, and does not put a dollar impact on it. It tells you a record stopped moving.
The precondition: It only ever reads Procore's own status field. A dispute that happened on a phone call and never got logged does not exist here.
No score: There is no confidence percentage anywhere in this, because a number shaped like evidence is not evidence.

Your call

Nobody has to be at fault for a stalled record to be worth a phone call.

What the rep does next

The owner's rep calls — not to argue the dispute, but to ask why CO #041 still reads disputed, and whether anyone is actually working it.

Read what this means if you're the owner