Philippines staffing guide · Published
On this page
Build a client handover checklist for a new Philippines assistant
A handover checklist that names the client's visible work, the systems behind it, the decision rules, and the open loops, so a new assistant starts with evidence instead of guesswork.
A new assistant rarely fails because the task list was too short. The failure usually comes from context that never left the departing person's head: which client prefers a call over email, which invoice needs a second approval, and which shared drive holds the current version. A handover checklist turns that context into named fields that someone can verify. Build it before the first day so the new assistant can test it against real work.
Treat the checklist as a working document, not a compliance form. It should point to systems, examples, and named owners rather than repeat policy language. The client should be able to skim it and correct anything that sounds wrong. Review it after the first month, when the new assistant knows which sections were useful and which were missing.
Start with the work the client actually sees
List the deliverables the client receives each week before listing the internal steps that produce them. A client sees a reconciled report, a confirmed meeting, or a answered support thread, not the five tabs used to build it. Write each deliverable with its due day, format, and approval path. That order keeps the checklist anchored to the result the client is paying for.
For each deliverable, name one recent example the new assistant can open. The example should include the working file and the final version, so the difference between draft and delivery is visible. Add a short note on what the client praised or corrected last time. Examples remove more ambiguity than another paragraph of instructions.
List the systems and access each task needs
Map every tool the work touches, including the ones used only once a month. Record the account owner, the role the assistant needs, and the approval step for access. Mark tools that require multi-factor authentication or a client-side invitation, because those often delay the first week. A task that cannot be completed without a missing login is not ready to hand over.
Separate read access from write access in the checklist. Many handovers fail because a new assistant can see a folder but cannot upload the finished file. Note where the assistant may edit directly and where a draft must be reviewed first. Review the access list with the client before day one and remove anything the role does not need.
Capture the client's decision rules
Write down the choices the assistant is allowed to make without asking. Include the threshold for a refund, the calendar rule for double bookings, and the tone the client uses with late-paying customers. Put each rule beside the task it governs so the assistant does not have to memorize a separate policy document. A rule without a task is easy to ignore.
Also record the decisions that must always escalate, even when the answer seems obvious. Name the person who decides and the channel to use. State what the assistant should do while waiting, such as holding the request or sending a short acknowledgment. Clear escalation rules protect both the client relationship and the assistant's confidence.
Record the open loops before day one
Every handover starts with work already in motion. List the requests waiting on the client, the invoices under dispute, and the meetings that still need a confirmed time. For each one, record the last action, the next action, and the date it is due. The new assistant should be able to continue the loop without reconstructing its history.
Mark which open loops are sensitive enough to mention in the first client update. A delayed filing or a missed callback needs a calm sentence in the handover note, not a surprise later. Give the new assistant the exact wording the client has already seen, so the story stays consistent. Close each loop in the checklist when it is resolved.
Rehearse the first week with a dry run
Ask the new assistant to complete one real task end to end before the handover is signed off. Choose something with a clear finish, such as preparing the weekly report or scheduling a recurring meeting. Watch where the checklist sends them and note every question they have to ask. Those questions are the gaps the document did not cover.
Update the checklist the same day as the dry run. Add the missing file path, the client contact, or the approval step that caused the pause. Keep a short log of what changed and why. A checklist that has survived one real task is more trustworthy than a longer one that has never been used.
Review the checklist after thirty days
At the end of the first month, ask the assistant which sections they used and which they ignored. Remove fields that no longer match the work and add the exceptions that appeared. Compare the result with the client's feedback and the first quality review. The checklist should get shorter and more precise over time.
Give the updated version to the client and ask for one correction. A client who edits the handover document is more likely to trust the process behind it. Store the current version in the shared workspace and retire older copies. Future handovers can start from this reviewed version instead of a blank page.
Questions and operating boundary
Who should own the handover checklist?
The departing assistant or the account lead writes the first draft, the client corrects it, and the new assistant tests it. One named person should own the final version and its review date.
How long should the checklist be?
Long enough to name the deliverables, systems, rules, and open loops, but short enough to read in one sitting. Link to examples and policies instead of copying them into the document.
Should the client see the internal steps?
Only where the client's decision or access is required. Keep internal working notes in a separate section so the client review stays focused on outcomes and rules.
Source
sba.gov provides authoritative background and does not endorse this service.