A handover register should answer five questions quickly: what is required, where does it apply, who owns it, what is its current status, and what happens next? Useful fields include a unique item number, deliverable title, discipline/system, location or asset, document ID, revision/date, source path, owner, status, reviewer, due date and action. Add a link to the controlling requirement so the team can check why the item is needed.

Keep status labels short and defined. For example: not started, requested, received, under review, returned for action, accepted by authorised reviewer, or not applicable with a reason. Do not use “compliant” as a substitute for an actual approval.

Test the register with a site user and a document controller. If they cannot find the original evidence in a few clicks, improve the naming or folder structure. Store the register in one controlled location and retain a dated export at formal submission milestones.