The Stamp Said Clarification
ASI 14 lands on a Thursday. Architect’s Supplemental Instruction, one page, a marked-up plan, and a stamp in the corner: Clarification — No Change in Contract Sum or Contract Time. The instruction relocates the fire riser room partition two feet east to clear a duct conflict the coordination drawings missed. The superintendent reads it, sees the stamp, forwards it to the framer and the plumber, and files it. The wall moves. The rough-in moves with it. Nobody writes anything down, because a clarification is not a change, and the architect said so in ink.
Forty days later the project manager is closing the month and the drywall and plumbing costs are running over. He traces the overrun to a partition that is not where the drawings had it and finds ASI 14 in the folder. He writes the change order — extra framing, rerouted rough-in, two days of schedule — and sends it to the owner.
The owner’s response is two sentences. The first says the ASI was a clarification, the contractor performed it without objection, and the work was reasonably inferable from the contract. The second cites the notice provision: claims must be initiated within twenty-one days of the event, and the event was forty days ago. The merits of the change order are never discussed. They do not have to be.
Why it happens
A stamp is a characterization, not a fact. Clarification describes what the architect believes the document does. Whether it is a change is a different question with a different test — did the instruction require work beyond what the contract documents already obligated the contractor to perform, and who required it — and an ASI that moves a wall two feet answers that test the same way regardless of what the stamp says. The keyword tells you before the test does: relocate is a verb that generates labor, and a document containing it is a document that costs money.
But an ASI arrives looking like the harmless paperwork it usually is, and the stamp is designed to be accepted. The superintendent reads the stamp, not the verb. The field performs the instruction, and performance without objection becomes the owner’s best evidence — the contractor’s own conduct says the contractor agreed this was no-cost work. The notice clause converts that silence into a permanent condition. Under the contract, notice within the window is not a courtesy; it is a condition precedent to the right to claim. Miss the window and the claim is not weakened. It never came into existence. The clock started the day the ASI landed, and nothing in the document said so.
Every contract family runs the same trap on a different timer — twenty-one days under AIA, fourteen under ConsensusDocs, thirty under EJCDC, twenty under the FAR — and every one of them extinguishes the claim on the calendar, not on the merits.
What it costs
On the Thursday it lands, ASI 14 is a proposed change order. The verb fires the scan, the four-part test calls it a change, and a notice goes out inside the window with the five things a notice has to contain: the event, the contract provision it triggers, the causal link, a preliminary statement of impact, and a reservation of rights. The wall still moves — the notice does not stop the work — but it moves as a documented change, and the argument that follows is about the price of two feet of relocated partition. The owner can dispute the number. The owner cannot dispute the right.
On day forty, the same two feet of partition is the contractor’s cost. The extra framing, the rerouted rough-in, the two days — absorbed, and absorbed without a change order the contractor can point to, because the change order is procedurally dead. And the next ASI arrives with the same stamp, because the stamp worked.
The specification did not decide who paid for the wall. The calendar did.
Catching it early
Read every incoming document for what it does, not what it is called. An ASI, an RFI response, a field order, meeting minutes, a verbal directive on the walk — each one gets scanned for the verbs that generate work: install, relocate, modify, add, provide, revise. Any document carrying one of them is a candidate change, whatever its stamp says. Then weigh the source: an ASI is design intent, and design intent cannot alter the contract sum or time by itself — only a change order or a construction change directive can do that. A clarification that changes the work is a constructive change wearing a clarification’s stamp.
Run the four-part test on the candidate. If it passes, fire the countdown the same day — exclude the day of the event, include the last day, apply the window the contract family sets — and get the notice out before the crew touches the wall. Every notice with all five elements; every acknowledgment of a no-cost characterization signed with a reservation of rights or not signed at all, because the owner’s documents carry language built to extinguish claims and a signature on them is the waiver.
Then price it and write it. Classify the change so the calculation method is right, build the cost with every dollar traced to a source, and wrap it in the narrative that proves entitlement instead of requesting approval — the trigger located outside the contractor’s control, the contract provision cited, the original scope and the revised scope side by side, the cost per the attached breakdown, and the notice on record.
That is what Delta does. It reads every project document for the change it actually contains, classifies it before anyone prices it, fires the notice clock the day it lands, and builds the change order as an argument the owner has to dispute on the evidence. They called it a clarification. The four-part test called it a change. Delta makes sure the calendar never gets a vote.