BLOG

Decisions Waiting on You? Build a Founder Decision Queue

Your VA may have completed the preparation, yet work still sits waiting for your answer. This guide shows how to build a founder decision queue with clear questions, recommendations, decide-by times, safeguards for unanswered items, and a record of the final decision.
Prepared decision folders waiting for owner review in a small office approval tray
On This Page

Your virtual assistant has checked the options, prepared the next step and correctly asked for your approval. Three days later, the question is still buried in chat. Two other tasks cannot move until you answer it.

The approval rule worked. Your VA knew which decision belonged to you. What failed was the process for getting that decision answered.

A founder decision queue solves this by keeping every decision that genuinely needs the owner in one maintained list. Each entry should contain the question, relevant context, options, a recommendation, a decide-by date with a reason, and the work that is waiting. Your VA prepares and tracks the entry; you make the decision. The answer then goes back into the task or document where the work happens.

This is the next step after you set clear approval rules for your virtual assistant. The authority ladder establishes what your VA may handle independently and what needs your sign-off. The decision queue manages the items that correctly remain with you.

Why decisions that should stay with you still become the bottleneck

Clear authority doesn’t guarantee that decisions happen on time.

Your VA may already know not to approve a new vendor, agree to an unusual client request or publish an unreviewed statement. But without a reliable way to present those decisions, each question may end up in a different place.

One sits in an email thread. Another waits in a project-management comment. The third was mentioned during a call but never recorded.

When the deadline passes, the task can appear late even though the person assigned to execute it has completed everything within their authority.

This distinction matters when diagnosing why delegated work is missing deadlines. Capacity, unclear instructions, dependencies and performance problems can create similar symptoms. Work awaiting an owner decision needs a different remedy from work that exceeds the VA’s available hours.

McKinsey’s 2019 decision-making survey also points to the limits of clear decision roles alone. Its findings suggest that assigning decision rights is not enough without practices that support timely, effective decisions. The survey involved executives and managers from organizations of different sizes, so its findings should not be treated as measured results for small businesses using virtual assistants.

The decision isn’t always the slow part

Think about a vendor quote that needs approval.

Comparing three offers might take your VA several hours. Choosing between the prepared options might require only a short response from you, provided the comparison is complete and the trade-offs are clear.

The delay often happens between the finished preparation and your answer.

Simply adding another reminder doesn’t fix the underlying problem if you still have to search for the quote, reconstruct the context and ask what your VA recommends.

The better handoff is one that makes the remaining decision immediately understandable.

What a founder decision queue is (and what it isn’t)

A decision queue is a list of open decisions waiting for a named decision-maker, with enough information and a clear deadline to get them resolved.

It is related to your task tracker, weekly report and decision log, but it serves a more specific purpose.

ToolMain question it answersWhat’s missing for pending decisions?
To-do listWhat work needs to be done?May not explain the choices or consequences of waiting
Weekly VA reportWhat was completed, blocked or carried forward?Usually summarizes decisions among other updates
Founder decision queueWhat exactly must the owner decide, by when and with what information?Designed for open decisions awaiting an answer
Decision logWhat was decided, by whom and why?Primarily records decisions already made

My weekly VA report template already provides a place to identify blockers and client decisions. That is useful for reviewing the broader workload.

The decision queue goes deeper on the individual approval. Instead of reporting only “waiting for client approval,” it shows the precise question, a suggested answer, what happens if the decision is delayed and what response is still required.

Once the owner answers, the queue entry becomes a record of that decision. It should no longer appear as unresolved work.

You don’t need specialized approval software for this. Your existing task system or a shared spreadsheet may be enough, provided everyone agrees which location is authoritative.

Anatomy of one decision queue entry

The most useful entry is one the owner can understand and answer without reconstructing the entire task.

It should capture the decision question, supporting material, available options, recommendation, decision deadline, consequences of delay and final response.

