See the queue before you sort it
Most executive offices do not have a decision queue. They have an inbox, a chat thread, a stack of meeting follow-ups, and a few requests that arrived verbally in a hallway. The first step is to gather every pending request into one list, with the source, the date it first appeared, and the person waiting on an answer.
Do not start by prioritizing. Start by making the queue visible, because a request that lives only in someone’s memory cannot be aged, delegated, or closed. Give each item a short neutral label and a link to the original message so the context is recoverable.
Set an entry rule. A request joins the queue when it needs a choice, an approval, or a resource commitment from the executive. Informational updates stay in a briefing file.
Requests that another leader can decide go back to that leader with a named owner and a date.
Classify by decision type
Not every item deserves the same path. Separate approvals, which accept or reject a defined proposal, from choices among options, ratifications of a decision already made elsewhere, and requests for direction on an ambiguous problem. Each type needs different evidence and a different response time.
An approval usually needs the proposal, the amount or obligation, the risk, and the name of the person who will execute it. A choice needs at least two viable options and a recommendation. A ratification needs the record of the prior decision and confirmation that the right body made it.
Direction needs a concise statement of the trade-off and the consequence of waiting.
Tag the type at intake. The tag tells the assistant what to request from the submitter and prevents a half-formed idea from sitting in the executive’s review folder for weeks. It also makes the queue measurable, because aging can be reviewed by type rather than as one undifferentiated backlog.
Age the request honestly
Use the date the request first asked for a decision, not the date of the most recent reminder. A request that has been nudged three times is older, not newer. Record both the first request date and the date the item became complete enough to decide, so the queue distinguishes slow submitters from slow decision-makers.
Group age into a handful of ranges, for example zero to two working days, three to eight, and nine or more. The exact cutoffs should reflect the organization’s rhythm. The point is to make waiting visible without turning the queue into a scoring exercise that invites gaming.
Review the oldest items first, but do not assume age equals importance. An old item may be waiting on a fact that no one can supply. In that case the decision is to close it, narrow it, or send it back, and that decision should be recorded like any other.
Assign an owner and a preparer
Every queue item needs a decision owner and a preparer. The owner is the person with the authority to decide; the preparer is the person who assembles the brief and chases the missing facts. They are often different, and conflating them is how requests stall silently.
Name the consulted parties as well, but keep the list short. A decision that requires six reviewers is usually a decision that has not been framed. If the executive must consult a board committee or counsel, record that requirement and the expected date rather than leaving it as an implicit condition.
When the owner is unavailable, name a delegate in advance and state the limits of that delegation. “Someone will cover” is not a queue control. The delegate should see the same brief and the same evidence standard as the owner, or the decision will be reopened when the owner returns.
Write the one-screen brief
The brief should fit on one screen: the decision requested, the deadline and consequence of missing it, the options, the recommendation, the material facts, and the source links. Put the ask in the first sentence. Executives should not have to infer the question from a narrative.
Keep the evidence proportionate. A routine approval needs the proposal and the authority check. A high-consequence choice needs the financial model, the legal or compliance view, and the dissenting opinion.
Label assumptions and say which ones have been verified.
Do not hide a weak recommendation behind neutral language. If the preparer believes an option is unworkable, say so and explain why. The executive can still choose it, but the record should show that the concern was visible before the decision, not reconstructed after it.
Run a twice-weekly decision review
A short, recurring review keeps the queue from becoming a graveyard. Twice a week, walk the oldest items, the items nearing a deadline, and the items whose missing facts have arrived. Batch similar approvals so the executive is not switching context for every routine signature.
Do not use the review to re-litigate every request. The preparer presents the brief, the owner decides, and the assistant records the outcome. Items that need more work get a specific next action and a date, not a vague “follow up.”
Protect the review from becoming a general staff meeting. If a topic needs discussion rather than a decision, move it to a separate session and leave the queue for choices that are ready. A disciplined twenty minutes is more useful than an hour of status updates.
Close the loop and measure the queue
A decision is not closed when the executive says yes. It is closed when the outcome is recorded, the requester is told, and the next action has an owner and a date. Write the decision in plain language, including any conditions or limits, and link it to the execution task.
Track a small set of measures: the number of open items, the age of the oldest item, how many closed inside the promised window, and the number returned for missing information. These measures show whether the queue is healthy without turning the office into a reporting factory.
Review the measures monthly with the executive or chief of staff. If one department’s requests routinely arrive incomplete, fix the intake template. If the executive is the bottleneck, say so with evidence and propose a delegation.
The queue is a service, and its job is to make decisions easier to make, not to document how busy everyone is.
Background sources consulted for this workflow: How CEOs Manage Time; Work Trend Index; Work, Task and Project Management Resources.