Revisions and document control

Each change after issue gets a new revision (e.g. letters for preliminary issues P1, P2… and numbers or letters for construction issues C1, C2…, or A, B, C — follow your standard). Changes are clouded with a revision triangle, and the title block's revision table records the revision, date and description. Remove old clouds when issuing the next revision.

Each issue states its purpose: For information, For comment, For approval, For tender, For construction. Under ISO 19650 national annexes, status codes (e.g. S1–S4 for shared, A-codes for authorised) describe suitability. Builders must build only from documents issued for construction.

A transmittal records what was issued, to whom, when, why and at which revision. The register summarises the current revision of every drawing. On many projects a common data environment manages both automatically.

A request for information is a contractor's formal question about the documents. Answer promptly and clearly, reference the drawings, and if the answer changes the design, issue revised documents — an RFI response shouldn't become a hidden design change. Track RFIs in a log.

Keep every issued document, unchanged, in a dated archive. Mark superseded prints on site as superseded. At completion, compile as-built documents from the contractor's marked-up records.