Philippines staffing guide · Published

On this page

Write a client handoff checklist for a new overseas assistant

A practical checklist for handing client work to a new overseas assistant, covering recurring requests, system access, decision rules, shadow tasks, and the first-month review.

Write a client handoff checklist for a new overseas assistant

A new overseas assistant inherits more than a task list. The handoff is where the owner explains which client requests repeat, which systems hold the record, and which decisions need approval before work moves. A written checklist turns that explanation into something the assistant can review alone on the first morning instead of interrupting the owner for every small question. The document should also say who answers questions it does not cover.

Most failed handoffs are not caused by skill gaps. They happen because the owner describes the job while the assistant is still learning names, and the details that matter later never reach a document. The checklist should be short enough to finish in one sitting and specific enough to test during the first week. Build it from today's real requests rather than an ideal process the team hopes to adopt.

Start from the client's recurring requests

Pull the last thirty days of requests from the mailbox, the project board, or the shared drive. Group them into a short list of recurring jobs, such as scheduling, document collection, invoice follow-up, and status updates. For each group, write one sentence that describes what finished work looks like to the client. This gives the new assistant a test for closing a task rather than a vague instruction to keep things moving.

Include the exception that appears every week, because exceptions consume more judgment than routine work. If a client sometimes sends a document in a different format, say how the assistant should handle it and who confirms the decision. Note the requests that should never be handled alone, such as changes to bank details or contract terms. The checklist should make those boundaries obvious before the first live request arrives.

Name the systems and access levels

List each system the role touches, the exact permission level, and the person who grants it. Separate read access from edit access, and separate drafting from sending. A new assistant should know which folder is safe to reorganize and which one is read-only evidence. Record where the login lives and which recovery route is approved, without writing passwords into the checklist itself.

Test every login during the handoff rather than on the first busy day. Confirm that the assistant can open the mailbox, the calendar, the shared drive, and the project board, and note any tool that requires a second approval. If a client portal needs its own invitation, start that request early. Access problems discovered at nine in the morning become client delays by noon.

Document the decision rules

Write the rules that decide when work continues and when it stops. For example, state which refund requests the assistant may acknowledge but not approve, and which calendar changes need the client's written confirmation. Use real examples from the past month, including one case that was handled well and one that required correction. Concrete examples teach judgment faster than a list of principles.

Keep the rules in one place and give each rule a stable name so the team can refer to it in messages. When a new situation appears, add it to the same document instead of leaving the answer in a chat thread. Review the rules at the end of the first month and remove anything that no longer matches the work. A short, current rule set is more useful than a long archive nobody reads.

Build a first-week shadow list

Choose five tasks the assistant will observe before doing them alone, and five tasks that can be practiced immediately. Observing a task means reading the request, watching the owner decide, and writing down the reasoning afterward. Practice should happen on real work with a review step, not on invented examples. The mix gives the assistant context without turning the first week into passive shadowing.

At the end of each day, ask the assistant to write one thing that was clearer than expected and one thing that still needs an answer. Those notes reveal gaps in the checklist while the memory of the handoff is fresh. Fix the document the same week, because a gap that stays open becomes a habit. The owner should also note where they interrupted the assistant unnecessarily.

Set the review and escalation path

Name the person the assistant contacts when a request falls outside the checklist. Give a primary and a backup, along with the hours when each is available. State what information the assistant should include in an escalation, such as the client, the request, the step completed, and the decision needed. A clear escalation note lets the owner respond once instead of asking three follow-up questions.

Schedule a short review at the end of week one, week two, and week four. Use the review to test the checklist against actual work, confirm access is still correct, and agree on the next task to hand over. Close the handoff when the assistant can complete the core routine without prompting. Keep the checklist as a living reference and update it whenever the client's pattern changes.

Test the checklist with one real request before the first solo shift. Ask the assistant to walk through the document, name the system they would open, and state the decision rule they would apply, then note every pause as a gap. If the assistant needs the owner to interpret a step, rewrite that step instead of explaining it again. A checklist that only works when the owner is available has not been handed off, and the first busy day will expose that weakness quickly.

Questions and operating boundary

How long should the handoff checklist be?

Long enough to cover the recurring work, access, decision rules, and escalation path, but short enough that the owner can walk through it in one session and the assistant can review it alone.

Should the checklist include client names and account numbers?

Use client references and role names where possible, and keep sensitive identifiers in the approved system rather than in a document that may be shared more widely.

What if the owner has no written process yet?

Build the first version from the last month of real requests, then test it during the first week and correct the gaps while the examples are still fresh.

Source

sba.gov provides authoritative background and does not endorse this service.

Explore services · Browse guides · Plan a controlled lane

Philippines staffing

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. Those details help shape a practical Philippines staffing request.

Contact Us