Construction handover discussions often mix document-control language with contract milestones. A short project glossary can reduce misunderstanding, provided it is clear about its limits. The working definitions below describe how a team might organise information; they do not replace definitions in the executed contract, approved plans or applicable requirements.
Useful working terms
- Deliverable: an identified item the team needs to provide, linked to the requirement that calls for it.
- Document register: an index describing documents, their identifiers, locations and review status.
- Transmittal: a recorded issue of documents to a recipient, with a reference that helps trace what was sent.
- Revision: an identified issue of a document; the revision label should follow the project’s agreed convention.
- Source record: the original supplied evidence retained so later summaries and indexes can be checked against it.
- Gap: information missing, unclear or not yet resolved against a stated requirement.
- Review comment: a reviewer’s question or requested change that needs a traceable response.
Terms that need extra care
“As-built”, “accepted”, “approved” and “practical completion” can carry specific contractual or technical meaning. Do not assign them simply because files have been received or renamed. A document organiser should record the status supplied by the authorised person and preserve the approval reference. Queensland Building and Construction Commission (QBCC) handover guidance provides Queensland context, but the project’s particular arrangements still need checking.
For operation and maintenance manuals, write the full term first and use “O&M” only after explaining it. An asset register lists identified assets; a manual explains supplied equipment or system information. Neither file name alone demonstrates that the other contains the necessary content.
Test the glossary with a real handover
In a hypothetical mechanical package, one person might call a drawing “final” while another means “latest received”. Add a status explanation: latest supplier issue, under review, with no approval reference yet located. That resolves the immediate ambiguity without inventing acceptance.
Give the glossary an owner, revision and source list. Ask the contract administrator and relevant technical reviewer to approve any project-specific definitions. Use the same terms in the register and meeting notes. When a client’s definition differs from the internal shorthand, keep the client’s meaning visible and explain the difference. The aim is shared understanding, not an unofficial rewrite of contractual responsibilities.



