Executive assistant onboarding: a 30-60-90 day plan

Start with the real operating need

A useful 30-60-90 day plan transfers context and authority in stages. It does not hand over an executive mailbox on day one or postpone meaningful work for a month. Begin with the leader's outcomes, recurring workflows, decision preferences, stakeholders, sensitive information, predictable peaks, and known failure points. Assign an onboarding owner with time to answer questions and accept work. Keep the plan adaptable because actual volume and system quality will change the pace.

Set authority and boundaries

For each phase, name workflows to observe, practice, own, and improve. Connect access to a current workflow and remove blanket permissions from the default plan. Define acceptance, escalation, feedback, backup, and the evidence required before independence expands. Separate the assistant's learning gaps from undocumented leader preferences or broken inputs so early evaluation remains fair and useful.

Build the first control

During days one through thirty, teach the operating context and provision narrow access. Walk through calendar rules, inbox categories, meeting preparation, travel preferences, communication channels, and the commitment system. Pair each written rule with a normal case and an exception. Review early outputs before they leave the company.

Make ownership visible

Create a stakeholder and authority map. Record who may request time, who can change priorities, which messages may be sent without review, and where specialist approval is required. The new assistant should know the safest action when an approver is unavailable and the last useful moment to escalate.

Test the workflow

During days thirty-one through sixty, transfer complete low-risk workflows. Use a clear trigger, source of truth, service window, output, acceptance owner, and recovery step. Sample results and corrections weekly. Add access only after the workflow and its boundaries are understood.

Protect judgment and access

During days sixty-one through ninety, test more complex coordination and one controlled disruption. Let the assistant prepare options for a calendar collision, travel change, or incomplete meeting brief. Evaluate question quality, recordkeeping, judgment, and timely escalation, not whether they guessed an unwritten preference.

Create reliable follow-through

Finish with an ownership review and backup rehearsal. Confirm which routines are accepted, which need more coaching, which should return to another owner, and what improvements are approved. Have the named backup use the current handoff record to complete one bounded task.

See the approach in practice

A leadership-team assistant begins with read-only calendar context and owns internal scheduling after two observed cycles. In month two, they take leadership meeting preparation using a checklist and acceptance review. In month three, they coordinate a fictional travel disruption and hand one meeting brief to the backup. Access and independence expand because evidence supports them, not because a date arrived.

Review evidence and improve

Use weekly reviews early, then move to a sustainable operating cadence. Track accepted outputs, correction causes, questions raised before action, time waiting on leaders, access changes, service misses, and work that appeared outside the role. At day ninety, decide the next operating scope and development priorities. Do not label system ambiguity as an individual performance issue or leave temporary onboarding access in place without review.

Check authoritative guidance

Before adopting this approach, review the real workflow with the accountable executive, the person doing the work, and any qualified owner needed for employment, legal, security, privacy, finance, travel, or governance questions. Use CISA identity and access management guidance as a current starting reference, not as a substitute for advice based on the organization's facts and location. Record confirmed facts separately from assumptions, name the decision owner, and identify the safe action while information is missing.

Write the operating brief

Turn the decision into a one-page operating brief for executive assistant onboarding. Include the intended outcome, trigger, inputs, source of truth, authority, service window, exception path, completion evidence, backup, and review date. Connect it to executive assistant support and executive support onboarding checklist so the surrounding service and practical guidance stay easy to find. Walk through an ordinary case and an ambiguous case before applying the rule to consequential work.

Design for continuity

Protect continuity by keeping current records in company-approved systems and limiting access to the work a person performs now. Material changes, approvals, and exceptions should remain visible instead of being rewritten after the fact. A named backup needs to understand what is open, why it matters, which action is permitted, who owns the next decision, and when action becomes too late. Test that handoff with a bounded scenario before relying on it during an absence.

Rehearse the exception path

Run a tabletop review related to executive assistant onboarding. Remove one expected input, introduce a priority collision, and make the usual decision owner briefly unavailable. Ask the team to show how the request enters, where current status lives, which action can proceed, when escalation starts, and what evidence proves completion. Treat confusion as a system defect, assign the correction, and repeat the affected step with the named backup.

Choose the next operating cycle

HireExecutiveTeam helps founders and leadership teams define and staff practical executive support. Apply this guide to the real calendar, inbox, board, travel, meeting, project, and follow-through workload. Keep executive judgment with accountable leaders and specialist decisions with qualified owners. Begin with a bounded operating cycle, review accepted evidence, and preserve the option to revise or stop the arrangement when the facts do not support expansion.

Related resources

• executive assistant support
• executive support onboarding checklist
• executive assistant KPI scorecard