How to use this guide
This is general operational guidance for New Zealand SMEs. Adapt it to the business and the decisions involved. It is not a complete compliance checklist, legal opinion or a substitute for advice about a particular situation. Examples are illustrative and do not describe client engagements or promised outcomes.
How do you decide what to transfer?
Define the role being handed over and the period the handover needs to cover. Separate recurring work from temporary responsibilities and unfinished projects. For each priority, explain the next action, its reason, the source record and who can authorise a change. A list of contacts is less useful than knowing why and when those people should be involved.
Keep personal employee details out of a general team handover. Identify the authorised system and relevant access owner instead of copying a full personnel file into a convenient shared folder. Explain uncertainties and open questions in neutral language. The incoming manager should be able to distinguish a confirmed fact, a working assumption and an issue awaiting specialist input.
How do you check the handover worked?
Walk through one realistic task together: a customer issue, a scheduled review or a work allocation decision. Ask the incoming manager to locate the source, describe the next step and explain an escalation route. This exposes missing context more reliably than a signature acknowledging receipt of a large document. Record what still needs clarification and who will provide it.
- Prepare a short priority summary and link to controlled source records rather than duplicate every document.
- Hold a discussion about decisions, exceptions and unresolved risks, including who takes responsibility during the transition.
- Confirm acceptance of each responsibility and arrange an early review of gaps discovered in practice.
A working structure
Manager handover outline
- Role, transition dates and temporary cover
- Top priorities and next decision due
- Recurring responsibilities and key dependencies
- Source records and access owner
- Unresolved questions and escalation contacts
- Receiving owner, acceptance and follow-up date
Illustrative example
Illustrative example: a team leader is moving to another site. Instead of forwarding a full email inbox, the outgoing leader prepares a priority register with links to approved project records. The receiving leader rehearses the next scheduling decision and identifies a missing supplier contact. That gap is resolved before the transition. Sensitive employee matters are handled through a separate authorised channel rather than copied into the operational register.
Questions about this guide
Is a handover only necessary when someone leaves?
No. A short handover can support leave cover, project transitions, changes in decision authority and a move between teams. Adjust the detail to the duration and consequence of the responsibility being transferred.
What if the outgoing manager is unavailable?
Reconstruct a provisional register from authorised records, label what is unconfirmed and assign an owner to each gap. Do not present assumptions as an agreed historical account.
Official sources and further guidance
These primary sources provide additional context. The operational suggestions and working outlines above are YJ Consulting’s general guidance; the links do not establish that an authority has endorsed this guide.
When YJ Consulting can help
YJ Consulting can help an Auckland or New Zealand SME map the current practice, organise the relevant records and turn the findings into an agreed improvement plan. The engagement starts by confirming the question, responsible adviser, information available and useful outputs. Legal, payroll, financial or other specialist questions should be identified and assigned separately.
Explore the relevant service · Service-scope information · Book an initial conversation