This approach is consistent with Atlassian’s DACI decision-making framework, which separates responsibility for preparing a decision from responsibility for approving it. DACI also calls for context, options, dates, relevant information and a recorded outcome.

Write a question that can be answered in one reply

“Vendor issue” isn’t a decision request.

“Do you approve Vendor B’s quote for the agreed scope, or should I request revised pricing?” is much closer.

The second version identifies the choice the owner needs to make. It also makes the next action easier to understand.

Your VA should attach the relevant source material instead of copying a long conversation into the approval request. When comparing suppliers, a prepared vendor comparison sheet can show differences in scope, price, exclusions and terms before you choose.

If the information isn’t sufficient to make a sensible decision, the entry should say what’s missing rather than present an unsupported recommendation.

The recommendation is the VA’s most useful contribution

Decision preparation shouldn’t stop at listing options.

Where the scope and expertise permit it, your VA can explain which option appears strongest and why.

For example:

Recommendation: Request a revised quote from Vendor B before approval.

Reason: Its initial price looks lower, but the onboarding fee and cancellation terms are unclear.

The recommendation gives the owner something concrete to accept, reject or modify. It doesn’t grant the VA authority to approve the purchase.

Bain’s RAPID decision roles distinguish between recommending a course of action and deciding whether to proceed. For a founder working with a VA, that separation is useful even without adopting the full corporate framework.

The VA can gather facts, compare options and recommend. The owner retains the decisions assigned to them.

Put the reason beside the deadline

“Please approve soon” is easy to postpone because it gives no useful timing information.

Instead, write:

“Decide by Thursday, 3:00 p.m. WAT, because the supplier’s quoted delivery window must be confirmed that afternoon.”

The time and time zone matter when a founder and assistant work in different locations. My guide to working with a virtual assistant across time zones explains why explicit handoff times are more reliable than phrases such as “later today.”

Your VA should distinguish between a real external deadline and a preferred internal review date. If the deadline is flexible, label it accordingly.

The queue must also say what’s blocked. The owner can then judge whether the pending decision deserves attention ahead of less consequential items.

Defaults belong only to genuinely reversible decisions

Not every unanswered question needs to stop all progress. But silence should never become permission to take an action that wasn’t authorized.

Jeff Bezos discussed reversible decisions in his 2016 letter to Amazon shareholders, arguing that decisions which can be undone may justify lighter processes. That is a useful principle, not permission for a VA to invent an approval rule.

For a low-risk internal layout choice, an owner might agree in advance:

“If I haven’t replied by 4:00 p.m., use Option A in the internal draft. Don’t publish anything.”

That gives the VA a limited, reversible fallback.

No answer must mean no approval for spending, contractual commitments, access changes, sensitive customer matters, public statements and actions that are irreversible or costly to reverse, unless a separate explicit authority arrangement already covers the action.

The default field should say “None” when an approved fallback doesn’t exist.

For anything with meaningful risk, the next step is to hold the action, notify the owner and use the agreed escalation route.

Close the loop by recording the owner’s answer

An approval shouldn’t live only in a chat reaction or a brief call.

Record the decision, who made it, when they made it and any conditions they attached.

For example:

“Approved Vendor B, subject to written confirmation that onboarding is included. Do not place the order until that confirmation arrives.”

This is more useful than simply changing the status to “Approved.” It tells the VA what is permitted and which condition still needs checking.

The decision record should appear in the task, document or system where the work will continue. The guide to tools for managing a virtual assistant covers the broader principle of keeping working instructions and updates easy to find.

Running the queue: one home, one rhythm, one rule for silence

The queue needs a few operating rules, but it shouldn’t become another large management project.

One home. Agree on one authoritative location for open owner decisions. A message or email can notify you that a decision is ready, but the full entry and its eventual answer belong in the maintained queue or linked task. Avoid keeping competing versions in several channels.

One review rhythm. Review decisions according to their real deadlines. If your work involves same-day approvals, a short daily review may fit. Less time-sensitive work may need only two scheduled reviews each week. Neither frequency is a universal standard. The nearest decide-by time should determine when attention is required.

