Construction glossary
What is construction document control?
Construction document control is the discipline of making sure everyone on a project is building from the current, approved revision of every document — drawings, specs, submittals, and change orders — and that superseded versions are pulled out of circulation. It covers how revisions are issued, how transmittals record what went out and to whom, how the current set reaches the field, and how dead versions get marked dead so no one builds off them.
Also called: Document control, Drawing control, Revision control, Construction documentation management.
What document control actually manages
Document control answers one question on every drawing and spec sheet: is this the version we should be building from? That means tracking revisions — A-100 Rev C supersedes Rev B — recording transmittals so there's a paper trail of what was issued and when, getting the current set into the hands that need it, and stamping superseded sheets so a foreman doesn't pour against last month's slab layout.
The failures it exists to prevent are concrete: a sub frames off a voided detail, an RFI answer never makes it out to the field, or change order #14 moves a wall that three trades never saw. Good document control is mostly about closing those gaps — making the current revision obvious and the old one unmistakably dead.
Filing the documents vs. reading them
Traditional document control is a filing discipline. It tracks the metadata around a sheet — its revision letter, its transmittal date, who it went to — but treats the document itself as a sealed envelope. The log knows A-100 is now Rev C; it doesn't know what changed on Rev C, or that the change steps on a submittal someone already approved.
When the documents are read, not just filed, control gets sharper. A system that ingests the plan, the spec section, and the change order can connect them — surface that a new revision touches a detail referenced in an open RFI, or that a field photo shows work built to the superseded sheet. The record stops being a folder of versions and becomes a connected one you can question, with the source sheet cited in the answer. That's the line BRAD works on: it reads what you forward, connects it, and answers with the citation attached — it doesn't replace your stamp-and-transmittal process or certify that a revision is correct.
See it on your project
Brad turns the documents and messages that run your job into one shared brain — and answers your team in seconds, with the source attached. Request a demo and bring a project.