Executive Assistant Onboarding: The 30-Day Plan That Sets the Role Up Right

Executive Assistant Onboarding: A 30‑Day Plan That Works

This U.S.‑focused, practical 30‑day onboarding blueprint gets a new executive assistant productive on calendar, inbox, and recurring operations while keeping executive time investment predictable. Copy the day‑by‑day Google Sheets/CSV template, paste the one‑page playbook, and use the acceptance tests and KPI tracker to confirm progress by Day 30.

TL;DR: One‑page 30‑day checklist (downloadable assets below)

Why a structured 30‑day onboarding matters (and the risks of skipping it)

Unstructured onboarding frequently causes missed meetings, inbox confusion, privacy slips, and repeated corrections that cost more executive time than a focused ramp. A structured 30‑day plan turns early effort into durable savings, reduced calendar friction, faster inbox responses, fewer small decisions for the exec, and creates repeatable SOPs for future hires.

Pre‑Day‑1: access checklist and the one‑page EA playbook (copy/paste)

• Accounts & devices: company email, Google Workspace or Outlook calendar, Slack or Teams, SSO invites sent and accepted.
• Security: enforce MFA, approved device policy. Set least‑privilege access: grant view only to sensitive folders until Stage 2.
• Legal: signed NDA and a short data‑handling addendum before any sensitive material is shared (sample clauses below).
• One‑page EA playbook (required): executive preferences (core hours, meeting lengths), escalation list, top 10 recurring tasks and examples (sample playbook text below).
• Admin: HR/payroll setup, equipment shipping, and an IT ticket for conditional access policy creation scheduled for Day 1.

Sample one‑page EA playbook (copy/paste)

Executive: [Name, role, time zone]. Core hours: M–Th mornings (9:00–12:00 focused); check‑ins allowed 2:00–3:00pm. Meeting default: 25 minutes; 50 minutes only for workshops. Booking rules: internal team ok with 24h notice; external strategic calls only Tue afternoons. Investor/board invites: notify Exec + [CFO] immediately; EA view‑only for first 30 days. Top recurring tasks: weekly leadership meeting ops (prepare agenda, send notes), travel booking within profile, calendar housekeeping. Escalation: Exec → Alternate (COO) → People Ops → IT (security).

Week 1 (Days 1–7): relationship, calendar handoff, daily 15–30 minute touchpoints

• Day 0/1 Kickoff (30–60 minutes): review the one‑page playbook, immediate calendar risks (investor/board), and top 10 contacts. Walk through how the executive prefers to be briefed (bullet length, channel).
• Daily 15–30 minute syncs (Days 1–4): run a 48‑hour calendar checklist, urgent inbox flags, and confirm access.
• Calendar rules to set Day 1: default meeting length, core hours, meeting buffers, travel blocks, minimum notice for reschedules; set these in Google Calendar or Outlook.
• Safe handover model: EA suggests edits; exec confirms during Week 1. No unilateral cancellations of investor/board meetings during Day 1–7.

Sample 1:1 kickoff script (30 seconds to start): “Hi: I’m [Exec]. My primary week: heads‑down mornings M–Th; best 1:1 time 2:00–3:00pm. I only accept external strategy calls on Tuesdays. For investor/board invites, loop in [CFO] and me. Today: show me the top 3 calendar conflicts and one ask I can confirm now.”

Week 2 (Days 8–14): inbox triage, meeting prep templates, travel profile, begin SOP drafts

• Inbox triage rules: define auto‑flags by sender/domain, canned responses, and what requires exec escalation. Target: median TTR for flagged items <24 hours (illustrative; see KPI note).
• Meeting prep templates: 24–48 hour prep notes with objective, top decisions, attendee list and pre‑reads.
• Travel & expense profile: preferred carriers, class, hotels, approval thresholds, and expense receipt process.
• Begin short SOPs/runbooks for recurring work, board packet prep, weekly leadership meeting ops, use checklists and screenshots (keep steps <8 where possible).

Inbox canned reply (example): “Thanks: I’ve received this and will review. If it requires [Exec]’s input, I’ll escalate within 24 hours. For urgent matters, call the office line at [number].” Use only for predictable categories (meeting requests, vendor outreach).

Week 3 (Days 15–21): ownership of recurring tasks, decision boundaries, and acceptance tests

• Assign 1–3 recurring processes the EA should own (e.g., weekly leadership meeting operations, routine travel booking, calendar housekeeping).
• Document decision boundaries: list what the EA can change without approval, what needs one‑click approval, and what is auto‑escalated (table below for examples).
• Staged access: after repeated correct execution, expand permissions. Use acceptance tests to verify readiness (examples below).
• Audit checkpoints: Day 7, 14, and 21 reviews to confirm proper access and performance; log results in the KPI tracker.

Acceptance tests & audit checklist (operational, copy/paste)

Get an executive assistant quote today.

Part-time or full-time support for calendar, inbox, travel, vendor follow-up, and personal logistics. Tell us what you need and we will scope the right plan.

Request quote

Professionals from top brands trust Aurora

