The short answer: Construction document control is the process of registering, numbering, reviewing, approving, issuing and archiving project documents so that everyone works from the current, approved version. It covers drawings, specifications, BOQs, contracts, method statements and correspondence, and it rests on four things: a register, a numbering and revision system, an approval workflow and a record of who received what.
The structural consultant issues Revision C of the L5 slab drawing on Monday, moving two beams. The site office prints it. The bar-bending contractor is still cutting steel from Revision B, which is pinned to the wall of his yard, two kilometres away. Nobody did anything unusual. The new drawing simply never reached the person who needed it.
Document control exists to prevent exactly this. It is not an admin job for a large company; on any project with more than one drawing revision, it is the difference between building what was designed and building what someone remembered. This guide covers how to set it up on a building project, step by step.
What is document control in construction?
Document control is the system that answers four questions about any project document at any moment:
- What is the current version?
- What status is it? For information, for approval, approved, or good for construction.
- Who has it? Which people and contractors received it, and when.
- What changed? And who approved the change.
If your team can't answer all four in under a minute, the site is relying on memory, and memory is how old drawings get built.
Why document control matters
- Rework: work built to a superseded drawing has to be broken out and redone, often after other trades have built on top of it.
- Cost and time claims: without a dated record of what was issued, it is hard to show whether a change came from the designer, the developer or the contractor.
- Quality and safety: structural and MEP changes that don't reach site can create real risk, not just cosmetic defects.
- Approvals and compliance: authorities and lenders expect approved plans and records that match what was built.
- Handover: as-built drawings and O&M documents are only as good as the revision history behind them.
We covered the most common failure in the most dangerous drawing on a construction site: the superseded one that nobody withdrew. This guide covers the whole system around it.
Which documents need control?
| Document type | Examples | Typical approver |
|---|---|---|
| Design drawings | Architectural, structural, MEP, landscape | Design consultant, then PM / developer |
| Good-for-construction (GFC) drawings | Drawings released for building | Consultant and developer |
| Shop and fabrication drawings | Steel, façade, joinery, bar bending schedules | Contractor prepares; consultant approves |
| Specifications and BOQ | Material specs, item descriptions, quantities | QS / consultant / developer |
| Contracts and work orders | Main contract, subcontracts, amendments | Developer / legal |
| Method statements and ITPs | How work is done and inspected | Consultant / QA |
| Material submittals | Samples, data sheets, test certificates | Consultant |
| Correspondence and instructions | Site instructions, RFIs, letters, minutes | PM |
| As-built and handover documents | As-built drawings, manuals, warranties | Contractor prepares; PM / consultant accepts |
The drawing register: the heart of document control
A drawing register (or document register) is a single list of every controlled document with its current revision and status. At minimum it should hold:
| Field | Example |
|---|---|
| Document number | SKY-B-STR-L05-201 |
| Title | Tower B, Level 5 slab reinforcement |
| Discipline | Structural |
| Current revision | C |
| Status | Good for construction |
| Date issued | 09 Nov 2026 |
| Issued to | Site engineer B, bar-bending contractor, formwork contractor |
| Transmittal reference | TR-0143 |
| Superseded revision | B (withdrawn from site 09 Nov) |
| Change summary | Beams B12 and B14 relocated; see revision cloud |
The register must be the single source of truth. If a drawing exists on the site office wall but not in the register, or the register says Rev C but the contractor has Rev B, the system has already failed.
Document numbering and revision conventions
A good numbering system tells you what a document is without opening it. A common structure is:
e.g. SKY-B-STR-L05-DR-201
Keep these rules simple and agree them before the first drawing is issued:
- Use the same codes for buildings, levels and disciplines as the schedule and BOQ.
- Never reuse a number for a different document.
- Separate revision from number: the number stays the same; only the revision changes.
- Use a clear revision sequence (for example, letters or numbers, with a different prefix for preliminary and construction issues), and stick to it.
- Mark every change on the drawing with a revision cloud and a revision note.
Projects working to ISO 19650, the international standard for information management using BIM, use a structured naming convention and a common data environment in which information moves through work-in-progress, shared, published and archived states, with an agreed approval step between each. You don't need full BIM to borrow the idea: draft, shared for review, approved for construction, superseded.
Document status codes
| Status | Meaning | Can site build from it? |
|---|---|---|
| Draft / work in progress | Being prepared by the author | No |
| For information | Shared so others can see the direction | No |
| For review / approval | Submitted to the consultant or client for comment | No |
| Approved with comments | Accepted subject to listed changes | Only if the contract allows, with comments incorporated |
| Good for construction (GFC) | Released for building | Yes |
| Superseded | Replaced by a newer revision | No; withdraw from site |
| As-built | Records what was actually built | Record only |
The document control workflow, step by step
- Receive and register. Every incoming document is logged with number, revision, date and status before it is used.
- Check. Confirm the number, title block, revision cloud and status are correct and complete.
- Review and approve. Route to the right reviewer with a deadline. Record comments and the response.
- Issue with a transmittal. Send the approved document to everyone who works from it, with a transmittal listing what was sent, to whom and why.
- Withdraw the old revision. Collect or stamp superseded prints "SUPERSEDED" and remove them from the work front and contractors' yards.
- Confirm receipt. Get acknowledgement from each recipient, especially subcontractors.
- Brief the site. Walk the affected supervisors and foremen through what changed.
- Archive. Keep every revision and its approval record. Never delete history.
How drawing changes turn into cost and time
Not every revision is a variation, but many are. When a revision changes scope, quantity or sequence, link it to the commercial process:
- Record the revision and its reason (design development, client change, error correction, site condition).
- Check the impact on BOQ quantities, materials already ordered and work already built.
- Raise a site instruction or variation where the contract requires one, before the work is done.
- Update the schedule if the change affects the critical path.
Our guide to construction cost control covers how variations are tracked against budget.
Making sure the site uses the latest drawing
The register can be perfect and the site can still build from the wrong drawing. Close the last metre:
- One place for current drawings, on paper and on phones, and nothing else on the walls.
- Stamp or collect superseded prints the same day the new revision arrives.
- Include subcontractors' yards and fabrication shops, not just the site office.
- Check before critical work. Before a pour or a fabrication run, the engineer confirms the revision on the work front against the register.
- Put the revision in the daily report for key activities, so it is visible if something goes wrong.
10 document control mistakes that cause rework
- No single register, or several registers that disagree.
- Drawings shared by forwarding chat messages, with no record of who received them.
- Old prints left on site after a revision.
- Revision clouds missing, so nobody can see what changed.
- The same number used for different drawings.
- Building from "for approval" drawings because GFC drawings are late.
- Consultant comments not tracked to closure.
- Shop drawings approved but not linked to the design revision they were based on.
- Verbal changes on site that never reach the designer or the register.
- As-built drawings left until the end, when nobody remembers what changed.
Who is responsible for document control?
On larger projects, a dedicated document controller maintains the register, transmittals and archive. On smaller projects the role usually falls to the project manager, a project engineer or the site engineer. Either way, responsibilities should be explicit:
- Authors (consultants, contractors) are responsible for the content and correct revision of their documents.
- The document controller is responsible for registering, distributing and archiving.
- The project manager is accountable for the system working and for withdrawal of superseded documents from site.
- Site engineers are responsible for confirming the current revision before work starts.
Document control checklist
- Is there one register for all controlled documents, with current revision and status?
- Is the numbering convention agreed and written down?
- Does every issue go out with a transmittal?
- Are superseded prints withdrawn from site and contractors' yards the same day?
- Do subcontractors acknowledge receipt of new revisions?
- Are revisions with cost or time impact linked to a site instruction or variation?
- Can the site engineer confirm the current revision of any drawing on a phone in under a minute?
- Are as-built changes recorded as they happen?
Where software fits
Spreadsheets can hold a register, but they can't stop someone opening an old PDF from a chat. Document control software helps when it keeps one current version, shows status and history, and controls who can see what.
In Brikito, construction management software with Brik AI, drawings, BOQs, agreements and contracts live in a version-controlled Documents tab, with the latest revision always tagged on site. Drawing sign-offs can be approved by the PM inline in chat, and anyone on the project can ask Brik which revision is current. Access is scoped by role, so contractors see what they need and not the rest.
Frequently asked questions
What is document control in construction?
It is the process of registering, numbering, reviewing, approving, distributing and archiving project documents, such as drawings, specifications and contracts, so that everyone works from the current approved version and there is a record of every change.
What is a drawing register?
A drawing register is a list of every project drawing with its number, title, current revision, status, issue date, recipients and transmittal reference. It is the single source of truth for which drawing is current.
What are GFC drawings?
GFC (good for construction) drawings are drawings formally released for building. Drawings marked for information or for approval should not be used for construction.
What is a transmittal in construction?
A transmittal is a record that accompanies issued documents, listing what was sent, the revision, the recipients, the date and the purpose. It proves who received which version and when.
How do you make sure the site uses the latest drawing?
Keep current drawings in one place, issue every revision with a transmittal, withdraw or stamp superseded prints the same day, include subcontractors and fabrication yards, and check the revision on the work front before critical activities such as pours.
Who is responsible for document control on a construction project?
A document controller usually maintains the register and distribution on larger projects; on smaller ones it is the project manager or an engineer. Authors are responsible for document content, and the PM is accountable for the system working on site.
One version, one place, one record
Document control is simple to describe and easy to let slip: one register, one numbering system, one approval path, and a record of who received every revision. Get those right, withdraw old drawings the day new ones arrive, and you remove one of the most common causes of rework on site.