Document Control & the Single Source of Truth

Welcome

Hello, and welcome. This is Super Structures General Contractors — a national general contractor headquartered in Powhatan, Virginia — here to help you and your clients build something that lasts. We're glad you're with us, and we look forward to connecting with you.

Alright, Document Control & the Single Source of Truth. Don't let the plain title fool you. Here's the part that actually matters on the job: Document control means one current set everyone builds from, a documented trail of every revision that changed it, and nothing superseded ever thrown away. Learn it well and you'll never again tear out a wall that was built right to the wrong sheet.

The intro course said the platform keeps everyone on the current drawings. That only happens if a person runs a process. This lesson is the process.

What the project record is made of

The contract documents are the agreement, the general and supplementary conditions, the drawings, the specifications, and the addenda issued before award. After award the record grows: architect's supplemental instructions and bulletins, sketches, RFI responses, reviewed submittals and shop drawings, change orders and construction change directives, field directives, meeting minutes, schedules, daily reports, inspection reports, photos, and at the end the closeout documents.

Two ideas govern it. The order of precedence clause in your contract decides which document wins when two disagree; a common pattern puts specifications over drawings, large-scale details over small, and later over earlier, but it varies, so read yours. The current set is the original sheets with every revision incorporated, usually starting from a conformed set at award.

The document controller role

Somebody owns it by name. On a large project that is a document controller; on a small one it is the project engineer or the PM, written into the project setup. The duties are receive, log, compare, distribute, post, supersede, confirm acknowledgment, and archive. The tools are logs: a drawing log with revision history by sheet, an RFI log, a submittal log, a change log, and a transmittal log.

Managing revisions

• Log it the day it arrives, with the issue date and what it affects.
• Compare it. Overlay or compare tools show exactly what changed on the sheet, which is more than the revision clouds always show.
• Slip-sheet it. The new sheet replaces the old in the current set; the old sheet moves to superseded with its history intact. Never overwrite.
• Link it. Hyperlink RFI responses, sketches, and reviewed shop drawings to the affected sheets so a foreman tapping a detail on a tablet sees the answer next to it.
• Transmit it. Send a transmittal to every affected trade stating what changed, and require acknowledgment. A sub that has already fabricated to the old revision needs to know today.
• Update the spec book too. Addenda and bulletins revise specifications as well as drawings.

Field markups follow the same discipline: each trade maintains as-built redlines on the current set, reviewed weekly, which become the record drawings at closeout.

Naming, structure, and permissions

Keep the design team's sheet numbering, and name files with project, discipline, sheet, revision, and date so a file is identifiable out of context. Use one folder structure template on every job. Set permissions by role: subs see the drawings, specifications, RFIs, and submittals that concern them; the owner sees what the contract says; internal cost documents are locked. Turn on the audit trail of who viewed and downloaded, and remove access the day someone leaves.

ISO 19650 describes a common data environment in which information moves through states, roughly work in progress, shared, published, and archived, with status and revision codes on every container. Even if you never adopt the standard, those states are a sound mental model: nothing is built from a document that has not reached the published state.

Making the field trust it

The rule is simple to state and hard to keep: the field builds only from the platform's current set on a device. Printed sets are allowed for marking, dated when printed, and treated as scratch paper. The foremen's weekly meeting opens with a current-set check: which sheets changed this week, what the changes were, and who acknowledged. The two classic failures are the superseded sheet taped to the trailer wall and the sub working from its own bid-time copy.

Going Deeper (Intermediate)

Submittals are install documents. A reviewed shop drawing marked approved as noted or revise and resubmit carries conditions that must reach the crew installing from it, and the detail drawings must be reconciled with the contract drawings they interpret. RFI hygiene matters too: one question per RFI, sheet and detail referenced, a proposed solution, a needed-by date tied to the schedule, and the response posted to the sheet. An RFI whose answer changes scope triggers the change process, and the document controller is often the first to notice.

Advanced / Pro-Level

Pros control the model in the same environment as the sheets, with the BEP stating which governs when they disagree. They measure the process: time from receipt to distribution, outstanding acknowledgments, and RFI cycle time by reviewer. At closeout they deliver record drawings, operation and maintenance data, warranties, test reports, and the full logs in a durable export, and they archive the whole record for the retention period the contract and the applicable statutes of limitation and repose require, which varies by state.

Practice Challenge

An electrical foreman roughs in a room from a printed sheet dated at bid time. Bulletin 4, issued three weeks ago, moved the panel. The drywall is already on. What happened, and what do you fix? (Answer: the first failure is control, not the foreman — bulletin 4 was received but the printed set was never superseded and the sub was never transmitted the change with an acknowledgment; fix the work and document the cost, then fix the system by pulling every printed set, requiring the field to work from the platform, adding the acknowledgment step to every transmittal, and running the weekly current-set check.)

In Practice

A project engineer who logs, compares, slip-sheets, links, and transmits every revision the day it arrives runs a job where the sub's foreman sees the new panel location on the tablet before coffee. A project engineer who forwards the bulletin email and assumes everyone read it finds out at the inspection.

Common Mistakes to Avoid

• No named owner of document control, so revisions sit in an inbox
• Overwriting or deleting superseded documents instead of archiving them
• Distributing a revision without saying what changed or confirming receipt
• Updating the drawings but not the specifications
• Tolerating printed sets on the wall and bid-time copies in the subs' trucks

Takeaway: Document control means one current set everyone builds from, a documented trail of every revision that changed it, and nothing superseded ever thrown away.

Educational content only — not design, engineering, surveying, or legal advice, and not a substitute for training, your company's procedures, or review by a licensed design professional or surveyor. Software and hardware are described as generic categories and no product is endorsed. Follow the applicable codes and regulations as adopted in your jurisdiction, your contract, and the manufacturer's instructions for every instrument and device.