Aurora illustration for Weekly Planning With an Executive Assistant
Delegation Playbook10 min read

Weekly Planning With an Executive Assistant: The Reset That Saves Your Week

A practical, copy‑ready playbook for U.S. executives evaluating a dedicated EA to own weekly planning: short cadences, exact scripts, a populated one‑page weekly brief, an accelerated 30/60/90 onboarding plan, security practices, and realistic ROI vignettes.

Key takeaways

  • A dedicated EA running your weekly planning reclaims predictable focus time, stabilizes priorities, and makes meetings higher‑value with one‑page briefs and automated follow‑ups.
  • Adopt a short, scripted cadence (three 10–15m check‑ins or one 30–40m weekly session). Use copy‑paste scripts, a stakeholder intro template, and a populated one‑page weekly brief to start immediately.
  • Onboard fast with a detailed 30/60/90 map that includes access, security milestones (NDA, SSO, least privilege), and measurable executive time commitments; expect directional ROI shown in three illustrative vignettes.

Reviewed by Aurora

Aurora publishes these guides for founders and executives across the US evaluating dedicated assistant support. We refresh articles against current public sources and Aurora's operating experience so they stay grounded in how buyers actually make decisions.

Last reviewed May 2, 2026

8 public sources referenced

Who this guide is for: and what you’ll get

For U.S. executives and decision‑makers (startup founders, mid‑market VPs, and C‑suite leaders at 500–5,000 employee companies) evaluating a dedicated executive assistant to run or improve weekly planning. This playbook gives: a recommended cadence, copy‑ready scripts, a populated one‑page weekly brief you can copy immediately, a detailed 30/60/90 onboarding map with executive time estimates, security checklists, tool guidance (Outlook/Google Workspace, Asana/Notion), and directional ROI vignettes.

Why weekly planning with a dedicated EA moves the needle

Executives lose momentum to three common drags: reactive calendars, shifting priorities, and meeting churn. A dedicated EA who owns weekly planning reduces each by operating as your repeatable operational layer: protecting deep work, surfacing priority tradeoffs, and owning pre‑reads and follow‑ups.

  • Time reclaimed: protect scheduled deep work and reduce ad‑hoc meetings.
  • Better strategic focus: weekly prioritized decisions keep long‑range work from being crowded out.
  • Improved meeting preparedness: agendas, pre‑reads, and action tracking are delivered reliably.

Illustrative outcomes

Examples are directional: a founder who offloaded calendar triage regained a recurring 3‑hour deep work block; a VP reduced recurring status meetings by 30% after consolidating pre‑reads; a COO shortened prep for board materials by centralizing document pulls and follow‑ups. Results vary with role, meeting density, and scope.

Who does what: roles and responsibilities

  • Executive: sets strategic priorities, makes final decisions, protects deep work windows, and attends short weekly check‑ins for sign‑offs.
  • Dedicated EA: owns weekly brief, calendar triage, agendas, pre‑reads, action tracking, stakeholder data pulls, and automated follow‑ups.
  • Other stakeholders (direct reports, PMs, admins): supply status updates to the EA on agreed cadence and respond to information requests.

Role‑selection decision checklist

  • Choose Chief of Staff when: cross‑functional strategic programs, stakeholder alignment, >5 org teams to manage, or you need deputy‑level influence.
  • Choose Dedicated Executive Assistant when: primary need is consistent operational ownership: calendar + meeting prep + follow‑up: and you want one high‑trust owner for your rhythm.
  • Choose Personal Assistant when: needs are mainly personal/lifestyle (errands, household scheduling) rather than strategic planning.
  • Choose Virtual/Outsourced EA (dedicated model) when: you want cost efficiency with U.S.‑calibrated remote support and documented security controls.

The ideal weekly cadence: timing, options, and scripts

Pick a cadence that fits your schedule. The EA prepares and shares the one‑page weekly brief 24–48 hours before your primary check‑in.

  • Start‑of‑week (15 minutes): EA delivers the brief; confirm top‑3 priorities and immediate decisions.
  • Mid‑week (10–15 minutes): rapid status; EA flags risks and proposes mitigations.
  • End‑of‑week (15 minutes): review what shipped, carryovers, blockers, and next‑week prep needs.

