Executive assistant management

Executive Assistant Weekly One-on-One Agenda

Use a focused weekly one-on-one to reset priorities, clarify authority, review exceptions, give feedback, and improve the executive-assistant partnership.

Hiring guide desk with scorecards, interview notes, and executive support planning materials
In this guide
  1. Define the executive support outcome
  2. Match role scope to leadership cadence
  3. Use a structured selection process

Use the meeting for choices, not task recital

A weekly executive-assistant one-on-one earns its place when it resolves choices that cannot be settled through standing rules. Routine task status belongs in the shared queue before the meeting. Live time should address changed priorities, authority questions, relationship context, sensitive exceptions, feedback, and one improvement to the operating system. If every line is an update, the executive remains the bottleneck while both participants leave without clearer rules for the next week.

Prepare from the open-work record

The assistant should scan commitments, waiting decisions, next-week calendar pressure, recurring meetings, travel, and requests that have exceeded their useful response point. Bring only items needing executive judgment or context. Each decision item should name the desired outcome, source, options, last useful time, affected commitment, and recommended next move. The executive should add emerging priorities before the session so the assistant can identify collisions instead of discovering them during discussion.

Open with changed reality

Start by asking what changed since the last alignment: a new customer issue, board request, hiring priority, travel constraint, personal boundary, or leadership decision. Changes matter more than a complete review of stable work. Identify which existing commitments are now threatened. The executive must choose the tradeoff or confirm the rule that applies. Recording the reason helps the assistant handle the next similar request without treating one emergency as a permanent priority.

Review the next ten working days

Look beyond tomorrow's calendar. Check decision meetings, preparation blocks, travel transitions, deadlines requiring executive input, and relationships needing follow-through. Confirm the purpose and required output for major meetings. Surface missing pre-reads or unaccepted owners while recovery is still possible. This forward view is not an invitation to fill open time; it protects the sequence of preparation, decision, and recovery that makes executive time useful.

Resolve priority collisions explicitly

When requests compete, compare consequence, reversibility, last useful time, relationship obligation, and the work displaced. The assistant can prepare facts and options, but the executive or named delegate owns consequential tradeoffs. State the choice, who needs to hear it, and whether the decision creates a new standing rule. Avoid labels such as urgent without a decision deadline or consequence. They teach the system to reward whoever escalates most loudly.

Renew delegated authority

Review one authority boundary each week while the partnership is forming. Confirm what the assistant may gather, prepare, recommend, execute, communicate, or decline. Discuss borderline cases and any action taken under emergency authority. Access to an inbox, payment tool, or calendar is not permission to use every function. Record approved changes with an effective date, and remove authority that no longer matches the role or current risk.

Coach through one real decision

Choose a recent case where the assistant hesitated or the executive corrected an outcome. Reconstruct the information available at the time, the rule applied, the missing context, and the consequence. Explain the reasoning behind the correction rather than simply replacing the output. The assistant should say how the rule will change future action. This turns feedback into transferable judgment and reveals when the instruction, not the person, caused avoidable rework.

Invite upward feedback

The assistant needs a safe route to identify unclear instructions, delayed executive inputs, competing stakeholders, unsustainable availability, or tools that make compliance difficult. Ask which recurring request creates the most reconstruction and which executive habit blocks completion. The purpose is operating improvement, not blame. Personnel-sensitive notes remain in the approved people process; accepted workflow changes move into shared instructions so the correction benefits future work.

Check capacity before adding scope

New work should displace, delay, or receive additional capacity; it should not disappear into an unchanged list. Review request volume, interruption, preparation, waiting time, and coverage. Name what will pause during board weeks, travel, or absence. If several executives share support, confirm who resolves their conflicts. A clear no or not yet protects higher-value commitments and gives leaders evidence for a staffing or process decision.

Close every decision with evidence

End each agenda item with an owner, action, date, affected parties, and acceptance condition. Update the authoritative queue during or immediately after the meeting. A statement such as handle travel is not closed; confirm the itinerary constraint, approval limit, traveler decision, and proof of booking. Mark waiting work with the person who must act. This prevents the one-on-one from creating a second private task system.

Protect continuity and absence

Review upcoming leave and the workflows that cannot wait. Confirm the backup, minimum access, activation authority, open-work handoff, and return acceptance. Test one normal case before a critical period. The backup should not inherit every message or private note. Good continuity preserves commitments and escalation paths while limiting exposure, and it leaves the primary assistant a reliable record of actions taken during the absence.

Measure whether the meeting is helping

Track repeated clarification, decision carryover, overdue executive inputs, reopened work, priority overrides, and cancellations of the one-on-one itself. Sample cases rather than chasing a perfect score. A healthy rhythm should reduce recurring ambiguity and shorten the path to accountable decisions without increasing access or after-hours pressure. If the same issues return, revise the agenda, authority, capacity, or executive behavior instead of lengthening the meeting.

Keep private matters in the right place

The one-on-one may surface performance, health, family, legal, or employee information. Discuss only what the workflow requires and store sensitive records in their authorized systems. The shared agenda can carry a neutral action or controlled link without reproducing private detail. Confirm who may see the agenda and how long it is retained. Operational convenience should not turn a recurring meeting document into an uncontrolled personnel or executive diary.

Use a compact closing agenda

A practical close has five prompts: what changed, which choice was made, which rule changed, who must be informed, and what will be reviewed next week. Confirm one improvement experiment and its owner. Remove completed items and archive superseded instructions. The result should be a calmer operating week with fewer private assumptions, not a polished document that nobody consults after the call.

Related resources

Read also: Executive assistant support and Remote executive support operating rhythm. Source: O*NET profile for executive administrative assistants.

FAQ

Can one person perform both roles?

Sometimes, but only when the combined outcomes, authority, capacity tradeoffs, and review expectations are explicit.

Which role should a founder hire first?

Hire against the first missing outcome: stabilize executive flow when logistics and follow-through are failing; add broader synthesis when cross-functional decisions remain unresolved.

Discuss executive support