CEO Executive Assistant
Build an Executive Delegation Intake Queue That Produces Clear Outcomes solves a narrow but important executive-office problem: whether a request is ready to delegate and which person has the authority, context, and capacity to own it.
For this workflow, capture requester, intended outcome, business reason, owner, deadline, priority, authority, source materials, dependencies, approval points, status, and completion evidence.
The assistant may clarify requests, maintain the queue, route work under standing rules, and surface conflicts. The executive or accountable function owner decides strategic priority, material tradeoffs, sensitive access, budget, personnel consequences, and exceptions to policy.
Consider this case: During one day the CEO sends requests through email, chat, voice notes, and meetings. By evening, several tasks use verbs such as “handle,” “look into,” and “follow up,” but nobody can say what finished means.
Useful indicators include requests with a defined outcome and owner, duplicate requests merged, untriaged age, overdue decisions, reopened tasks, blocked items escalated, and closure evidence accepted.
Diagnose the request before assigning it
An intake queue is most useful when it exposes work that is not ready to delegate. “Handle the board follow-up” might mean schedule a call, collect written answers, obtain a decision, or send a commitment on the CEO’s behalf. Before choosing an assignee, rewrite the request as an observable outcome. Identify the recipient, the latest acceptable completion time, the source material, and the decision that remains with the executive.
Do not ask for every possible detail. The intake should collect only what changes ownership or execution. A travel question may require the traveler, fixed dates, destination, approval limit, and constraint that cannot move. It does not require a biography of every participant. When information is missing, return the item with one precise question. A queue clogged with vague “need more context” comments trains requesters to bypass it.
Work a request that crosses authority boundaries
Consider a CEO who forwards a partner’s email and writes, “Please take care of this today.” The partner wants a revised delivery date and hints that a discount would preserve the relationship. The assistant can identify the contract owner, confirm the current milestone, and prepare response options. The assistant cannot promise a date the delivery team has not accepted or offer a concession without commercial authority.
The queue should split the work. Operations owns the feasible delivery date. The account owner recommends the relationship response. The authorized commercial leader decides any concession. The assistant coordinates the deadline, assembles the facts, and sends only the approved message. The original request remains one outcome, but the record makes the dependencies and decision rights visible.
If the deadline passes while an owner is silent, the escalation is not “CEO, what should we do?” The assistant reports which decision is blocked, who has the required authority, what happens if no answer arrives, and the safest available holding response. That gives the executive a bounded exception rather than the entire workflow back.
Manage capacity without rewarding queue jumping
Urgency should be tested against consequence and fixed timing. A request from a senior person is not automatically urgent, and a short message may carry a hard external deadline. Ask what changes if the item waits until tomorrow. If the answer is embarrassment rather than material impact, it may not displace a payroll, regulatory, customer, or safety commitment.
Publish a small number of service classes. Same-day work might cover externally fixed decisions or incidents. Standard work can follow a stated response window. Planned work belongs on a project schedule rather than in a perpetual urgent lane. Exceptions need a reason and a named approver. Review who uses the exception route; repeated priority inflation is an intake-design problem, not proof that the team needs more colored labels.
Capacity conversations should happen before acceptance. An assignee who already owns three fixed deadlines can offer a later date, a narrower result, or another qualified owner. The queue records that negotiation. Quietly accepting impossible work makes the dashboard look healthy until the executive discovers the missed promise.
Prove completion with the recipient’s outcome
Completion evidence depends on the request. A scheduled meeting needs accepted participants and a confirmed time, not merely an invitation draft. A briefing needs the approved version in the intended location. A vendor answer needs receipt by the named contact. A decision request needs the recorded decision and any conditions translated into follow-up work.
Reopened items deserve separate attention. Some reopen because facts changed; others reopen because the original outcome was ambiguous or the assignee lacked authority. Sample both. Correct the intake question when it failed to reveal a dependency, and correct the delegation boundary when an assignee was asked to improvise. Over time, the queue should make fewer requests bounce, not merely process more rows.
The executive should see a short exception view: overdue accepted work, decisions waiting on executive judgment, ownerless requests, and commitments likely to miss an external deadline. Everything else can remain with the operating owners. That is the queue’s real value: it lets delegation continue without converting the CEO into the dispatcher for routine work.
Distinguish coordination from ownership
A queue often assigns work to the person who is best at chasing responses. That person becomes the visible owner even though another colleague controls the result. For a customer renewal, an assistant might coordinate dates and documents, but the account leader owns the commercial recommendation and legal owns contract language. Record those roles separately. The coordinator can then surface a missed dependency without being held responsible for a concession they could not authorize.
Test the distinction when an item stalls. If the coordinator has collected every input but the accountable owner has not chosen among options, the queue should show “decision overdue,” not “work in progress.” Conversely, if an owner decided but no one delivered the response, coordination remains open. This split makes delay diagnosable. It also prevents executives from solving every late item by adding the assistant as another owner. During a monthly sample, ask whether each named owner could personally accept the consequence of the outcome. If not, the assignment was administrative shorthand rather than a real delegation.
Retire requests that no longer justify attention
Not every accepted request should survive unchanged. When the underlying meeting is canceled, the customer chooses another option, or a later decision makes the output irrelevant, close the item as superseded and name the event that ended it. Do not let it become an unexplained overdue task. A short weekly review of aging work can distinguish legitimate long-cycle assignments from requests that everyone has quietly abandoned. This protects capacity and keeps completion rates honest.