Client-facing technical documents need an issue trail that explains which information was sent, to whom and for what purpose. A filename containing “final” does not provide that trail, particularly when the same document passes through several review cycles.
Use stable identification
Keep a document number or other unique identifier consistent across revisions. Record its title, responsible author, revision, issue date, intended recipient and purpose of issue. Use the client's required numbering or revision convention where one exists; do not impose an incompatible scheme merely to make a folder look tidy.
Distinguish draft, review and authorised issue states in the document and register. The person preparing a formatted copy should not assign an approval status beyond the authority they hold. If the status is unclear, record a question for the document owner.
Record each formal issue
At issue, capture the exact file or controlled-system version, the transmittal or message reference and the recipient. Preserve the review response and connect the next revision to the comments or change request that prompted it. Keep superseded issues accessible to authorised users without presenting them as the current instruction.
If a document is withdrawn, show that state and tell affected recipients through the agreed route. Removing it from one folder does not establish that everyone who received it knows it has changed.
Worked example
A hypothetical mechanical subcontractor submits drawing M-014 revision B for review. The reviewer returns comments. Revision C is prepared and checked by the authorised technical team, then issued through a new transmittal that references the earlier response.
The register retains both issues. Its current-view link points to revision C, while revision B remains in the issue history. A downstream user can see that the client response applies to a particular revision rather than assuming it covers every later file with the same title.
Check the assembled pack
Before a handover or submission, compare the register revision with the revision displayed inside each file. Look for PDFs exported from an old draft, missing attachments and inconsistent document identifiers. Route any technical content discrepancy back to the responsible author or reviewer.
These are practical control recommendations. Client requirements, contract instructions and authorised approvals remain the source for issue status and acceptance. A documentation service can organise the trail and identify mismatches; it cannot substitute a technical signature or certify the contents by renaming a file.



