Ask most people on a construction project what a Document Controller does and you will get one of two answers: a vague gesture toward “filing” or a blank look entirely. Yet in the background, a good Document Controller is one of the most operationally critical people on any project. When the role is done well, information flows smoothly, the audit trail is clean and nothing falls through the cracks. When it is not done — or done badly — the consequences surface in disputes, delays, missed approvals and handover failures.

This article explains exactly what a Document Controller does, why the role matters far more than most clients realise, and how to decide whether your project needs one.

It Is Not Filing

The filing misconception is understandable but costly. A Document Controller does not simply store documents — they manage the entire lifecycle of project information: how it is created, named, issued, reviewed, approved, revised, distributed and archived. On a live construction project, that means hundreds or thousands of documents moving between the client, design team, contractor and subcontractors at any given time, each with its own revision history, status and required action.

Getting that wrong — even occasionally — has real consequences. A contractor building to a superseded drawing. An approval not issued because the transmittal went to the wrong person. A planning condition left undischarged because nobody tracked the submission. These are not hypothetical scenarios. They happen on projects where document control is treated as an afterthought.

What a Document Controller Actually Does

Transmittal Management

Every time a document is formally issued between parties on a construction project, it should be accompanied by a transmittal — a formal record of what was sent, to whom, on what date, for what purpose (for information, for comment, for approval, for construction) and at what revision. The Document Controller creates, issues and tracks these transmittals, ensuring that every submission has a documented audit trail and that responses are received and recorded within agreed timeframes.

Revision Control

Construction documents go through multiple revisions. A drawing that starts as Revision A for comment will typically pass through several more iterations before it reaches Revision P1 for construction. The Document Controller maintains the master register of current revisions, ensures that superseded versions are correctly archived and that the team is always working from the current issue. This sounds straightforward. On a project with thousands of drawings and hundreds of consultants, it is anything but.

Naming Convention Compliance

Under ISO 19650 — the international standard for information management in construction — every document and file must follow a defined naming convention that encodes the project, originator, volume, level, type, role and number into a structured string. The Document Controller enforces this convention, checking incoming submissions for compliance and rejecting or correcting non-compliant files before they enter the Common Data Environment. Without this discipline, the CDE quickly becomes unusable.

Common Data Environment Administration

Whether the project uses Autodesk Construction Cloud, Aconex, Asite, SharePoint or another platform, the Document Controller typically administers the CDE — setting up folder structures, managing user permissions, configuring workflows and ensuring that documents move through the correct approval stages before being published to the wider team. They are, in practice, the custodian of the project’s information environment.

Tracking Outstanding Actions

A significant part of the Document Controller’s role is chasing. Submissions that have been sent for approval and not responded to within the agreed period. RFIs that have been open for weeks. Inspection requests that have not been acknowledged. The Document Controller maintains the registers that track these outstanding actions and reports on them regularly, ensuring that nothing is forgotten and that the project team is accountable for their responses.

Handover Documentation

At the end of a project, the client is entitled to receive a complete set of as-built information, O&M manuals, warranties, certificates and compliance documentation. Compiling this package — known as the Health and Safety File under CDM 2015 and the Golden Thread under the Building Safety Act 2022 — is a major undertaking that begins long before practical completion. A Document Controller who has maintained rigorous records throughout the project makes this process orderly. One who has not makes it a crisis.

Does Your Project Need a Document Controller?

The honest answer is that almost every construction project of meaningful complexity does. The question is really about scale and how the role is resourced.

Small Projects

On a straightforward single-discipline project with a small team and a short programme, document control can often be absorbed into the Project Manager or Design Manager’s role, provided they have the discipline and the tools to do it properly. The risk is that it gets deprioritised when the project gets busy — which is exactly when good records matter most.

Medium and Large Projects

On any project with multiple consultants, a main contractor, specialist subcontractors and a live CDE, a dedicated Document Controller is not a luxury — it is a necessity. The volume of information in play makes it genuinely impossible to manage effectively as a secondary responsibility. The cost of a Document Controller is a fraction of the cost of a single dispute that arises from a poorly maintained audit trail.

Projects Under the Building Safety Act

For higher-risk buildings — those over 18 metres or seven storeys containing two or more residential units — the Building Safety Act 2022 has introduced a statutory duty to maintain the Golden Thread of information throughout design, construction and occupation. This is, in effect, a mandatory document control requirement with legal consequences for non-compliance. If your project falls within scope, a Document Controller is not optional.

What Good Document Control Looks Like in Practice

Good document control is largely invisible — it is noticed only when it is absent. On a well-run project, the team always knows the current revision of every drawing, every transmittal has a response, the CDE is clean and navigable, and handover documentation arrives complete and on time. The Document Controller behind that outcome has typically been working quietly and consistently throughout the project, enforcing standards that everyone else finds slightly inconvenient but ultimately relies on.

Poor document control looks very different. Multiple versions of the same drawing in circulation. Transmittals that were never responded to because nobody knew they existed. A CDE that nobody uses because it was set up incorrectly and never maintained. A handover package that takes months to compile because the records were never kept in the first place. And, eventually, a dispute in which nobody can prove what was issued, to whom and when.

How JC Virtual PMs Can Help

At JC Virtual PMs, our Document Controllers are experienced professionals who understand both the technical standards — ISO 19650, CDE workflows, naming conventions — and the practical realities of keeping information moving on a live construction project. We work with the platforms your project uses, from Autodesk Construction Cloud to Aconex, Asite and SharePoint, and we embed seamlessly into your project team from day one.

Whether you need dedicated document control support from project inception or help bringing order to an existing project, get in touch to discuss how we can support your information management needs.