One explicit silence rule. Decide what happens when an owner hasn’t responded: hold the task, send a reminder, escalate through an agreed channel, or use a specifically approved reversible fallback. Don’t make the VA guess whether silence means yes.

When an entry reaches its decide-by time unanswered, the VA can update its status, notify the owner and record the consequence of further delay. They shouldn’t repeatedly change the deadline just to make the item look current.

What should bypass the normal queue?

Urgent security incidents, legal deadlines, safety issues and serious customer crises need the agreed immediate escalation route, not a routine batch of decisions waiting for the next review.

The queue may record what happened afterward for traceability, but it should not delay urgent contact or qualified advice.

If no escalation route exists, establish one through your VA approval rules before relying on the queue for critical work.

Watch the oldest decision, not the longest list

The number of open decisions tells you how much is waiting. Their age can tell you more about where work is getting stuck.

Record the day each decision was first raised, then check how many days it has remained unanswered.

During a review, examine overdue items first, followed by decisions approaching their due times and older items that still have no clear resolution.

Don’t automatically prioritize a harmless old item ahead of a new decision involving a serious consequence. Age is a warning signal, not the only priority rule.

It also helps to look for repeat questions.

If your VA sends the same type of decision each week and you consistently give the same answer, you may have found an opportunity to create a rule. The next occurrence might belong in a documented procedure or at a lower authority level, provided the risks and conditions justify that change.

That is where writing a clear SOP for recurring VA tasks becomes useful.

Repeatedly approving the same harmless formatting choice is different from repeatedly approving purchases or permission changes. Some decisions should remain with you even when they become familiar.

When a decision queue is the wrong tool

Not every business needs a dedicated approval register.

If only one or two straightforward owner decisions arise occasionally, an existing task status and clear notification may be sufficient. Creating another table would add administration without much benefit.

The queue also isn’t a substitute for deciding who has authority. When the owner and VA disagree about what requires approval, resolve the authority question first.

For genuinely urgent matters, use immediate escalation rather than waiting for the next queue review.

Finally, a queue cannot force an owner to decide. It makes unanswered questions and their consequences visible. If the owner routinely avoids decisions, the solution may require simplifying the choices, changing commitments or resolving the underlying disagreement.

A copyable founder decision queue

Start with a spreadsheet, database table or equivalent view in your existing task tool.

Give each decision its own row. Keep the supporting documents linked rather than copying entire emails into cells.

The table below includes all the fields needed to prepare, date, track and close an owner decision.

ID / date raisedDecision questionContext and linksOptionsVA recommendation and reasonDecide by and whyWhat’s blockedDefault if no answerOwner answerRecorded inAge
____________________________None unless pre-agreedPending________

For a spreadsheet implementation, calculate Age from the date raised while an entry remains open. Once answered, preserve the final decision date and stop treating it as an open item.

Fictional example: three decisions at different risk levels

The following entries are entirely fictional. Assume the owner is reviewing the queue on April 15, 2027, at 9:00 a.m. West Africa Time. The dates and choices illustrate how different decisions receive different handling, not a prescribed response-time policy.

Decision D-01: Internal presentation layout

  • Raised: April 13 (2 days open).
  • Question: Which layout should be used for an internal presentation draft?
  • Context/options: Two draft layouts linked in the task, Option A or B.
  • Recommendation: Option A, because the figures are easier to compare.
  • Decide by: April 16, 3:00 p.m. WAT, ahead of internal review.
  • Blocked: Final formatting of the internal draft.
  • Default: Owner pre-agreed that Option A may be used in the internal draft if there’s no answer. Nothing may be published or sent externally.
  • Owner answer / recorded in: Pending; presentation task.

This is a low-risk, reversible choice with a narrowly approved fallback.

