Civils drawing register builder

Record each issue, not just each drawing

A drawing number alone does not tell a site team which revision it received, why it was issued or where the controlled file is held. Use one row for each issue so a revision, recipient, purpose and source-system reference can be traced without deleting the earlier history.

Copy the document number, revision, issue date and status exactly as they appear in the project's controlled system. Status codes and suitability descriptions are project-defined. This builder deliberately supplies no generic code set because an invented code can look authoritative and lead to the wrong document being used.

Keep the index separate from the CDE

A common data environment (CDE) is more than a single piece of software. UK BIM Framework guidance, Part C, Edition 1 (2020) distinguishes the CDE workflow from the technology that supports it, and notes that the project CDE may include solutions used by more than one party. The Framework now lists this edition among its archived guidance. This page cannot connect to that workflow, check whether a drawing has been superseded or tell who has received a transmittal. Enter the project-system reference and location, then verify any working copy against the actual project record before use.

The index is useful for package coordination and close-out, but it is not an approval workflow. If a discrepancy affects work, record the question in the agreed project process and wait for the responsible person to resolve it. The groundworks handover pack guide explains how final as-built and quality records link back to the information that controlled construction.

Example: two issues of the same drawing

Suppose the project system holds C-104 revision 2 and a later revision 3. Keep two rows. In the revision 3 row, identify revision 2 as the previous issue and copy the new transmittal reference and project-defined issue purpose.

Ask the document controller to resolve any missing distribution acknowledgement in the controlled system. Recording revision 3 here does not prove that a subcontractor has received it or removed earlier working copies.

Keep revisions and actions visible

Do not replace a superseded revision in the working index without retaining the issue history. Link the replacement to the previous issue, record the project-system location and make any distribution or acknowledgement reference explicit. A person entering a status here is copying a record, not changing the formal document status.

For an open mismatch, record the drawing reference, what is missing, the responsible role and where the resolution will be stored. If the response alters the scope, use the contract's separate instruction and change-control route. The groundworks ITP builder can reference controlled drawings in activity checks, but it does not replace this issue index or the CDE.

Save and verify the working copy

Entries remain in this page only. Download or print the register, check it against the controlled source, then save it in the location your project requires. Do not place confidential project documents or unnecessary personal details into the browser form.