1. 1Task 1: Calendar change: EA reschedules a recurring internal meeting with correct buffer and notes to attendees (no exec corrections).
2. 2Task 2: Meeting prep: EA delivers a one‑page prep note 24 hours before a recurring leadership meeting with decisions and pre‑reads linked.
3. 3Task 3: Inbox triage: EA processes a simulated vendor request using canned responses and escalates correctly.
4. 4Task 4: Travel booking: EA books a routine trip within profile and submits a correctly formatted expense placeholder.
5. 5Task 5: Security check: EA requests access to a restricted Drive folder and follows the correct request/approval workflow (logged).

Week 4 (Days 22–30): wrap‑up, 30‑day review, and simple 60‑day plan

• Prepare a 30‑day scorecard (KPIs listed below) and share it in the review meeting.
• Conduct the 30‑day review (30–60 minutes): confirm ownership, adjust permissions, identify 60‑day goals (higher trust work: vendor relationships, basic approvals, board packet contributions).
• Finalize SOPs into a tagged, searchable drive folder; set audit frequencies and retention policies for sensitive docs.

Early KPIs & quick ROI checklist (what to measure by Day 30)

• Calendar friction: count conflicts and last‑minute reschedules pre‑ vs post‑EA (illustrative target: 20–50% reduction depending on baseline). (Target is illustrative, adjust to your starting point; derived from Aurora onboarding benchmarks and industry practice.)
• Inbox flagged items TTR: median time to first response for flagged emails (illustrative target: <24 hours for non‑urgent flagged items).
• Meeting readiness: % of recurring meetings with a one‑page prep note delivered 24 hours prior (illustrative target: 70%+ for recurring meetings).
• Executive time saved: conservative estimate of hours reclaimed on recurring admin tasks (use a 1‑week time log pre‑ and post‑onboarding for comparison).
• Error/incident count: number of scheduling/privacy mistakes (target: zero incidents for board/investor errors).

Sample executive time budgets (low / medium / high complexity) and a Week 1 sample calendar

Security, compliance, and U.S.‑specific controls (concrete steps)

• Google Drive: use shared drives for sensitive materials; set role = Viewer/Commenter for Stage 1, Grant Manager only after audit; turn off 'download, print, copy' for sensitive files. Enable Drive audit logs and review download events weekly during onboarding.
• Outlook: prefer delegation for assistants who manage calendars (delegate calendar only) vs full mailbox delegation. Shared mailbox is an alternative for team mail, but avoid granting full inbox access until Stage 2 and log access.
• Identity & access: SSO + MFA mandatory; use conditional access to restrict high‑risk actions (e.g., downloads) to corporate devices/IP ranges.
• Retention & audit cadence: tag sensitive docs and set a 90‑day access review during onboarding, then quarterly reviews for high‑sensitivity folders.
• Regulated industries: if you handle PHI (HIPAA), securities communications (FINRA/SEC), or other regulated data, involve legal/People Ops immediately, additional controls and recordkeeping will be required.

Sample NDA / data handling clauses to request from People Ops or legal (send to counsel for final language): 1) Confidential Information definition inclusive of investor/board materials; 2) Prohibition on downloading/sharing outside approved drives; 3) Requirement to follow Company’s security policies (MFA, SSO, approved devices); 4) Immediate notification clause for suspected breaches; 5) Return/destruction of materials on termination. State law and data breach obligations vary, have counsel approve final wording.

Outsourced / remote EA: staged onboarding and cultural calibration

• Staged acceptance: start with non‑sensitive tasks (calendar housekeeping, meeting prep), then move to travel and vendor communications, then sensitive materials after successful audits.
• Operational SLAs: Response SLA for day‑to‑day <4 hours during business day; escalation SLA for urgent board/investor issues = 15 minutes. Log SLA breaches and review during checkpoints.
• Cultural calibration: run two role‑play exercises in Week 1 (handling investor invite, drafting a short email to a board member). Provide feedback on tone and phrasing and record examples in the playbook.
• Audit checkpoints: Day 7 (access + task accuracy), Day 14 (ownership tasks), Day 21 (permission signoff).

Downloadable, editable assets (one‑click templates)

• 30‑Day EA onboarding template (Google Sheets / CSV): https://www.aurora.co/resources/ea-30-day-onboarding-template.csv
• KPI tracker (Google Sheets): https://www.aurora.co/resources/ea-kpi-tracker.xlsx
• Daily & weekly checklists (printable PDF): https://www.aurora.co/resources/ea-daily-weekly-checklist.pdf
• Copyable micro‑copy snippets (email handoffs, canned replies, kickoff scripts): https://www.aurora.co/resources/ea-microcopy.txt
• Sample one‑page EA playbook (DOCX / Google Doc): https://www.aurora.co/resources/sample-ea-playbook.docx
• Sample SOP/runbook template (Google Doc): https://www.aurora.co/resources/sample-sop-runbook.docx

Final checklist & internal reading (copy these into your playbook)

• Pin the one‑page playbook to the Day 1 calendar invite and share with IT/People Ops.
• Schedule the 30‑day review now so it’s a committed checkpoint.
• Run the five acceptance tests and log results in the KPI tracker.
• Attach templates listed above to your onboarding folder and tag sensitive docs with access controls.
• Further reading: What Does an Executive Assistant Do? The Complete 2026 Guide, How to Hire an Executive Assistant Who Actually Frees Up Your Time, Remote Executive Assistant: How It Works and Why It Often Works Better, Calendar Management for Executives: What to Delegate, Inbox Management for Executives: How an EA Takes Control.