How Executive Assistants Support Quarterly Planning and OKR Prep
Byline: RemoteExecutiveSupport Editorial Team
Executive assistant quarterly planning: what the role covers
Quarterly planning is one of the most time-intensive organizational cycles an executive manages. Gathering input from department leaders, reviewing prior-quarter results, facilitating the goal-setting process, and producing the documentation that comes out of it all take significant coordination effort.
An executive assistant's role in this cycle is not strategic. The EA does not set objectives or evaluate performance. Their role is to make the logistics of the planning cycle invisible, so the executive can spend available attention on the substance of the planning rather than on coordinating its mechanics.
Done well, EA support for quarterly planning means the executive arrives at the planning sessions with complete input, pre-read materials distributed, the right people in the room, and follow-up processes already set up. The administrative surface of the cycle disappears entirely.
Pre-quarter preparation tasks for the EA
The EA's quarterly planning work starts three to four weeks before the planning sessions themselves. This early work includes scheduling all planning sessions on the calendar, confirming participants, and communicating what input is needed from each department leader before the session.
Many organizations use a standard input template for department leaders to complete before the quarterly planning meeting. The EA sends the template, tracks submissions, follows up with non-respondents, and compiles the inputs into a single summary document the CEO can review before the session. This replaces the informal and inconsistent input-gathering that often characterizes undermanaged quarterly cycles.
The EA also coordinates any pre-reads: prior-quarter performance summaries, financial snapshots, key metric reviews, and strategic context documents. These are distributed to participants with enough lead time to review them before the session.
Supporting the planning sessions themselves
During planning sessions, the EA is typically not present. Their pre-session work is done. What the EA does is remain available for logistics support: pulling up a document that was not included in the pre-read, booking a room extension if the session runs long, or handling a coordination issue that arises mid-session.
In some organizations, the EA handles note-taking during planning sessions, either in person or via video. When this is the case, the EA captures decisions, open questions, and action items in a structured format rather than a narrative transcript. The output should be scannable and immediately actionable, not a verbatim record of the conversation.
After the session, the EA formats and distributes the session output to participants with a clear deadline for reviewing and confirming decisions. This post-session distribution is a step that often gets skipped in organizations without EA support, and its absence is one reason planning decisions fail to take hold.
OKR documentation and follow-through support
If the organization uses OKRs, the EA supports the documentation and tracking process that follows the planning sessions. This includes formatting the agreed objectives and key results in the company's tracking tool, setting calendar reminders for mid-quarter check-ins, and coordinating the input-collection process for the quarterly review.
The EA's most valuable contribution to OKR cycles is follow-through coordination. Objectives can be agreed upon cleanly and then drift as the quarter progresses and immediate work pressures displace the plan. The EA surfaces that drift before the end of the quarter, when adjustments are still possible.
For guidance on the broader meeting preparation and follow-through function, executive meeting preparation covers how skilled EAs manage the full cycle of high-stakes meetings from logistics to post-meeting follow-up.
For executives who use quarterly planning as part of a structured time design, the CEO ideal week template covers how to structure the executive's time at the quarterly level and what to protect across each planning horizon.
The MIT Sloan Management Review has documented that strategy execution failures often originate in the gap between planning sessions and day-to-day decision-making. EA-managed follow-through processes, such as tracked action items and structured check-in cadences, directly address that gap.
Frequently asked questions
What does an executive assistant do during quarterly planning?
The EA handles logistics and follow-through across three phases: pre-quarter input gathering and session scheduling, in-session support (availability for logistics, note-taking in some organizations), and post-session output distribution and OKR documentation. The strategic content is the executive's domain; the EA makes the process mechanics invisible.
When should the EA start quarterly planning coordination?
Three to four weeks before the planning sessions. This allows time to schedule all sessions, communicate input requirements to department leaders, collect and compile input, and distribute pre-read materials before participants arrive.
What is the EA's role in OKR tracking?
The EA formats and distributes agreed OKRs after planning sessions, sets calendar reminders for mid-quarter check-ins, coordinates the end-of-quarter review input process, and surfaces any objectives that appear to be drifting before the quarter closes. The EA does not evaluate performance; they manage the process cadence that supports evaluation.
How does EA support improve quarterly planning outcomes?
When logistics and input-gathering are managed reliably, the executive and department leaders arrive at planning sessions with complete information and can focus the session time on substantive decisions. Post-session follow-through that is actively managed significantly improves the implementation rate of planning decisions.
Can a remote executive assistant manage quarterly planning coordination?
Yes. Quarterly planning coordination is primarily asynchronous: input gathering, document distribution, note formatting, and tracking tool updates do not require physical presence. The EA communicates with participants, manages the document flow, and handles follow-through from any location. Remote delivery of this function is standard and effective.