CEO Executive Assistant
The meeting owner promises a pre-read, but the assistant receives fragments late: a deck in chat, a spreadsheet by email, and a revised recommendation minutes before the meeting. The CEO’s protected review time disappears even though every file technically arrived.
The operational problem is not a lack of effort. It is that the request, decision boundary, and proof of completion often live in different systems or in one person’s memory. A workable process gives the assistant enough structure to move ordinary work quickly while making consequential exceptions visible to the right owner.
This guide is distinct from board-pre-read-distribution-workflow because it covers ordinary executive decision meetings and the operational chase cadence, rather than formal board distribution controls. It is a new workflow for a separate customer decision, not a renamed or re-dated version of that earlier article.
Authoritative sources used
- Records Management — National Archives and Records Administration; checked 2026-10-06.
These sources provide current control principles for verification, access, privacy, continuity, or records. Applying them to executive-assistant work is our operational synthesis, not legal, security, privacy, employment, travel, procurement, or compliance advice. Use qualified owners for requirements specific to your organization and jurisdiction.
Work backward from review time
Set the content deadline from the CEO’s required review window, not from the meeting start. Include time for the owner to correct missing sources, reconcile numbers, and produce one authoritative version. A 10 a.m. meeting with a two-hour review need may require a prior-business-day cutoff.
Define what ready means
A pre-read is ready when the decision or discussion outcome is explicit, the recommendation and alternatives are visible, material claims cite their owner or source, open questions are labeled, and the file has a version and accountable author. Page count alone is not a readiness test.
Escalate the consequence, not just lateness
At each chase point, say what will happen if the packet remains incomplete: the item moves, the CEO receives a marked incomplete packet, the meeting changes to discovery, or an authorized owner accepts the risk. This turns reminders into decisions.
Freeze and preserve the meeting version
At the agreed cutoff, identify the version the CEO reviewed. Later changes require a visible delta and a named decision on whether to incorporate them. Do not silently swap an attachment and erase the basis for questions or decisions made in the room.
Use this operating record
Maintain the meeting outcome, packet owner, component list, source owners, draft and final deadlines, review window, current version, unresolved gaps, escalation owner, and the immutable reference to the version used in the meeting.
Mark each consequential fact as verified, assumed, disputed, expired, or pending. Add a source owner and checked time where the fact can change the decision. Link to restricted evidence in its proper system rather than copying confidential material into a general task tracker. Access to an inbox, calendar, document library, signature image, purchasing tool, or executive device does not create authority to decide.
The record should show four gates. At intake, define the observable outcome and consequence of delay. Before execution, verify identity, version, audience, authority, and required inputs. During execution, stop when a material fact changes. At closure, inspect the destination state and reconcile temporary access, copies, notifications, reservations, or follow-up obligations.
Work through a realistic exception
Test the workflow with one ordinary case and one exception before relying on it. Change a single fact: the requester is unfamiliar, the recipient changes, the owner is unreachable, a deadline moves forward, a source conflicts with the brief, or the destination system shows a different state. Ask who detects the difference, which stop rule applies, who may authorize resumption, and what evidence proves the corrected result.
For example, imagine the request arrives near the last useful decision time. The assistant should not hide uncertainty to make the workflow look fast. Instead, surface the verified facts, the missing fact, the safe options still available, the consequence of each option, and the named owner who can accept the residual risk. Urgency changes the update cadence; it does not manufacture authority.
Measure the workflow without rewarding shortcuts
Track packets ready before the review window, meetings converted to discovery because the recommendation was incomplete, late material changes, minutes spent locating the authoritative file, and decisions revisited because the reviewed version was unclear.
Review a small sample monthly during rollout, including both smooth cases and exceptions. Look for work that appeared complete in the tracker but was not complete in the destination system. A low escalation count is not inherently good if people have learned to conceal ambiguity. The useful measures reveal whether the office reached the intended state with proportionate control and recoverable evidence.
Roll it out in 30 days
During the first week, trace two recent examples across email, chat, calendar, documents, and the destination system. In week two, agree on owners, minimum fields, approval boundaries, stop conditions, and closure evidence. In week three, pilot the record on low- and medium-consequence work, including one tabletop exception. In week four, remove fields nobody uses, repair unclear handoffs, document the backup path, and set a review trigger for changes in people, policy, vendors, systems, or risk.
The point is not to create a longer checklist. It is to make the safe path understandable to another authorized person without requiring them to guess at the executive’s intent. That reduces avoidable back-and-forth while preserving the decisions that genuinely belong with the CEO or a qualified functional owner.
Final review questions
- What exact destination state are we trying to create?
- Which facts are current, and who owns each source?
- What remains outside the assistant’s authority?
- Which material change invalidates the present approval?
- What is the last useful decision time, including time zone?
- Which evidence will prove closure without exposing excess information?
- What temporary access, copies, or obligations must be removed afterward?
For hands-on help building reliable executive workflows, review our project and task coordination service or start a conversation.