RFI-to-change-order exception example: a late-notice hard case, decision by decision

Short answer

The records that explain how an exception was handled are the ones that capture each decision with its date: the RFI answer, the revised drawing, the daily report recording the choice to proceed, the cost code opened for the extra work, the written notice, the priced proposal and the signed modification. In the Illustrative case below, notice went out late, so part of the cost fell outside the federal 20-day lookback. Each step left a record, and lined up in order they let a reviewer check every judgment the contractor made.

Visual briefFull-size diagram
A case timeline that branches at day 2: the path not taken sends notice at once, while the actual path proceeds without notice, sends notice on day 31, prices $63,500 on day 45 and closes with a $52,700 modification on day 90, each step showing the record it left.
Illustrative federal-project case, invented for this page. Amounts and dates are fictional.

This case belongs with change order data in construction, which explains what a notice is and why it matters. Here the job is one hard case, walked through step by step, ending with how to spot the same pattern at a client.

Step 1: the answer that moved the work

Illustrative and invented for this page. A fictional 280-person mechanical contractor is renovating a federal medical office building under a fixed-price contract.

On day 0, RFI 214 reports that a supply duct main on level 2 clashes with a new steel beam shown on the structural drawings. The official response, prepared by the design team, issued under the Contracting Officer's authority and logged in Autodesk Build, reroutes the duct below the beam, which adds four fittings, lowers part of the ceiling and moves 14 diffusers. On day 1, mechanical sheet M-202 is reissued in Aconex as a new version with a transmittal.

RecordSystemHolderWhat it proves
RFI 214 with the official response and activity logAutodesk BuildProject engineerThe question, the answer and when each was given
M-202, new system version and transmittalAconexDocument controllerThe drawing changed the day after the answer

Nothing here yet says "change". An answer to a question has expanded the work, but no one has called it a change order. That is the exception.

Step 2: proceeding without notice

On day 2 the superintendent decides to proceed with the reroute to keep the ceiling close-in on schedule. The decision is sensible for the schedule and costly for the record: no written notice goes to the Contracting Officer.

DayDecisionWho decidedRecord it left
2Proceed with the reroute nowSuperintendentDaily report: "Proceed per RFI 214"
3 to 28Crew performs the extra workForemanTimecards, at first coded to the base scope
15Split the extra work onto its own cost codeProject controls managerNew cost code with an opening note citing RFI 214

Two decisions are visible here: the superintendent's choice to proceed and the project controls manager's choice to separate the cost. The second only happened because someone spotted an overrun on day 15. Without the daily report and the cost code note, nobody could later show when the extra work began.

Step 3: the late notice and what the lookback cut off

On day 31 the project manager sends written notice, citing RFI 214 and the reissued M-202, stating the date, circumstances and source of the instruction, and stating that the contractor regards it as a change. Under FAR 52.243-4(b), an interpretation from the Contracting Officer that causes a change is treated as a change order only with written notice of this kind, and under paragraph (d), except for defective specifications, costs incurred more than 20 days before the notice are not adjusted.

Twenty days before day 31 is day 11. The work from day 3 to day 10 therefore fell outside the lookback unless the contractor could show the drawings themselves were defective. Had notice gone out on day 2, the whole period would have been inside it. That is the branch point the case turns on, and it can only be checked because both the notice date and the cost dates are on record.

Step 4: pricing, the defective-drawing argument and the final decision

On day 45 the estimator submits a priced proposal of $63,500 in two parts: $48,200 for the work from day 11 to day 28, inside the lookback, and $15,300 for day 3 to day 10, claimed on the ground that the structural and mechanical sheets conflicted, a defective-specification argument. On day 90, after negotiation, both parts are resolved in a bilateral modification of $52,700.

StepDecisionDecided byRecord
NoticeTreat the answer as a changeProject managerNotice letter in Aconex mail, day 31
PricingSplit the claim at day 11Estimator with the project managerCost build-up and proposal letter, day 45
ArgumentClaim the early days as a defective drawingContracts managerProposal narrative citing the clashing sheets
OutcomeAccept $52,700Contracts manager and the Contracting OfficerSigned modification, day 90

Why is this sequence useful evidence? Because every judgment can be tested against a dated record: when the clash was known, when work started, when notice went out, how the claim was split and what was finally agreed. A reviewer can see the cost of the late notice, the argument used to recover part of it and the negotiated result. Clean cases teach one rule; this one shows how people actually handled a rule they had partly missed.

Spotting the same pattern at a client

Construction technology advisors can recognize companies with cases like this without seeing a single document. Ask the project controls director, at metadata level:

  • Do RFI answers often come with reissued drawings? That is where scope moves without a change request.
  • Are cost codes opened partway through work, with a note naming the RFI? It shows someone separated extra work after the fact.
  • Are notice letters filed where they can be matched to the RFI and the cost code? The notice is the record most often missing.
  • Do modifications often settle below the proposal? The gap reflects decisions worth explaining.
  • Which systems and years hold all this? Project platform, document control and job cost, and the date any access ends; see Procore project data exports and the BIM 360 to Autodesk Construction Cloud migration.

Then introduce the person who can authorize a licensing discussion, the CEO, with the project controls director as working contact. Introduced companies need 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Owner confidentiality terms, design copyright and federal handling restrictions are for SourceX's rights review, not the partner. The RFI log page and RFI-to-paid-change records cover the surrounding records, and the construction technology consultant page covers the advisor's role. This page is general information, not legal advice.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a contractor you advise keeps notices, cost codes and modifications that tell stories like this one, register as a partner, check the company against who qualifies, and read the program terms before introducing its decision-maker.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Why use a case where the contractor got something wrong?

Because exceptions are where judgment shows. A clean case has one decision; a late-notice case has several, each with its own record, and that sequence is what makes the history useful evidence.

Does the 20-day rule apply to private projects?

Not as such. It comes from the federal FAR Changes clause. Private contracts set their own notice rules, and the contractor's counsel reads the actual contract; the pattern of answer, decision, notice, pricing and outcome is the same.

Should a partner judge whether the contractor's claim was right?

No. Entitlement is for the company and its counsel. A partner notes which records exist, which years they cover and who owns them.

Sources

  1. acquisition.gov/far/52.243-4
  2. help.autodesk.com/cloudhelp/ENU/Build-Rfis/files/work-rfis/Exp…
  3. help.aconex.com/documents/how-do-version-control-and-the-aco…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment