A superintendent tells a sub to run an extra conduit run because the field condition doesn't match the drawing. Three months later, that conversation is a line on an invoice the owner doesn't remember agreeing to. Extra work dies as a billable item at the moment it's only spoken, not written — and the fix has to happen the same day, not at invoicing.
Key takeaways
The problem isn't that extra work goes unnoticed — it's that the record of it lives only in the memory of the person who gave the instruction. By the time an invoice is prepared weeks or months later, the specifics have blurred: the exact date, the exact reason, who authorized it and on what basis, are all being reconstructed rather than recalled.
An owner or consultant reviewing that invoice has no independent way to verify any of it, which is exactly the position that produces a disputed change order. treadstonelaw's own explainer covers what that dispute looks like from the owner's side — unauthorized extra charges, disagreement about what the original scope already covered, and conditions discovered mid-project — and in each case, the contractor's position is only as strong as the contemporaneous record behind it.
A firm doesn't need to invent a change-management process from scratch. CCDC's own description confirms CCDC 2 addresses “procedures for changes in the work” as a defined part of the contract, and CCDC 16 exists specifically to explain the philosophy behind that process — key terms, how the price gets adjusted, and how a claim is distinguished from an ordinary change.
What CCDC doesn't publish is the specific clause language and procedural detail — that text sits behind the paywall with the rest of the General Conditions, and no clause number should be quoted from memory. The operational point stands regardless: a field note that follows the contract's own change process, whatever it specifically requires on a given form of contract, survives scrutiny in a way an informal verbal instruction never does.
An RFI is often the first written trace of a condition that becomes an extra. One field platform describes “Ball In Court” as a tracked responsibility that starts with the assignee and shifts to the RFI manager once required responses are complete — which means the RFI itself, properly logged, is already a dated record of who identified the condition and when, before a single dollar is discussed.
That RFI record is the natural anchor for the field note that follows: the same date, the same condition, tied together rather than treated as two unrelated pieces of paper. A field note that references its originating RFI number is harder to dispute than one that stands alone.
Once a condition is documented in the field, it still has to become a priced, tracked change order rather than sit as an unresolved note. A dedicated change-orders view helps here: the Commitments tool one field platform ships gives “an overview of any change orders that have been created for that particular subcontract,” including status, amount and due date, which is the office-side tracking layer a field note eventually has to reach.
The gap most firms lose money in isn't the field note itself — it's the handoff between the field note and that tracked office record. A note that sits in a superintendent's daily log for three weeks before anyone enters it into the change-order tracker is a note that's easy to forget, easy to under-price from memory, and easy for an owner to push back on for being late. See our companion piece for how the pricing side of that handoff gets built to survive a later audit.
Extra work and schedule delay often originate from the same field condition, but they need separate documentation because they get argued differently. An extra is priced against the scope that changed; a delay claim is argued against the critical path and the days actually lost. Our companion piece covers building that delay-specific record; conflating the two into one field note usually weakens both arguments rather than strengthening either.
The drawing that prompted the field condition in the first place is worth tracking too — our companion piece covers making sure the revision that resolves the condition actually reaches the crew, which closes the loop the extra started from.
A worked example
A site supervisor verbally directs a sub to add reinforcement around an unforeseen utility conflict on a Tuesday. No RFI is filed and no written note is made that day; the extra surfaces on an invoice six weeks later at $8,400, and the owner's consultant rejects it outright for lack of a contemporaneous record — there is no RFI, no dated field note, and no reference to the change procedure the contract defines.
Run the same conflict with the process used: an RFI is logged the day the condition is found, Ball In Court assigned to the site engineer for a same-day response; a field note references the RFI number, the condition, and the verbal direction given, dated and photographed; the item is entered into the change-order tracker within 48 hours at an estimated $8,400, pending final pricing. The consultant's review has a dated trail to check against — RFI, field note, tracked change order — and the $8,400 is approved on the first submission rather than disputed on the last.
It can, but it's the weakest possible record of one. treadstonelaw's own guidance covers how disputes over unauthorized extras actually get argued — the contractor's position depends heavily on whether there's a contemporaneous written record, not just on whether the instruction was in fact given.
An RFI documents a question or a field condition that needs an answer; a change order is the priced, authorized modification to the contract that may follow from it. One field platform shows RFI responsibility tracked as its own workflow, separate from the change-order tracking that comes after a condition is confirmed and priced.
From the signed contract itself, read carefully — not from memory or a generic template. CCDC's own General Conditions text is sold rather than published, so a firm should confirm the actual procedural requirements on its own copy of the contract rather than assuming a clause number from a different project or edition.
A 30-minute call is enough to tell you whether AI pays for itself here.
