Exception and Handover Register
Track vehicle deviations, concessions, open actions and document handover against a named decision, owner, status and approved revision.
Review contacts: Alicia June and Mia Fu.
| Exception ID | Requirement / document | Description | Impact | Owner | Due date | Disposition | Evidence / closure |
|---|---|---|---|---|---|---|---|
How to use this tool
Do not hide unresolved exceptions inside general meeting notes or delivery photographs.
- Assign every exception a stable identifier and owner.
- Record evidence, due date and approval or rejection.
- Link closed items to the retained handover record.
Keep a record of your inputs
Add the project ID, responsible person, date and revision before using the worksheet to compare suppliers or make a technical decision. Record where each input came from. Leave unknown values open for confirmation; do not fill a gap with an assumed catalogue figure.
The result helps with calculation or recordkeeping only. A competent reviewer must check the units and operating conditions against the selected equipment documents. That review must also cover destination requirements, interactions between systems and the evidence needed at acceptance.
Assumptions and limits
- Acceptance of an exception is a project authority decision.
- The register does not create a compliance conclusion.