The newest drawing in a folder may still be awaiting review. An older drawing on a subcontractor’s tablet may have been issued for the work, but could now be affected by a proposed change.
Finding the right drawing therefore involves more than sorting files by date.
For a busy fit-out team, document control needs to answer a practical question: which information is authorised for this task, and how do we know the people doing the work have received it?
Separate revision from permission to use
A revision identifies an update to a document. Its status helps explain how that information may be used under the project’s agreed procedures.
The UK BIM Framework’s September 2020 guidance treats revision and permitted use as distinct parts of information management. For the project team, the practical lesson is to check both.
Consider a reflected ceiling plan showing revised lighting positions. A new revision is circulated for comment. If someone assumes that “latest” means ready for installation, they may act before the design review is complete.
The answer is not simply to use the previous drawing. Where a known change could affect planned work, the responsible project and design leads need to confirm the correct information and next step.
Make the drawing register useful at the point of work
The register should help a colleague identify the document without relying on a familiar filename or a particular person’s memory.
For each drawing, make the following easy to find:
Drawing number and a clear description of the area or package.
Revision and the project’s recorded status or permitted use.
Issuing organisation and issue date.
Relevant approval record, including any conditions.
Link to the controlled file and the issue record.
Use the naming, status and revision conventions agreed for the project. Where the project has formal information-management requirements, the team needs to follow those rather than introduce an informal alternative.
A short explanation of unfamiliar codes helps subcontractors and new team members use the register correctly. Test it with someone who did not create it: can they find the information for a particular room and tell what it can be used for?
Keep the issue record attached to the information
Uploading a drawing is only part of issuing it. The team also needs a record of what was sent, to whom, when and for what purpose.
That record might be a transmittal or an issue function in the document system. The important point is that it identifies the exact drawing and revision. A message saying “updated drawings attached” leaves too much room for uncertainty.
Where several documents form a package, identify the set. A changed ceiling plan may need checking alongside the lighting layout or another related drawing. The design team should identify the relevant dependencies.
A recorded receipt confirms that information reached someone. It does not prove that the recipient reviewed it or resolved its effect on the work. Where action is required, give that action a separate owner.
Manage the copies that leave the system
Printed drawings, downloaded files and email attachments are part of site reality. Their use needs a workable process.
Agree how the team checks an offline copy against the controlled record and how replacement issues reach the people holding those copies. Make it easy to identify the drawing number and revision on the sheet or file.
Preserve superseded issues in the project history while making them clearly distinguishable from the active working set. Deleting the old record can remove evidence of what was issued at a particular time.
Avoid relying on a filename such as “final” or “final updated”. It cannot tell a new colleague whether the document was reviewed, issued or later replaced.
Resolve conflicts where they arise
If a drawing, schedule and approval record disagree, make the discrepancy visible and refer it to the appropriate person. Do not let a convenient filename or timestamp settle the question.
A useful discrepancy record states the conflicting references, the work potentially affected and who is checking it. Record the resolution against the relevant issue so the same question does not have to be answered again.
This is particularly useful when a design change arrives close to installation. The team needs to establish which information governs the affected work and communicate that clearly to those involved.
Use an AI colleague for the repetitive comparisons
A focused pilot could compare a drawing register with recorded file references, highlight missing revisions or identify inconsistent issue information. It could prepare a list for the document controller or project manager to review.
That would depend on the quality and accessibility of the source material. Scanned or incomplete title blocks may need a person to check them. The agent should flag unreadable information instead of guessing.
It should also leave technical interpretation and permission to use a drawing with the authorised team. Recognising a revision number is a different task from judging whether a design is suitable.
Build Agents is developing this kind of supporting role alongside existing document systems. If confirming the right issue takes too much searching, bring one drawing package to a conversation with us. We can explore whether a focused paid pilot would make the checking easier.