Single weekly session (30–40 minutes)

Use this when you prefer one concentrated alignment. EA shares the brief 24–48 hours before and runs the agenda: review last week’s outcomes, confirm top priorities, unblock decisions, and assign follow‑ups.

Copy‑ready, exact language for check‑ins (copy‑paste)

  • Start‑of‑week EA opener: “Good morning: this week’s top items are 1) Product launch tasks, 2) Board deck approvals, 3) hiring decisions. I’ve blocked 3x1hr deep work windows: Mon 9–10am, Wed 2–3pm, Fri 9–11am. Items requiring your sign‑off today: A (approve by EOD), B (choose option 1 or 2). What do you confirm?”
  • Start‑of‑week exec line: “Confirm. Approve A. Delegate B to Priya with deadline Thursday EOD. Block my calendar Thursday 3–4pm for the launch review.”
  • Mid‑week EA opener: “Quick check: item A is on track; B slipped to Friday unless we reassign. I recommend reallocating X to Y. Your call.”
  • Mid‑week exec line: “Reassign B to Y and push deadline to Friday. Please confirm with Y and update the brief.”
  • End‑of‑week EA opener: “What shipped vs. planned: shipped X, Y; carryover Z. Decisions pending: C (due Monday). Recommended next steps are… ”
  • End‑of‑week exec line: “Approve recommendations for C; keep Z on next week’s top 3. Please confirm owners and due dates in the brief.”
  • Template approval phrase for quick sign‑offs (use verbatim): “I approve [item]. Delegate to [owner]. Follow up by [date].”

Stakeholder intro email (EA should send this in Week 1)

Subject: Quick intro: [Executive]’s weekly planning rhythm Hello [Name], I’m [EA name], [Executive]’s dedicated executive assistant. Each week I’ll collect short status updates for our weekly brief and coordinate agendas. Could you please: 1) share a 1–2 sentence status on your active items by Thursday 3pm; and 2) flag any decisions you need from [Executive] this week? I’ll keep requests brief and only ask for what’s essential. Thanks: [EA name / contact info]

Weekly deliverables your EA should produce

  • One‑page weekly brief (top‑3 priorities, calendar snapshot, decisions requested, blockers, and action log).
  • Calendar clean‑up and proposed protected time blocks (deep work, focus windows).
  • Meeting agendas and one‑paragraph pre‑reads for major meetings, shared 24–48 hours in advance.
  • Action log with owners, due dates, and automated follow‑up reminders.
  • End‑of‑week recap with shipped items, carryovers, and recommended rebalancing.

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.

Professionals from top brands trust Aurora

Brand logo 1Brand logo 2Brand logo 3Brand logo 4

One‑page weekly brief: populated sample (copy‑ready)

Week: May 4–10, 2026 | Executive: Dana Lee (VP Product) | EA: Jordan Ruiz Top 3 priorities 1) Launch beta onboarding flow: QA complete; awaiting legal sign‑off (status: at‑risk: legal approval needed by Wed 5/6). 2) Hire Senior PM: interview panel scheduled; top candidate interview Tue 5/5 (status: on‑track). 3) Prepare Exec Review deck for Friday: draft ready; need revenue slide update (status: action required). Calendar snapshot (key blocks) - Mon 9–10am: Deep work (blocked) - Tue 11–12pm: Candidate interview (do not interrupt) - Wed 2–3pm: Focus block (blocked) - Fri 8–10am: Exec Review prep (blocked) Decisions requested 1) Legal approval to ship beta onboarding (owner: Dana): due Wed 5/6 EOD 2) Approve headcount for Senior PM (owner: Dana): due Thu 5/7 noon Blockers & suggested next steps - Legal has open question on data retention; suggested next step: EA to pull last‑quarter retention policy and schedule 15m with Legal by Tue 5/5. Action log - Jordan (EA): Schedule 15m with Legal by Tue 5/5: due Tue 5/5: status: open - Priya (Hiring): Send candidate feedback form to panel: due Tue 5/5: status: sent - Mark (Revenue): Update slide with April numbers: due Thu 5/7 10am: status: pending Notes: This brief shared 48 hours before primary weekly check‑in. Exec to confirm or edit top‑3 in the Start‑of‑week 15m.

