A drawing arrives in your inbox with a newer revision letter. Does that mean it is ready for the next work package? A project coordinator needs more than a recent email or a familiar file name to answer that question. A useful construction drawing register connects each drawing with its identity, revision, stated purpose, controlled location and issue record.
This guide explains a practical coordination check. Follow your project's document-control procedure, agreed responsibilities and authorised instructions. A register records information; it does not approve a design, authorise construction, replace technical review or determine contractual rights.
1. Confirm what the register controls
Start by identifying the controlled system and the person responsible for maintaining it. Your project may use a common document platform, a managed spreadsheet or another approved arrangement. Confirm which source team members must consult and who can change the recorded status.
Ask how drawing issues are communicated, how superseded versions are retained and how recipients know that an update needs attention. A private spreadsheet copied from the main system can become a competing source. If you need a temporary working list, label its purpose and date and check it against the controlled source before relying on it.
2. Keep identity, revision and purpose separate
A drawing number identifies a document. A revision identifies a version of that document. Its stated purpose or status describes the intended use under the project's conventions. Record these separately rather than assuming that a higher number or later letter means permission to build.
Adapt the following fields to the approved register:
- Drawing identity: project reference, drawing number, title, discipline and relevant work area.
- Revision: the revision shown on the drawing and the corresponding issue date.
- Purpose or status: the wording or code used by the project, with its meaning confirmed.
- Controlled location: a link or document reference that opens the intended file.
- Issue evidence: the transmittal or other authorised issue reference and date received.
- Follow-up: the responsible role, unresolved question and reference to its tracking record.
Use the exact project conventions. Do not invent a status code, translate “for coordination” into “for construction”, or combine several disciplines into one revision entry when their documents have different histories.
3. Reconcile the register with the actual drawing
Open the file from the controlled location and compare its drawing number, title, revision and purpose with the register. Check the relevant title block or revision panel, not only the file name. Confirm that the link does not open an older download or another document with a similar title.
Compare the issue evidence as well. A transmittal may cover several drawings, so check the particular item. Record discrepancies through the project's process and seek clarification from the responsible person. Avoid changing a register entry merely to make two inconsistent sources appear to agree.
4. Treat a new issue as a coordination task
When a new issue is received, check what it replaces and which activities or recipients may be affected. Use the approved process to update the register, retain the previous version and notify the relevant team. Keep the issue trail rather than deleting the history or silently overwriting a shared file.
Where printed sets are used, confirm who manages their replacement or marking. A paper drawing left in a work area can remain in use after the digital register changes. Do not assume that uploading a file has informed every recipient. Connect any effect on upcoming work with the two-week look-ahead plan.
5. Make an unresolved mismatch visible
Describe the discrepancy precisely: the drawing reference, the two sources that disagree, the affected area and the confirmation needed. Assign follow-up through the existing process and record who is responsible for responding. Keep the question visible until the authorised response has been recorded and communicated.
For a technical question, follow the construction RFI checklist. Use the change record checklist where a proposed change needs a controlled decision. A register update alone does not resolve either issue.
Hypothetical example: newer does not settle the question
Hypothetical example: a coordinator receives drawing M-204, revision C, marked “for coordination”. The register still links to revision B, with a different recorded purpose. A supervisor asks which version applies to the next work package.
The coordinator records the mismatch and its issue references, identifies the affected area and asks the responsible document controller or project lead to confirm the applicable issue and authorised use. They do not relabel revision C or tell the team to choose a version from the date alone. Once the authorised response is received, the controlled register and relevant recipients are updated through the agreed process.
A short check before the next work package
- Am I consulting the controlled source?
- Do the drawing identity, revision and purpose agree with the actual file?
- Can I trace the issue reference and any recorded clarification?
- Have affected recipients and printed sets been addressed through the approved process?
- Are unresolved questions assigned and visible?
Build the coordination skill
Practise using fictional documents or material you are authorised to access. Ask an experienced document controller to review whether another person could follow your references. Use the career assessment to consider how document coordination fits your wider development needs.
For structured learning in project information and communication, review the current WBS BSB50820 Diploma of Project Management or discuss your study needs with WBS. The diploma does not grant a construction licence or guarantee employment or promotion.
