Construction Document Control: The Basics Every QS Should Know

You join a project three months in. The previous QS has moved on. There is a shared folder on the server with hundreds of files in no particular order. The drawing register was last updated six weeks ago. There is no variation register. The RFI log is a spreadsheet someone started and then abandoned after the first dozen entries.

The project is behind programme. The client is asking questions. The contractor has already submitted a preliminary extension of time claim. And somewhere in that folder of unorganised files is the evidence that will determine whether the commercial position of this project is defensible or not.

This is not an extreme scenario. It is a version of what QS professionals encounter regularly when they step into an established project — or when a project they have been running has grown faster than the document system supporting it.

Document control is not a bureaucratic overhead. For a QS, it is the infrastructure that makes everything else possible. Accurate quantities depend on working from the right drawing revision. Defensible valuations depend on a complete record of instructed variations. Successful EOT claims depend on a correspondence trail that proves notice was given correctly and on time.

This guide covers the document control basics that every QS should have in place from the first day of a project — not as an aspiration, but as a minimum professional standard.

Why Document Control Is a QS Responsibility, Not Just an Administrative One

On large projects, document control is a dedicated function — a document controller who maintains the registers, manages distributions, and keeps the system current. On smaller projects, and often on mid-size ones too, that function falls to the QS by default.

Even on projects where a document controller exists, the QS has a specific interest in document quality that goes beyond the general project record. Every commercial decision the QS makes — every valuation, every variation account, every EOT submission — depends on documents that were issued at a specific revision, on a specific date, to specific parties. If those documents cannot be produced in an organised, traceable form, the commercial position of the project is exposed.

A QS who treats document control as someone else's problem and focuses only on the numbers will eventually face a dispute where the numbers are right but the evidence to support them is missing. At that point, being technically correct is not sufficient.

The Seven Documents Every QS Must Keep in Order

The table below covers the document types that directly affect the QS's ability to manage cost, value work, and defend the project's commercial position. Each one is described by what the QS uses it for and what breaks down when it is absent or poorly maintained.

Every one of these documents exists on every construction project. The question is not whether they will be produced — it is whether they will be organised and maintained in a way that makes them retrievable and usable when they are needed.

The Drawing Register: Your First Line of Defence

The drawing register is the most fundamental document control tool the QS uses. Every quantity in the working papers, every item description in the BOQ, every rate applied in a valuation — all of them depend on the assumption that the measurement was taken from the correct drawing at the correct revision.

Without a current drawing register, that assumption cannot be verified. The QS who measures from a superseded drawing, values a variation using obsolete dimensions, or issues a payment certificate based on quantities from a drawing that has since been revised is building commercial decisions on an unreliable foundation.

A drawing register that serves the QS's needs must include:

•       Drawing number and title: The unique identifier for every drawing in the project set — structured consistently so any drawing can be found in seconds

•       Current revision and date: The revision letter and issue date of the most recent version — updated on the day each new revision arrives

•       Issue purpose: Whether the drawing is issued for information, for comment, for construction, or superseded — a drawing issued for information is not authorisation to build or measure for contract purposes

•       Distribution record: Which parties have been issued the current revision and when — the QS's evidence that they were working from the correct version

•       Revision history: Previous revisions archived and referenced — so when a quantity is questioned, the evolution of the design can be traced

The drawing register also connects directly to how quantity data stays current when revisions arrive. For a detailed guide on managing the quantity impact of drawing revisions, see our article on How to Handle Drawing Revisions Without Losing Your Quantity Data.

The RFI Log: Managing the Questions That Affect Your Quantities

A Request for Information is the formal mechanism for clarifying ambiguities, gaps, or conflicts in the contract documents. For the QS, an RFI is not just a design coordination tool — it is a commercial instrument.

When a contractor submits an RFI asking how a particular junction detail should be constructed, the response determines what gets built. What gets built determines what gets measured. What gets measured determines what gets paid. An RFI that remains unanswered for three weeks while work continues is not just a design problem — it is a quantity and cost problem that will surface at valuation.

What the RFI Log Must Capture

Every RFI submitted or received should be logged with sufficient detail to make the record useful, not just complete. A log that records only the RFI number and date is a register. A log that records the question, the drawing or specification it relates to, the date submitted, the date a response is due, the date responded, and the commercial impact of the response is a management tool.

The RFI log fields that matter to the QS:

