The Drawing Is Approved. Did the Workface Receive the Right Revision?
Drawing approval is not the end of document control. Teams need to know which revision reached each workface, when superseded information was withdrawn, and what was actually built.
The short answer
An approved drawing is not controlled at the workface until the project can prove that the correct revision was distributed, superseded information was withdrawn or clearly invalidated, the receiving team understood the change, and the work being installed can be traced to that revision. Approval is one status in the information flow; construction control depends on what people actually used.
That distinction matters because drawing errors are rarely caused by document control alone. The breakdown often occurs at the interfaces between design approval, distribution, subcontractor supervision, printed copies, digital devices, method statements, procurement and site verification. The safest control is an evidence chain from approval to use.
A project example
A structural detail is revised after a coordination review. Revision C is approved and issued through the formal document system. The subcontractor's commercial office receives the transmittal, but a supervisor at Level 12 still has a marked-up print of Revision B in the site folder. The change is visually small but affects an opening dimension. Work proceeds for two shifts before the discrepancy is discovered during the next trade's set-out.
The project can show that Revision C was approved on time, yet that fact does not answer the operational question: did the workface receive and use it? Rework now depends on when the old copy remained available, who was notified, what material was prefabricated, and whether the superseded detail had already influenced other activities.
This is why drawing revision control belongs inside the wider programme-to-site planning chain. Information readiness is one of the conditions that determines whether an activity is truly ready to start.
Separate approval from distribution and verification
Projects often compress three different events into the word “approved.” Design approval means the content has passed the required review. Distribution means the approved information has reached the intended recipients. Workface verification means the team about to install the work has confirmed that the information in use is the current authorised revision.
Each event needs its own evidence. A timestamped approval record does not prove distribution. An email or transmittal does not prove that printed copies were replaced. A digital document portal does not prove that a subcontractor's fabrication drawing or method statement was updated. When those distinctions are explicit, managers can see where the control chain is incomplete.
The objective is not to make supervisors perform document-control administration. It is to make the current construction information easy to identify and wrong information difficult to use.
Build a revision evidence chain
For information that can materially affect installed work, the minimum chain should identify the document number, revision, approval status, approval date, distribution list, affected package or location, superseded revision and any action required from the receiving team. Where a change is significant, link the reason or instruction that created it.
Printed information needs special treatment. Some projects attempt to eliminate paper entirely, but physical copies remain useful in many environments. The control should therefore assume that prints can exist. Use visible revision markings, controlled print dates, designated holders and a routine for removing or stamping superseded copies. Uncontrolled personal notes should never look like approved construction information.
Digital devices create a different risk: cached files or screenshots. A tablet may show yesterday's downloaded PDF even though the portal contains the new revision. The workface check should focus on document identity and revision, not on whether the user opened a particular app.
Connect revisions to work packages and locations
A drawing register tells document control what changed. Operations need to know where the change matters. Linking drawings to packages, systems, zones or programme activities allows the team to assess impact quickly. A revised riser detail may affect only one location; a changed specification note may affect dozens of prefabricated items.
This mapping also improves distribution. Rather than broadcasting every revision to everyone, the system can identify the subcontractor, supervisor, procurement package and active workface likely to be affected. The receiving team is more likely to recognise the importance of the update when the context is clear.
A project-centric ERP such as Saturn can provide the common project and package context around documents, procurement and site records. The point is not to claim that ERP replaces a common data environment. The value is in connecting information status with the operational and commercial records that depend on it.
Make superseded information visibly unusable
Revision control fails when the current version is available but the old version remains equally convenient. A strong process makes the approved current version obvious and the superseded version unmistakable. Archive access may still be required for audit, claims or as-built history, but historical information should not look like live construction information.
At the workface, this means removing replaced print sets, updating drawing boards, controlling document packs used for permits or inspections, and checking subcontractor-controlled copies. For high-risk changes, a targeted briefing may be more reliable than a generic transmittal.
The project should also consider derived information. Shop drawings, cutting lists, material orders, setting-out files and method statements may have been created from the superseded revision. Replacing the base drawing does not automatically correct those downstream artefacts.
Verify before irreversible work
Not every task needs a formal revision check. Focus on points where the cost of correction rises sharply: before concrete pours, closures, fabrication release, penetration cutting, equipment installation, testing or handover. A brief verification at those decision gates can prevent significant rework.
Verification should be proportionate. It can be a supervisor check against the controlled drawing list, a permit reference, an inspection request that records drawing revision, or a digital work package that displays the current approved set. The important feature is traceability: if a problem is found later, the team can see what information was expected at the time.
This practice also strengthens quality records. Inspection evidence becomes more meaningful when it identifies the information against which the work was checked.
Treat revision changes as planning events
A drawing change can alter sequence, access, material, labour and plant requirements even when its commercial value is still being assessed. The planning team should therefore know which active or near-term activities are affected. If the revision invalidates prefabricated material or changes a prerequisite, workface readiness must be reconsidered.
This is where contextual links between document control and planning matter. The planner does not need to review every drawing. The system should surface revisions attached to active work packages and show whether an operational response is still open.
For a related example of resource consequences, see how shared plant decisions are handled when the crane is busy and activities compete for priority.
Five practical controls
1. Distinguish approved, distributed and workface-verified states. Do not let one status imply all three.
2. Map critical drawings to work packages and locations. This turns a register into operational context.
3. Control superseded physical and digital copies. Make history available for audit but hard to mistake for current information.
4. Check revision identity before irreversible work. Use proportionate gates at high-consequence points.
5. Assess downstream artefacts after a revision. Shop drawings, orders, set-out data and method statements may also need change.
These controls work best when ownership is clear. Document control governs the formal record; design leads resolve technical status; package managers assess operational impact; supervisors verify workface use. No single team can close the chain alone.
What management should measure
Useful indicators are not simply the number of drawings issued. Measure conditions that reveal exposure:
- active work packages with an approved revision not yet acknowledged by the responsible team;
- superseded drawings still attached to live work packs;
- high-consequence inspections that do not record drawing revision;
- revisions affecting near-term activities without an impact assessment;
- rework events traced to obsolete or ambiguous information;
- time between approval and verified workface distribution for critical documents.
The goal is to identify where the project is vulnerable before incorrect work is installed.
Frequently asked questions
Is document control responsible if an old drawing is used on site?
Document control owns important parts of the formal issue process, but workface use is a shared operational control. Supervisors, package managers and subcontractors must ensure that the information being used for installation matches the current authorised revision.
Should all superseded drawings be deleted?
No. Historical revisions may be required for audit, change analysis, claims and as-built records. They should be retained in a clearly historical state and separated from the live construction set so they cannot be mistaken for current information.
Can a common data environment solve the problem by itself?
A common data environment can greatly improve control of approved files, but teams still need distribution, workface verification and downstream change management. Technology cannot assume that every cached file, print, fabrication record or subcontractor pack changed automatically.
How can the process avoid slowing the site?
Use targeted controls at meaningful decision points rather than asking for repeated checks everywhere. Make the current revision easy to identify, map it to the work package, and include revision identity in processes the team already performs, such as permits or inspections.