Map the overlap window before the start date
Map the hours when the assistant and the manager are both online. Treat that overlap as the most expensive part of the schedule and reserve it for decisions, not routine updates. Put recurring reviews, exceptions, and client calls inside the window. Move status reporting and documentation outside it so the shared hours are used for judgment.
Check the overlap against the assistant's local working hours and any contractual limits. A schedule that looks efficient in one time zone may require an unreasonable start or end in another. Write the agreed hours in the onboarding plan and confirm that the times are correct across daylight-saving changes. A recurring meeting that shifts by an hour twice a year can quietly break a handoff.
Put handoffs at the end of a shift
Place the main handoff at the end of the assistant's shift, not in the middle of the day. The outgoing person should summarize what is complete, what is waiting, and what needs a decision. Include the next action and the owner for each open item. A handoff written while work is still in progress is usually incomplete.
Give the incoming person a short window to read the handoff before the queue opens. Ask them to acknowledge the items that need action rather than only opening the note. If an item is unclear, the outgoing person should clarify it before going offline. This small step prevents a question from waiting a full day for an answer.
Record status in a shared queue
Keep the handoff in a shared queue that both people can edit. Use a status that describes the next action rather than a generic in progress label. Attach the source document or a link to the system of record for each item. The queue becomes the shared memory of the role and reduces dependence on chat history.
Do not let the queue become a second inbox for every request in the business. Limit it to the work the role owns and the items waiting on a named decision. Archive completed items on a fixed cadence so the list stays readable. A queue that contains everything quickly stops being trusted as a handoff tool.
Limit after-hours escalation to named triggers
Define the events that justify contacting someone outside the overlap window. Use specific triggers such as a client outage, a payment failure, a legal deadline, or an unauthorized access attempt. Give the assistant a clear channel and a fallback contact for each trigger. Routine questions should wait for the next overlap instead of becoming an evening message.
Review every after-hours escalation after the first month. If the same kind of issue appears repeatedly, change the process rather than asking the assistant to keep calling. If no escalation occurred, check that the trigger list is realistic and that the assistant knows how to use it. A policy that is never tested may fail when a real incident arrives.
Review missed handoffs every week
Review missed or late handoffs at the end of each week. Count the items that had no owner, the items that were returned, and the questions that waited more than one shift. Ask whether the cause was a scheduling gap, an unclear instruction, or a missing input. Record the fix and assign a date to check it.
Share the pattern with the manager and the assistant without turning it into a personal score. The purpose is to improve the schedule and the written process, not to rank people by their willingness to work late. If the overlap is too short for the volume of decisions, adjust the scope or the staffing. A handoff plan should make the work predictable, not heroic.
Keep the plan visible after onboarding
Keep the time-zone plan in the same workspace as the task instructions. Update it when the client's hours, the role's scope, or the team's staffing changes. Add the plan to the first-month review so it is tested with real work. An onboarding document that is never revisited becomes a description of an old arrangement.
Give new team members a short tour of the handoff queue and the escalation triggers. Ask them to walk through one real handoff before they own the shift. Confirm that they know who reads the note and when. The plan is working when the incoming person can act without waiting for the outgoing person to wake up.
Protect the assistant's local working hours
Write the assistant's local start and end times into the plan and treat them as a real boundary. Do not schedule a recurring call outside those hours unless the arrangement and the pay reflect it. Check the impact of daylight-saving changes on both sides of the handoff. A plan that only works because someone silently answers messages at night is not sustainable.
Give the assistant a way to flag a schedule conflict before it becomes a missed handoff. Review the flag at the next overlap and adjust the queue or the coverage. If the client expects coverage beyond the agreed hours, budget and staff it explicitly. Protect the local hours first, then design the handoff around what remains.
Put the handoff rules in the client agreement
Write the handoff window, the response expectations, and the escalation triggers into the client agreement. A verbal understanding disappears when the client's team changes. State which decisions wait for the overlap and which can be made by the assistant. This protects the assistant from being blamed for a delay the arrangement created.
Review the agreement when the client adds a service or changes the volume. A new urgent queue can overwhelm an overlap that was sized for routine work. Update the schedule and the escalation list together. The client should see the handoff as part of the service design, not as an internal detail.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Department of Labor — Hours Worked Under the FLSA general guidance on what counts as compensable hours worked under the Fair Labor Standards Act.
Related reading
A remote VA's first-week workload ramp
A first-week workload plan that moves a remote virtual assistant from supervised practice to a capped queue without hiding review work.
A shadowing schedule that protects the manager's calendar
A short shadowing plan that gives a new virtual assistant real observation time without consuming the manager's entire week.
Write a task documentation standard before the VA starts
A documentation standard that gives a virtual assistant the inputs, decisions, examples, and review rules needed to finish work without guessing.