Tools, integrations, and U.S. calendar guidance

Match the EA’s tooling to your stack: Outlook or Google Workspace for calendars; Slack for quick signals; Asana/Trello/Notion for the action log; Google Docs or Notion for the shared brief. Practical U.S. calendar tips:

  • Outlook: use Scheduling Assistant, decline+propose time, and set sensitivity/private flags for confidential invites.
  • Google Calendar: use Find a time / Suggested times, set Working hours, and email scheduling with delayed send for different time zones.
  • Cross‑time‑zone execs: block consistent local focus windows, indicate time zones in brief (e.g., EDT), and use calendar descriptions to show preferred contact windows.
  • Best practice: EA sends calendar invites with clear purpose and time‑zone friendly options and uses ‘decline + propose’ rather than silence for low‑value invites.

Quick‑win checklist: what to hand off immediately (Week 1)

  • Grant access: calendar, Slack, select inbox folders, and shared drive to the EA (use least privilege, see security checklist).
  • Calendar triage: ask the EA to cancel or renegotiate non‑essential recurring invites and propose protected focus blocks.
  • Meeting prep: EA drafts agendas and pre‑reads for the next three critical meetings.
  • Stakeholder intro: EA sends the one‑paragraph intro email to direct reports (template above).
  • Shared brief: EA populates the one‑page brief for the coming week and shares 24–48 hours before your main check‑in.

30/60/90 accelerated onboarding checklist (detailed with executive time)

  1. 1Day 0 (Kickoff: executive time: 60–90 minutes): NDA signed; account provisioning decisions; list of core apps & permissions; high‑level priorities and top‑3 goals for next 90 days.
  2. 2Day 1–7 (Access & triage: exec time: 30–45 minutes total): SSO/SSO provisioning or least‑privilege sharing; EA audits calendar and recurring invites; EA cancels/renegotiates obvious nonessentials and proposes protected blocks; initial stakeholder intros sent.
  3. 3Day 8–14 (First briefs & trial runs: exec time: 30 minutes spread across check‑ins): EA delivers first populated weekly brief; run first Start‑of‑week check‑in with exec; EA iterates brief format based on feedback.
  4. 4Day 15–30 (Ownership & stabilization: exec time: 15–30 min/week): EA implements action log, automates follow‑ups for overdue items, and runs check‑ins with increasing independence; EA owns meeting agendas and pre‑reads.
  5. 5Day 31–60 (Cadence & coverage: exec time: 15–30 min/week): EA runs check‑ins solo, integrates stakeholder updates, and begins proactive risk flags and suggested tradeoffs.
  6. 6Day 61–90 (Proactivity & optimization: exec time: 15–30 min/week): EA proactively recommends priority tradeoffs, optimizes calendar patterns, and reduces ad‑hoc interruptions; evaluate coverage and adjust scope or hours.

Security, compliance, and U.S. practices (actionable)

Ask for: and document: these items during onboarding: 1) Signed NDA and role‑specific confidentiality rider; 2) Identity verification and background check (industry norm: criminal & employment verification); 3) SSO provisioning or least‑privilege account sharing, with MFA enabled; 4) Audit logging for file access and admin changes; 5) Data residency expectations (note differences for regulated data in healthcare/finance). For highly sensitive work, prefer U.S.‑based or U.S./timezone EAs and include contract clauses about data handling. Aurora implements dedicated assignments, background checks, and documented access logs; review our security and privacy details before provisioning.

Typical time‑savings and ROI: illustrative vignettes (directional)

