Executive Assistant Offboarding Plan

Appoint one transition owner

An executive assistant departure touches operations, security, people processes, records, and executive relationships. Name one accountable transition owner who can coordinate those domains without absorbing their decisions. Confirm the approved timeline, confidentiality rules, receiving owners, and who may communicate the change. The reason for departure should remain with authorized people processes. The operating plan needs only the facts required to preserve work and remove access safely.

Inventory live commitments first

Start with work whose useful date arrives before or shortly after departure: meetings, travel, board materials, candidate interactions, customer follow-up, approvals, and promised communications. For each item, record the authoritative source, current state, next action, decision owner, due date, recipient, sensitivity, and acceptance condition. A list of folders or tasks is not a handoff if the successor cannot tell which commitments remain real.

Map recurring cycles

Document recurring leadership meetings, reporting windows, travel routines, inbox reviews, relationship touchpoints, and seasonal peaks. Show the trigger, preparation lead time, source inputs, approval point, distribution rule, and closure evidence. Remove obsolete routines rather than transferring them automatically. A calendar recurrence can survive long after its purpose has changed, so ask the accountable owner to confirm which cycles should continue.

Preserve business records at the source

Move company-owned instructions, decisions, contacts, and work evidence into approved company systems before access ends. Prefer controlled source links to copied attachments. Do not export an entire mailbox merely because classification is difficult. Identify records subject to legal, contractual, security, privacy, or retention requirements and let qualified owners decide their treatment. Personal notes and unsupported opinions should not become permanent company records.

Translate relationship knowledge neutrally

Useful continuity may include a stakeholder's approved routing channel, expected pre-read, accessibility need, or agreed response owner. Write observable instructions with a source and review date. Avoid personality labels, private speculation, or sensitive history that the successor does not need. Where appropriate, ask the stakeholder or relationship owner to confirm future routing. This protects trust while reducing dependence on one assistant's memory.

Reconcile delegated authority

List every workflow where the assistant could prepare, approve, execute, send, spend, or disclose under delegated rules. Name the executive or specialist who owns each authority and whether it transfers, pauses, or expires. System access is not proof of permission. Temporary coverage should receive only the authority required for its stated period, with an explicit stop condition and record of actions taken.

Build the access revocation schedule

Inventory company identities, delegated mailboxes, calendars, document groups, task tools, travel profiles, payment systems, devices, integrations, forwarding rules, scheduling links, shared credentials, and third-party accounts. Assign an approver and revocation owner. Sequence removal against required record preservation and live work. Do not leave access open just in case; document any bounded exception with purpose, expiry, monitoring, and approval.

Test the receiving owner

Have each receiving person perform a representative task before the final day: locate the current source, identify authority, complete the next action, and show acceptance evidence. Include one exception such as a missing input or priority conflict. Questions reveal gaps that a document review misses. The departing assistant can clarify operating facts, while the accountable executive resolves policy or priority questions that were never formally decided.

Handle inbox and calendar continuity carefully

Decide how new messages, invitations, and existing threads will route after departure. Use approved delegation, shared addresses, or notices rather than impersonation. Review future meetings for preparation and ownership, not only attendance. Remove forwarding and scheduling pages tied to the old identity after the replacement path works. Preserve necessary sent-item evidence without granting the successor unlimited access to historical private correspondence.

Close travel and expense exposure

Reconcile active itineraries, unused credits, traveler profiles, loyalty information, approvals, receipts, cards, and vendor contacts. Separate company and personal travel records. Confirm who can change or cancel bookings after the handoff and how after-hours disruption will escalate. Remove payment permissions promptly. An open itinerary may require continuity, but it does not justify keeping broad access to every past trip or financial record.

Communicate routing, not private detail

Tell affected internal and external contacts where future requests should go, when the change takes effect, and whom to contact for urgent matters. Use approved language and audiences. Avoid disclosing employment details or inviting contacts to keep using the departing person's account. Track high-consequence acknowledgements such as board, customer, travel, or candidate routing so silent delivery failure is visible.

Run final-day control checks

Confirm accepted work transfers, returned devices and records, disabled identities, removed groups, transferred integrations, closed forwarding, rotated shared secrets where necessary, and documented exceptions. Security should verify revocation independently of the checklist owner. Operations should confirm the successor can find time-sensitive work. Preserve timestamps and evidence in the authorized record, not in a public status note or informal chat thread.

Review the first two weeks after exit

Sample missed commitments, bounced messages, reopened items, access alerts, undocumented rules, and questions requiring the former assistant's memory. Assign each issue to a receiving owner and distinguish transition gaps from new work. Do not restore broad access to solve a missing instruction. Repair the source, routing, or authority record. Close the transition only when operations accepts continuity and security confirms no unresolved access exception.

Improve the role for the successor

Use the transition evidence to remove obsolete tasks, clarify impossible capacity assumptions, narrow unnecessary access, and update onboarding. Record patterns rather than personal blame. If important work depended on private memory, the process needs a source and reviewer. If one person held incompatible company and personal duties, reconsider the scope. A strong offboarding plan leaves a safer, more understandable role instead of reproducing every inherited workaround. Give the successor a dated role brief that distinguishes inherited commitments from newly approved priorities, then review it with the executive after the first complete operating cycle. That final review prevents temporary transition work from quietly becoming permanent scope.

Related resources

• Executive assistant support
• Executive support handoff template
• Executive support knowledge transfer