What is the role of a document controller?
A document controller keeps the project's documents orderly so that nobody works from an outdated drawing or loses a critical letter. They sit between the design team, the site and the commercial team, and they own the register of what exists, what revision is current and who has it. On larger projects the role may be a team; on smaller ones it is often combined with project administration.
What are the core duties?
- Maintain the document register. Every drawing, specification, letter, report and form gets a unique number, a title, a revision and a status.
- Set and enforce naming and numbering. A consistent convention makes search and handover possible. Our guide to ISO 19650 in construction covers a recognised approach to naming and information management.
- Control revisions. Superseded drawings must be clearly marked, and the right revision must reach the site. Misreading a revision is a common cause of rework.
- Issue transmittals. Each issue is recorded with what was sent, to whom, in which revision and for what purpose. Start from the free transmittal template.
- Track approvals and responses. Submittals, RFIs and other items have due dates and statuses; the controller chases and reports on them. See RFI vs submittal vs ball in court.
- Archive and hand over. At completion, the controlled set and records are compiled for the employer. Our closeout checklist shows what is usually expected.
What does a typical day look like?
Logging the morning's incoming mail and drawings, checking new revisions against the register, issuing transmittals, updating the submittal and RFI trackers, answering "which revision is current?" questions from site, and preparing the weekly overdue list for the project manager.
What goes wrong without document control?
Teams build from superseded drawings, approvals sit in inboxes, and during a dispute nobody can show what was issued when. We describe the pattern in signs your document management is broken.
What tools support the role?
A shared drive and spreadsheet register work on small projects but demand discipline. A dedicated system adds version history, access control and an audit trail. Arkan's Document Control organises files in a folder tree, keeps every version with who uploaded it and when, lets earlier versions be restored, and applies visibility settings and encrypted folders. Documents can be submitted for review and approved or rejected through approval workflows. For a fuller comparison of options, read our guide to construction document management systems.
How do you get better at the role?
- Write a short document control procedure and get it agreed at project start.
- Keep one register and make it the source of truth.
- Reconcile the register against what is actually on the system or drive each week.
- Tell people early when something is overdue, not after.
If you want to see how a document controller would work in Arkan, book a demo.