•       RFI number and date submitted: Unique reference and submission date for tracing and response tracking

•       Drawing or specification reference: Which document triggered the question — links the RFI to the quantity record

•       Question summary: Brief description sufficient to understand the issue without reading the full RFI

•       Response due date: Contract or agreed response period — flags overdue responses before they impact work

•       Response received date: When the answer arrived — important for delay analysis if the response was late

•       Commercial impact: Whether the response generates a variation, changes a quantity, or has no commercial consequence — assessed by the QS after response receipt

An RFI that generates a variation should be cross-referenced to the variation register. An RFI response that changes a dimension should trigger an update to the relevant quantities in the working papers. These links are what keep the commercial record coherent rather than fragmented across separate documents.

The Variation Register: Where Commercial Control Lives

The variation register is arguably the single most important commercial document the QS maintains. Every scope change, every instructed addition or omission, every adjustment to the contract sum flows through the variation register. A project whose variation register is well maintained arrives at final account with a clear, auditable history of every change. A project without one arrives at final account with a dispute.

What a Variation Register Must Include

The variation register is not just a list of variation numbers and brief descriptions. For the QS, it is the primary tool for tracking the financial exposure of the project against the contract sum throughout construction.

Each entry in the variation register should capture:

•       Variation number: Sequential unique reference — never reuse a number, never leave gaps

•       Description: Clear summary of the scope change — sufficient to identify the variation without reading the full instruction

•       Instruction reference: The formal instruction that authorises the variation — a variation without a formal instruction is a claim, not a variation

•       Date instructed: When the instruction was issued — relevant for programme impact assessment

•       Estimated value: The QS's assessment of the likely cost — updated as the valuation develops

•       Agreed value: The final agreed sum — recorded when agreement is reached and referenced to the agreement correspondence

•       Status: Instructed, under valuation, agreed, or disputed — the current commercial position of each variation at a glance

The variation register also serves as the early warning system for budget control. When the cumulative estimated value of all variations begins to approach the contingency budget, the client needs to know before commitments are made that push the project beyond its financial envelope. The register makes that conversation possible with evidence rather than estimates.

Transmittals: The Document That Proves What Was Sent and When

A transmittal is a formal cover record that accompanies documents issued between parties. Its purpose is simple: it creates a verifiable record that a specific document, at a specific revision, was sent to a specific party on a specific date.

In ordinary project conditions, transmittals seem like administrative overhead. On a project that goes to dispute, they are some of the most valuable documents in the file. The question 'did you receive the revised drawing before you started that work?' has a definitive answer when a transmittal record exists, and a contested one when it does not.

Every significant document issue — drawings, specifications, BOQ amendments, variation instructions, responses to RFIs — should be accompanied by a transmittal. The transmittal does not need to be elaborate. It needs to record what was sent, who sent it, who received it, and when.

The transmittal record connects directly to the broader question of how construction documents are organised and tracked across the project. For a full guide to construction document organisation and the habits that support it, see our article on How to Organise Construction Documents So Nothing Gets Lost.

Setting Up Document Control on a New Project

The best time to set up document control is before the project starts. The second best time is the day you join. The worst time is six months in, when the system has never existed and the project is already mid-construction.

On a new project, the document control setup takes half a day. On an established project with no existing system, it takes longer — but the cost of not doing it grows with every week that passes.

The minimum setup for a QS joining a new project:

•       Drawing register: Created from the initial drawing issue, current from day one, updated with every subsequent revision

•       RFI log: Opened immediately, even if no RFIs have been submitted yet — the structure is ready when the first one arrives

•       Variation register: Opened at contract award — the structure exists before the first variation is instructed, not after

•       Correspondence folder: A clearly structured filing system for all project correspondence — organised by date and subject, not by whoever received the email first

•       Transmittal log: A record of all significant document issues — started from the first drawing package, maintained consistently throughout

These five elements take hours to set up and weeks or months to prove their value. That asymmetry is what causes teams to deprioritise them when a project is moving fast. The projects that maintain them consistently are the ones that reach final account without a major dispute — not by accident, but because the evidence was always there.

Document control is also the foundation of every successful Extension of Time claim. An EOT submission without a clear record of delay notices, RFI response timelines, and instruction dates is an EOT submission without evidence. For a complete guide to EOT procedures and what they require from the document record, see our article on Extension of Time (EOT) in Construction: A Practical Guide for Engineers and Contractors.