The drawing goes out Issued for Construction at Rev 4. The field prints it, pins it to the trailer wall, and starts building. Back in the office the design keeps moving: an RFI comes back, a tie-in shifts, a support gets added, and the drawing quietly rolls to Rev 5, then Rev 6. Those get issued too. They land in the project's document system, in an email, in a transmittal the superintendent skims on a phone between two other fires.

Three weeks later the pipe's in and it doesn't line up with the new tie-in, because the crew built exactly what Rev 4 told them to. Rev 4 was a real, approved, Issued-for-Construction drawing. It just wasn't the current one. Nobody handed the trailer the wrong drawing on purpose. The current revision simply didn't make it the last twenty feet to the wall.

How the field falls behind the office

IFC is a status, not a promise that everyone's holding the same sheet. The office issues on the office's cadence. The field builds on the field's. In between sits a document system that will tell you Rev 6 is current if you go log in and look, and a wall of printed Rev 4s that nobody reprints unless someone flags it. This isn't malice or sloppiness. 'We issued Rev 6' and 'the crew is building Rev 6' are two different events, and only the first one has a workflow behind it.

• The revision is current in the EDMS; the paper on the wall is two revs old and nobody reprinted it.
• The superseded drawing was a legitimate IFC issue, so it doesn't look wrong. It looks approved.
• What changed between Rev 4 and Rev 6 is buried in a transmittal cover sheet, not shown as a marked-up delta a foreman can read in ten seconds.
• Multiple crews, multiple trailers, multiple print dates, and nobody's sure which wall has which rev.

What the field actually needs to see

A foreman doesn't need the whole revision history. They need one thing: what changed between the sheet on the wall and the current issue, marked up so it's obvious in the time they've got. 'Rev 6, see transmittal 041' isn't that. A clouded delta showing the tie-in moved and a support got added is. Rework on a wrong-revision build isn't a drafting problem. It's a drawing that was current in a system nobody had open.

A superseded IFC drawing looks exactly like a current one: same stamp, same title block, same approval, right up until the pipe doesn't fit.

How Kord keeps everyone on the same revision

• Every issue is a versioned snapshot, so 'current' is unambiguous: one latest approved revision, not a folder where Rev 4 and Rev 6 look equally official.
• The visual diff shows what changed between the revision in the field's hands and the current one, marked up per format, so the delta is something a foreman can actually read.
• A release ties the transmittal to the exact revisions issued, so 'what did we send the field on the 12th' is a lookup, not a reconstruction from email.
• The consistency check catches the RFI change that made it into the model but not the drawing, before Rev 6 goes out carrying a contradiction.
• Because the set is versioned together, a support added to the model shows up against the drawing that should have moved with it, instead of drifting until the field finds the mismatch.

On a fast project the drawing is never done. It's just current, until the next RFI. The risk isn't the change; changes are the job. The risk is the twenty feet between 'Rev 6 is issued' and 'the crew is building Rev 6.' Close that gap by making the current revision, and the delta from the last one, impossible to miss. Steel is expensive to move. A clear diff is cheap.