Decision D-02: Vendor quote

  • Raised: April 10 (5 days open).
  • Question: Which vendor quote should be approved, if either?
  • Context/options: Linked comparison sheet; Vendor A, Vendor B or request revised terms.
  • Recommendation: Request revised terms from Vendor B because an onboarding charge is unclear.
  • Decide by: April 15, noon WAT, because the illustrative booking window is due to close.
  • Blocked: Vendor selection and purchase order.
  • Default: None. No purchase without explicit approval.
  • Owner answer / recorded in: Pending; vendor procurement task.

The oldest entry is also approaching its deadline. The VA can prepare a clarification request but cannot commit the business to the purchase.

Decision D-03: Client-facing exception

  • Raised: April 14 (1 day open).
  • Question: Should an unusual client request be accepted or declined?
  • Context/options: Linked request and agreed scope; accept, decline or propose different terms.
  • Recommendation: Decline the request as written and offer a scoped alternative.
  • Decide by: April 15, 10:00 a.m. WAT, because a client response is due.
  • Blocked: The client’s next update.
  • Default: None. The external commitment requires an explicit owner response.
  • Owner answer / recorded in: Pending; client communication task.

Although this entry is newer than the vendor decision, its earlier deadline deserves attention first. The VA can prepare the response, but the owner must authorize the final position.

The rules beneath the table

Keep these rules alongside the queue so that the way it is used remains clear:

  1. Location: Every pending owner decision is recorded in one agreed queue, with a link back to the underlying task.
  2. Review: The owner reviews the queue on a rhythm that fits the nearest decision deadline. Urgent items follow a separate escalation route.
  3. Silence: No answer means hold and follow up unless a specific reversible fallback was approved in advance.
  4. Graduation: Repeated decisions with stable, low-risk answers may become written rules, while sensitive or high-impact decisions remain at the appropriate approval level.

The aim is not to eliminate the founder’s decisions. It is to make them easier to prepare, quicker to locate and clearer to resolve.

Look at the oldest unresolved item in your queue. Does it still need your judgment, or has the same question been returning because nobody documented the answer?

If you want help gathering the context, preparing recommendations, tracking deadlines and recording decisions, explore my virtual assistant support for admin and operations. The preparation and follow-through can be delegated while the decisions that belong to you remain yours.

Not Sure What to Delegate?

Recurring workload or a clearly defined project? Boost VA can help shape it into a practical support plan.

Good fit if you need help with:

  • Recurring business tasks
  • Research and admin
  • SEO / WordPress execution
  • Content or project support
Ongoing SupportRecurring tasks & workflows
Defined ProjectClear scope & deliverables
Picture of Rahman Salami

Rahman Salami

Rahman Salami is a retained virtual assistant and founder of Boost VA, supporting founders, agencies, and online businesses across growth, backend, and operations. With over seven years of virtual assistant experience, he helps clients reduce day-to-day friction through reliable execution, clear communication, and practical support across SEO, research, WordPress, data management, social media, and administration.

View Author Profile

Share This Article

Related Articles

Business owner reviewing guest invitations for an upcoming client meeting

Should Your Virtual Assistant Attend Client Meetings?

Not every client call or project meeting needs your virtual assistant in the room. This guide helps founders decide when live attendance adds value, when notes will do, when a short agenda slot is enough, and how to handle client awareness, recordings, time and responsibility.

Two bakery workers behind a counter, one checking a smartphone while the other prepares the display

Google Business Profile Messaging: Text, WhatsApp or Neither?

Google Business Profile chat ended in 2024, but eligible businesses can now add text or WhatsApp contact options. This guide explains what changed, how the options differ, why messaging may not appear on your profile, and what to arrange before customers start sending messages.

HVAC technician checking a missed call beside an outdoor air conditioning unit

Missed Call Follow-Up for Home Service Businesses: Scripts

Missed calls can turn into risky promises when someone without technical authority is asked about prices, repairs, and arrival times. This guide gives home-service owners a callback authority card, examples of what to say, emergency hard stops, a practical call log, and cautious text-back templates.