Philippines staffing guide
Build a Handover Pack Before an Assistant Is Out
Leave, illness, or turnover should not strand the queue. A handover pack names the work, the access, and the next action.
Published · 9 minute read
On this page
A handover pack is the difference between a planned absence and a crisis. It tells the backup where the work lives, what is due, what is waiting, and who can approve an exception. It should be written before the absence, not during it.
The operating problem
A handover pack is the difference between a planned absence and a crisis. It tells the backup where the work lives, what is due, what is waiting, and who can approve an exception. It should be written before the absence, not during it.
Start with the current queue. List the open items, the owner, the next action, the due date, and the source. Include the items that are waiting on someone else. A backup who only sees the completed work will miss the commitments that are still open.
List the access. Name the systems, the accounts, the shared mailboxes, and the files the backup needs. Confirm that the access is active before the primary leaves. A handover that requires a two-week approval is not a handover.
Include the recurring tasks and the calendar. The backup should know what happens on Monday, what happens at month end, and what must be reviewed before it goes out. Link to the procedures, but also write a short note about the parts that are not in the procedure.
What to control
Name the decision owners and the stop rules. The backup should not approve a refund, change a price, or send a sensitive message just because the primary is away. The handover pack should repeat the authority line and the escalation path.
Record the customer or client commitments. If the assistant promised an update on Thursday, the backup needs to know. Include the exact wording and the channel. A missed promise during an absence damages trust more than a delayed internal task.
Test the pack with the backup. Ask them to complete one routine item and one exception using only the pack. Note where they get stuck and update the pack. A handover pack that has never been used is a draft.
After the absence, review what worked and what was missing. Update the pack and the access list. If the same gap appears twice, fix the underlying process rather than relying on a hero backup.Keep the pack in a shared location with a clear owner and a review date. A pack that lives on the primary's laptop is not available during an absence. Link it from the team calendar and the role brief.
A workable routine
Write a short note for each open item. The backup needs to know what happened, what is next, and what not to do. A list of ticket numbers is not enough. Include the customer's time zone and the promised update.
Review the pack after a system change, a policy change, or a new client. The access list and the procedures may be out of date. A quarterly review is a minimum; an event-driven review is better.
After the absence, ask the backup what they would change. The person who used the pack sees the gaps that the primary cannot see. Update the pack and thank the backup. A handover culture depends on making the next absence easier.
Keep the pack current during normal work, not only before a holiday. When a task changes, update the pack the same week. A last-minute scramble produces a pack that lists everything and explains nothing. The best time to write a handover note is when the work is fresh.
Review and evidence
Include a short section on relationships. The backup should know who prefers a call, who needs a written summary, and who is sensitive about timing. These details are hard to reconstruct from a ticket. Keep them factual and respectful, and avoid personal judgments.