CEO Executive Assistant
Executive Time-Zone Handoffs: A Follow-the-Sun Protocol for Assistants solves a narrow but important executive-office problem: which items must transfer to the next coverage owner, when acknowledgment is required, and when the executive must be escalated.
For this workflow, capture item, executive local time, source time zone, current owner, next owner, decision needed, deadline, known facts, uncertainty, authority limit, next check, and acknowledgment.
Consider this case: The CEO lands in Singapore as the home-office assistant signs off. A flight change, a board document, two meeting moves, and a customer escalation all have deadlines before the original assistant returns.
Useful indicators include critical handoffs acknowledged, deadlines expressed with time zone, items transferred without duplicate action, authority questions escalated, missed next checks, and follow-up evidence recorded.
Choose work that can survive a handoff
Not every executive-office task benefits from continuous coverage. Research, document preparation, itinerary monitoring, and status collection can often move between regions when the record is clear. A sensitive negotiation, live personnel matter, or ambiguous message drafted in the executive’s voice may be safer with one owner, even if work pauses overnight.
Assess the cost of lost context. A handoff is worthwhile when the receiving assistant can act from the record without reconstructing private conversations. If the explanation requires a long call every day, the process has not become follow-the-sun; it has added another meeting. Keep judgment-heavy work with the person closest to the decision and transfer well-bounded actions.
Write a handoff that supports action
Lead with what changed during the sending shift and what must happen before the next overlap. For each live item, state the intended outcome, current fact, next action, owner, deadline in an explicit time zone, authority boundary, and escalation trigger. Link the source instead of pasting sensitive content into the handoff.
Distinguish observation from assumption. “Airline app shows cancellation at 18:40 Singapore time” is a fact with a source. “The executive will prefer the morning flight” is an assumption unless the preference is documented for that situation. The receiving assistant can verify the fact and prepare options without treating the assumption as approval.
Use absolute dates and local zones. “Tomorrow morning” is unsafe when one assistant writes in London and another reads in California. Include the executive’s current zone when travel is involved. Daylight-saving changes and half-hour offsets deserve special attention because familiar mental conversions fail.
Handle an overnight travel disruption
An executive flying from New York to Singapore learns during the U.S. evening that a regional connection has been canceled. The Asia-based assistant begins work before the U.S. team wakes. The handoff identifies the traveler, ticket locator in the approved travel system, protected customer meeting, acceptable arrival window, budget authority, and conditions that require executive choice.
The receiving assistant confirms the cancellation with the carrier, prepares two viable routes, checks visa and ground-transfer implications, and places only reversible holds allowed by policy. One option arrives before the meeting at higher cost; the other requires moving the meeting. The assistant does not cancel the original ticket or promise the customer a new time without authority.
The executive receives a short decision request at the agreed contact window. Once the choice is approved, the Asia assistant executes it, updates the itinerary source of truth, and records confirmation. The next U.S. handoff reports the completed result, remaining monitoring, and any refund owner. Nobody duplicates the booking because acceptance was visible.
Define acknowledgment and escalation
The receiver should acknowledge ownership, not merely receipt. A useful response says which items were accepted, which need clarification, and when the next update will arrive. If an item cannot be accepted because of capacity or authority, return it before the sending assistant signs off. Silence creates two dangerous assumptions: the sender thinks coverage exists, while the receiver may think no action was authorized.
Set consequence-based escalation. Safety, stranded travel, account compromise, and a near-term external commitment may justify waking a named leader. A routine draft question can wait for overlap. Record the trusted channel and fallback owner before coverage begins; an escalation tree invented at 3 a.m. tends to expose sensitive details or reach the wrong person.
Learn from failures without adding ceremony
Review missed acknowledgments, double actions, late escalations, and items that repeatedly need oral explanation. A duplicate booking may show that acceptance was not visible. A missed customer update may show that the deadline lacked a zone. An unnecessary wake-up may show that the consequence threshold was vague.
Fix the specific weakness. Add a source link, clarify a boundary, change the overlap time, or keep the task with one owner. Do not answer every error by adding fields to every handoff. The protocol succeeds when work moves safely with less synchronous coordination, not when the template becomes longer.
Maintain a short directory for coverage roles rather than individual habits. It should show the active shift, backup, trusted escalation channel, and the systems each role may use. Update it when travel or leave changes coverage. The directory should not list private phone numbers more broadly than necessary. During a drill, ask a backup to accept and close one ordinary item; this tests access and authority before a real overnight disruption exposes the gap.
Design around the last safe moment to act
A handoff deadline should come from the work, not from the end of someone’s shift. If a traveler must be rebooked before an airline cutoff, the outgoing region needs to send the case early enough for the receiving region to read it, ask one question, and act. Calculate that last safe moment and work backward. A midnight transfer that leaves five minutes before the cutoff is technically on time and operationally useless.
Use a single authoritative record for changes made during overlap. Chat can alert the next owner, but the handoff record should state the current option, evidence, authority limit, and next irreversible action. If both regions act at once, one person must be designated to commit while the other observes. For work that cannot safely cross regions, such as a sensitive employee conversation requiring local context, say so explicitly and retain ownership until the qualified person returns. A global team is not improved by passing every task around the clock.
Respect regional authority and local conditions
The receiving team may see constraints the sender cannot, including local holidays, vendor hours, language, or regulatory limits. Give it authority to pause an unsafe instruction and state what evidence is needed. A handoff is not an order to execute blindly. When local conditions change the plan, the receiving owner records the change and alerts the accountable leader before an irreversible step. This keeps round-the-clock coverage from flattening differences that matter.