I'm an electrical contractor, and the costliest rework I've ever eaten wasn't a mistake by the crew. They did beautiful work — off a drawing that had been revised two weeks earlier. Nobody told the field. The current set was in someone's email; the set on the job was the old one. A day of labor and material, gone, plus the schedule hit, because the crew built exactly what they were shown and what they were shown was wrong.

Why the wrong set ends up in the field

Drawings change constantly on an active job — RFI responses, addenda, revisions. Each change supersedes the last. The trouble is distribution: the new set lands in the office, but the crew is working off the PDF that got printed or texted three revisions ago. There's no malice and no carelessness. There's just no single place that says, with certainty, "this is the one you build from today."

The crew will build exactly what you put in front of them. If it's the old revision, that's not their mistake — it's a distribution problem.

Revision control, in plain terms

Revision control means every drawing has a clear lineage: when a new revision comes in, it supersedes the old one, and the old one is marked as such instead of just sitting around looking equally valid. Two things have to be true for it to actually protect you:

  • The field sees only the current set by default. If you have to dig to find the right one, someone will grab the wrong one.
  • Superseded sheets are loudly flagged. Not deleted — you keep them for the record — but clearly marked so nobody builds from them by accident.

Current by default, history on demand

The goal is simple: a tech pulls up the drawings on a phone and sees the current revision, full stop. The old ones still exist — you need them for disputes and as-builts — but they're behind a "show superseded" filter and stamped with a warning, not mixed in with the live set. When "the current set" is unambiguous and always in the crew's pocket, the wrong-revision day stops happening.

Keep the history — you'll need it. Superseded drawings are evidence. When there's a dispute about what was in the contract documents when the work was done, that supersede chain is exactly what protects you. Revision control isn't about deleting the old; it's about making sure nobody builds from it.

The one-minute version

  • Building off a superseded revision is a distribution problem, not a crew mistake.
  • Revision control gives every drawing a clear, superseded-or-current lineage.
  • Show the field the current set by default; flag superseded sheets loudly.
  • Keep the old revisions for disputes and as-builts — just don't let anyone build from them.