Below are three directional vignettes showing how time‑savings are derived. These are examples, not guarantees. See our deeper ROI framework at The ROI of an Executive Assistant: A Better Way to Measure Return.

  • Startup Founder (high meeting density): Baseline: ~25 meeting hours/week. Handed off calendar triage (remove nonessential 1:1s), delegated meeting prep, and prioritized deep work blocks. Result: removed 3 recurring 30‑min meetings (1.5 hours), consolidated prep saved ~2 hours, calendar triage prevented 2 ad‑hoc 30m meetings (~1 hour) = illustrative reclaimed 4.5 hours/week.
  • Mid‑market VP (medium meeting density): Baseline: ~18 meeting hours/week. EA consolidated status meetings, produced pre‑reads that shortened recurring updates by 30%, and automated follow‑ups. Result: reduced recurring meeting time by ~2 hours, saved ~2 hours in prep/follow‑up = illustrative reclaimed 4 hours/week.
  • C‑suite Executive (lower meeting count but higher prep cost): Baseline: ~12 meeting hours/week with heavy prep. EA centralized board & exec prep, pulled documents, and maintained action log. Result: saved 3–5 hours/week in prep time and last‑minute pulls = illustrative reclaimed 3–5 hours/week.

Combined outcomes depend on meeting load, willingness to delegate inbox/decisions, and scope of EA responsibilities. For pricing and scope alignments, see Executive Assistant Pricing Guide: What You Are Really Paying For.

Short answers to common objections

  • “I don’t have time for weekly meetings.”: Use the short check‑ins (Start/Mid/End). EA prep keeps live time minimal and decision‑dense.
  • “Remote EAs aren’t culturally calibrated.”: Require U.S.‑calibrated communication protocols, dedicated assignments (no rotating pool), and an onboarding checklist that includes stakeholder intros and language/style expectations.
  • “Onboarding will be a months‑long drain.”: Follow the detailed 30/60/90 map. Executive time investment concentrates in Day 0–14 (1–2 hours total) and then drops to short weekly check‑ins.

Aurora: how we accelerate this rhythm: and next steps

Aurora’s dedicated‑EA model pairs you with one trained assistant who owns weekly planning, supported by security controls and a defined onboarding methodology. Request a sample weekly brief (we deliver within 48 hours after intake) or book a 15‑minute consult to scope priorities and expected coverage. CTAs: Request sample weekly brief | Book a 15‑minute consult. For operational reading, see How to Hire an Executive Assistant Who Actually Frees Up Your Time and Calendar Management for Executives: What to Delegate.

If you want to pilot a dedicated EA for weekly planning: 1) Request the sample weekly brief (48‑hour turnaround), and 2) Book a 15‑minute consult to align scope. Helpful reads: What Does an Executive Assistant Do? The Complete 2026 Guide, Remote Executive Assistant: How It Works and Why It Often Works Better, The ROI of an Executive Assistant: A Better Way to Measure Return, and 15 Tasks Every Executive Should Delegate to an EA Immediately.

Appendix: one‑page weekly plan layout (copy‑ready)

Header: Week range | Executive | EA owner Section A: Top 3 priorities (1‑line status each) Section B: Calendar snapshot (blocked deep work, travel, critical meetings) Section C: Decisions requested (owner, due date) Section D: Blockers and suggested next steps (owner contact) Section E: Action log (owner, action, due, status) Use this as a Google Doc or Notion page and share it 24–48 hours before your main weekly check‑in.

Frequently asked questions

Will weekly planning meetings take too much of my time?

No: use the short check‑in cadence (Start‑of‑week 15m; Mid‑week 10–15m; End‑of‑week 15m) or a single 30–40m weekly session. The EA prepares the one‑page weekly brief in advance and follows up with action owners, so your live time is focused on decisions, not status updates.

How long until an EA is operating independently on weekly planning?

An accelerated 30/60/90 roadmap is realistic for many executives: Day 0–30 covers access, triage, and initial briefs; by Day 31–60 the EA runs check‑ins and automates follow‑ups; by Day 61–90 the EA is proactively surfacing tradeoffs. Complexity varies, so treat this as a target path with exact timing dependent on role and scope.

Can a remote or outsourced EA meet U.S. confidentiality and compliance expectations?

Yes: require explicit measures: background checks, signed NDAs, SSO/MFA provisioning with least‑privilege access, and audit logging. Consider onshore or U.S./timezone‑based EAs for highly sensitive work or regulated industries (healthcare, finance). Aurora’s model uses dedicated assignments and documented security controls.

Sources consulted

Aurora reviews current source material while building and refreshing these articles so the guidance stays grounded in the market executives are actually buying in.

Get started

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.

Aurora planning moment
Aurora assistant
Focused professional
Aurora team detail
Desk detail
Aurora work scene