Executive assistant first-week readiness checklist

Start with the decision

What is the smallest safe set of workflows a new assistant can complete and have accepted during the first week? Start there rather than with a preferred title, provider, or deadline. Map the actual calendar, inbox, meeting, travel, board, project, and follow-through work that consumes leadership attention. Record the outcome, current owner, frequency, useful deadline, sensitive data, decision dependency, and evidence of completion. Include a normal week and a peak period so the scope survives real demand.

Set the authority boundary

Readiness is not measured by the number of systems opened on day one. It comes from clear outcomes, narrow access, verified delegation, realistic practice, named reviewers, and a reliable path for missing context or suspicious requests. Write the boundary in plain language: work support may complete under standing authority, work it may prepare for review, and work that must remain with an accountable executive or qualified specialist. Urgency, seniority, or an existing relationship does not create permission.

Gather demand evidence

Choose two recurring workflows, document their triggers and acceptance criteria, provision least-privilege access, and rehearse a normal request, a priority collision, an unavailable executive, and a possible impersonation attempt. Separate confirmed facts from estimates and preferences. Note where delay is merely inconvenient and where it creates a customer, governance, financial, people, security, or leadership consequence. Preserve the source and observation period so the team can revisit assumptions.

Define accepted outcomes

Turn the evidence into five to seven outcomes. For each outcome, name its trigger, required inputs, source of truth, accepted output, accountable reviewer, service window, exception path, and closure evidence. Describe a representative cycle and known peaks. Remove generic requirements that do not connect to an outcome.

Set priority rules

Define priority before work begins. State who resolves collisions between leaders, how urgency is justified, the last useful decision time, and what can wait. Maintain one queue for open work and one authoritative status record. Email and chat can carry alerts, but neither should become a hidden competing task system.

Control access

Design access from workflows, not status. Use separate identity, approved delegation, multifactor authentication, least privilege, secure source links, and scheduled review. Never place credentials or unnecessary personal, board, people, customer, or financial details in coordination records. Record the approver and revocation owner for every permission.

Evaluate consistently

Use a structured selection or vendor review. Give finalists the same job-related scenarios, evidence requests, anchored criteria, and explanation of stages. Use fictional or sanitized work samples, offer reasonable accommodations, and avoid asking for unpaid production work or another organization's confidential material. Have the appropriate owner review employment and contracting requirements.

See the workflow in practice

A new assistant begins with calendar intake and meeting preparation rather than unrestricted inbox sending. The executive reviews two completed cycles, confirms the escalation record, and only then approves the next permission level. This scenario is not a universal prescription. It demonstrates why the decision should follow observed work, explicit authority, and accepted evidence rather than title prestige, speed, or a promise that one person will handle everything.

Verify the evidence

Verify claims consistently and with appropriate authorization. Ask about the capabilities evaluated earlier, including prioritization, discretion, source checking, communication, recovery, and closure. Document what was observed, what was inferred, and what remains uncertain. Do not let an informal back channel replace a fair review.

Use authoritative guidance

Use CISA phishing guidance as a current starting point for the relevant operating context. Guidance can change and cannot resolve company-specific legal, employment, governance, tax, privacy, accessibility, travel, or security questions. Route those questions to the qualified owner and record the approved rule rather than relying on memory.

Write the operating brief

Before launch, write a one-page operating brief. Include outcomes, scope, exclusions, decision rights, service windows, systems, access, acceptance criteria, escalation, backup, review cadence, and exit obligations. Walk through a normal request, a missing-input case, a priority collision, an unavailable decision owner, and a suspicious request.

Review early performance

Review the first two operating cycles closely. Sample accepted work, corrections, clarification loops, waiting time, priority overrides, after-hours exceptions, access changes, reopened decisions, and requests arriving outside scope. Activity counts are not enough; a busy support function can still create rework and hide ownership.

Pilot before expansion

Use a baseline and a small pilot before promising a permanent model. Record current cycle time, preventable corrections, unanswered requests, decision waiting, missed preparation, and work reopened after apparent completion. Run the proposed workflow for a defined period, then compare the same measures and inspect a sample of actual outputs. Ask the supported leaders, the support professional, and downstream owners where the process moved friction rather than removing it. Keep qualitative observations alongside counts because faster handling can conceal weaker decisions or poor records. Approve expansion only when the accountable owner accepts both the work and its evidence; otherwise revise the scope, authority, capacity, or service window and repeat the bounded test.

Plan continuity

Protect continuity from the first day. Maintain current instructions in a company-approved location, keep an open-work handoff, and name a backup with appropriately limited access. Test one bounded handoff. At transition, return records, remove forwarding and integrations, revoke access, confirm open decisions, and preserve required evidence.

Choose the next step

Connect this decision to executive assistant support, then use executive assistant access onboarding checklist and executive assistant onboarding plan for adjacent workflows. HireExecutiveTeam can help a founder or leadership team turn observed work into a practical executive support scope. Begin with a bounded cycle, retain consequential judgment with accountable leaders, and expand only when accepted evidence supports the change.

Related resources

• executive assistant support
• executive assistant access onboarding checklist
• executive assistant onboarding plan