Document control becomes practical when an old revision is difficult to mistake for the current instruction.
A revised detail reaches the designer, the office and one subcontractor. A printed copy of the previous version remains in the site folder. Nobody is being careless on purpose; people are working from different information that each appears authoritative.
The risk is not solved by naming every file “final”. It needs a clear way to identify, issue and supersede project instructions.
Keep approval status visible
A document can be current for discussion without being approved for construction. Label its purpose and status as well as its revision. Make sure the team understands the difference between a proposal, an authorised change and the documents applicable to the work.
MBIE’s guidance on consent amendments emphasises accurately recording the work and the appropriate handling of variations. A project team’s internal filing system should support that process, not create an unofficial route around it.
Identify who controls the working set of documents and who receives a change. Include the subcontractors and suppliers affected by the detail, not only the main email distribution list. A revision to one interface may matter to more than one trade.
Retire the old working copy deliberately
Preserve older revisions as history, but separate them from the set used for current work. Printed copies need attention too. A controlled digital folder is less useful if the crew relies on yesterday’s paper drawing pinned in the site office.
For a significant change, confirm receipt and understanding with the affected team. Sending an attachment establishes that it was sent; it does not prove the installer recognised what changed.
Keep a concise change note. Identify the affected location and describe what is different without expecting everyone to compare two complete drawing sets line by line. Refer back to the proper revised documents rather than making the note itself an alternative specification.
If work has already been completed against an earlier instruction, raise it promptly with the appropriate people. Do not quietly alter records to make the history look simpler.
A good document system answers three questions quickly: what applies, who authorised it and what did it replace? When those answers are clear at the workface, fewer decisions have to be reconstructed later from inboxes and memory.