An architect's supplemental instruction is not an FYI. It is a change to the work, issued after the drawings, and it is supposed to reach the people who will close up the area it affects. When an ASI sits in an inbox until the ceiling is closed or the wall is finished, that is not a paperwork inconvenience. It is a rip-out, or work that no longer matches what the owner thinks they bought.
This is a typical case, not a specific job, and the dollar figures are only examples.
How it usually goes
A light-commercial interior is heading into ceiling close-up. Mid-stream, the architect issues an ASI: relocate two ceiling devices, add an access panel, and change a soffit dimension. It is a short document, but it actually changes the work.
The ASI lands in email. It may even get acknowledged in the office. But it never gets posted to the current set, never goes out to the mechanical or electrical sub, and never gets a line in a log anyone in the field will see. The ceiling crew has been looking at the issued drawings all week. The grid goes in. The devices go in the original locations. The area is closed up.
A week later, someone forwards the ASI, or the architect walks the space and asks why the instruction was ignored. Now you are opening a finished ceiling and moving devices. The crew built the set they had. The ASI just never left the inbox, so it never became part of the current work.
Free: the Built On Record Job File Kit — logs, checklists, and a folder tree
Unsubscribe any time. Privacy
What that costs (example figures)
The direct work is opening a finished area, moving devices or reframing a soffit, patching, and maybe a second inspection. That direct rework might land somewhere in the range of $4,000 to $18,000 on a miss like this, depending on how much of the ceiling or wall has to come down and whether you are doing it after hours. That is a ballpark, not a quote.
The rest of the cost stacks up fast. Close-up was supposed to release the next trade. The sub will say they never saw the ASI. The office will say it was emailed. The design team will say they issued it on time. Without a distribution record and a current-set posting, that argument has no clean ending. If the ASI also affected cost or time, you now have a change conversation on top of a rework conversation.
The basic controls that would have caught it
Treat an ASI the way you treat a revised drawing, because that is what it is.
Log it when it arrives. A simple change log, or a line in the same spreadsheet you use for RFIs, should show the ASI number, the date received, whether it changes the work, and who in the field has received it.
Post it where the current set lives. A "binding ASIs" packet next to the current drawings, or a clouded mark on the current sheet, is the difference between an instruction and a surprise.
Distribute on purpose, and keep proof. A short note to the superintendent and the affected subs: ASI number, what changed, and where the file is.
Review before close-up. No ceiling close-up and no wall cover until someone has looked at the ASIs issued for that area. Do it the day before, not after the grid is locked in.
You can run these controls with a shared folder and a spreadsheet. I talk about the trail that makes "I never got that" a short conversation in "The Audit Trail: How a Clean File Ends Arguments Before They Start."
If changes are landing faster than the inbox can handle
Your superintendent should not discover an ASI after the ceiling is closed. If instructions are coming in through email, a portal, and verbal direction all at once, that is a reason to get help.
I can set up the job file, run the logs and distribution on a retainer, or prepare closeout. An ASI that sits in an inbox is not an instruction yet. It is a future opening in a finished ceiling.
If you want help, not just a checklist
Some jobs run fine on a clean file and a superintendent who gives the log fifteen minutes twice a week. Others do not: revisions are moving fast, closeout is already behind, or the field simply has no hours left for paperwork.
That is where I come in. I set up the job file, run the logs on a retainer, or prepare closeout before the scramble starts. Your files stay yours, and there is no software contract to sign.
A job-file kit you can use this week
Free logs and checklists for RFIs, submittals, dailies, changes, transmittals, pay apps, warranties, and closeout, plus a folder tree to keep them in. Sent by email, with an occasional practical note after that.
Free. Unsubscribe any time. Privacy