The drawing register: every sheet, its current revision and the day it arrived
The mechanical trade says it used the current hotel duct layout. The coordinator finds a newer sheet in the office folder but cannot immediately show when it arrived or which field set received it. The register needs to connect document identity, status and distribution.
Keep one identifiable entry for each drawing sheet, with its received revision, issue purpose and current authorized status. Link the entry to its incoming issue and the field distribution record. A newer file in a folder is not enough to establish what was authorized for a particular task or what someone actually used.
Connect the sheet with its issue history
- Identify every sheet consistently. Record sheet number, title and discipline using the issuer's identifiers. Check the initial list against the actual received package, including missing or repeated sheets. Give supplemental references their own links rather than hiding an unrelated sketch inside a revision field.
- Record the received issue. Enter revision, issuer date, date received, issue purpose and incoming transmittal or other source record. Preserve each prior issue and its receipt history. If the revision designation is ambiguous or the package list does not match the files, ask the issuer; do not assume the highest letter or newest filename must be the correct field issue.
- Confirm status and distribute deliberately. Identify which issue is authorized for the relevant use under the project's process. Record pending questions and any linked instructions that remain applicable. Update affected recipients and field sets through the agreed publishing routine, linking what was sent, when and to whom. Sending a message and confirming usable field access are different steps.
- Compare the register with the field. Sample the active areas and device or printed sets at a cadence suited to the work, and check affected sets when an important issue changes. Record mismatches and their response. Keep the previous record intact so the current status does not erase the history needed to understand an earlier installation.
Make the register an index to evidence rather than a conclusion about liability. It can show a recorded receipt and distribution, while installation records, acknowledgment and the actual document used may still need review. Resolve that gap before writing that a trade must have known about a change simply because the coordinator entered it in a table.
Common mistakes
- Using newest filename as the entire current-status rule.
- Overwriting receipt history when a revision arrives.
- Treating recorded distribution as proof of the document actually used.
Checklist
Review one drawing entry
- Sheet identity and discipline.
- Revision, issuer date and received date.
- Issue purpose and incoming record.
- Authorized use and linked live instructions.
- Distribution and field-confirmation evidence.
Check your understanding
The register shows a newer issue was sent. Does that prove it was used?
