Executive Decision Memo Routing: From Draft to Recorded Decision

Executive Decision Memo Routing: From Draft to Recorded Decision solves a narrow but important executive-office problem: whether a decision memo is ready for the accountable executive and what review must occur before the decision is recorded.

For this workflow, capture question, recommendation owner, options, verified facts, assumptions, risks, consulted functions, decision owner, deadline, decision, conditions, and communication owner.

The assistant may enforce the format, coordinate reviewers, flag missing evidence, schedule the decision, and record the result. The assistant does not author specialist conclusions or choose on behalf of the accountable decision owner.

Consider this case: A five-page memo recommends entering a new partnership, but the actual question is buried, finance reviewed an older version, legal comments are unresolved, and the CEO’s decision deadline is not stated.

Useful indicators include memos complete on first executive review, version conflicts, decisions made by deadline, open assumptions, conditions tracked, decisions reopened, and communications completed.

Start with the decision and decision-maker

Before polishing a memo, write the question in a form the authorized person can answer. “Review international expansion” is a topic. “Should the company fund a three-month market test in Country A within the proposed cap?” is a decision. Name who holds that authority and who must advise, concur, or receive notice. Routing a vague topic to more readers does not create a decision.

The memo should make the deadline credible. Explain what external event, option expiry, or downstream commitment sets the date. Separate a real constraint from a project team’s preferred pace. If waiting preserves useful information, include that as an option. If delay closes an option, show when and how.

Build evidence around disagreement

A decision-maker benefits from knowing where informed people differ. Summarize the strongest case for each viable option, the assumptions behind it, and the evidence that could change the recommendation. Do not manufacture balance by giving an implausible option equal space. Do not hide dissent in an appendix if it concerns a material risk.

Identify the source and observation date for changeable facts. Revenue forecasts, staffing availability, regulatory interpretations, and vendor quotes age differently. A link alone is not enough when the linked document can change; cite the version or snapshot used. Label estimates and explain their sensitivity to the decision.

Route a memo with a late factual change

Suppose a CEO is due to approve a distribution partnership. The memo recommends approval based on a launch date and exclusivity term. An hour before the meeting, counsel learns that the counterparty changed the territory definition. The assistant should not swap the attachment and leave earlier comments attached to an obsolete version.

The memo owner issues a clearly marked revision, summarizes the changed fact, and states which analysis it affects. Counsel updates the legal consequence. The commercial owner confirms whether the recommendation stands. Reviewers receive the revision through the same controlled route, while the prior version is retained as superseded rather than silently overwritten.

If the change removes the basis for a decision, the owner should recommend deferral. A scheduled executive meeting is not a reason to force a yes or no on incomplete evidence. The record can show that the decision was postponed, what evidence is required, who owns it, and the next decision point.

Control versions without creating ceremony

Use one authoritative location, a visible status, and an owner allowed to issue a new version. Drafts can circulate for working review, but the decision packet should contain only the version presented for approval. Comments that change substance must enter the memo or a documented decision note; they should not remain scattered across chat and email.

Access follows the sensitivity of the decision. Personnel, acquisition, legal, and security memos may require narrower review than ordinary operating choices. The routing list should reflect who supplies evidence or holds authority, not who might be interested. Remove temporary access when the purpose ends.

Translate the decision into execution

A recorded answer is incomplete until affected owners know what it authorizes. State the chosen option, effective date, spending or scope limit, conditions, and any actions explicitly not approved. Assign each condition to someone who can satisfy it. A condition without an owner becomes a future argument over whether the decision took effect.

Communicate at the right level. The project team may need detailed constraints; a broader group may need only the outcome and next step. Sensitive rationale should not be copied into every announcement. The decision log can point authorized readers to the memo while giving others the minimum needed to act.

Later review should ask whether the assumptions held and whether conditions were met, not relitigate the choice with hindsight. If new evidence warrants reopening, create a new decision request that cites the prior record. This preserves accountability while allowing leaders to change course deliberately.

Assign one person to close the routing record. That person confirms the final version, authority, decision time, conditions, communication owner, and destination in the decision log. Without a closer, a memo can remain marked “pending” after the executive decided or appear approved before a condition was satisfied. Administrative closure is not the same as making the decision, but it is what lets the organization act from a reliable record instead of oral recollection.

Preserve dissent without turning the memo into a transcript

A decision memo loses value when disagreement is either erased or reproduced as pages of meeting notes. Ask each dissenting owner to state the assumption they reject, the consequence if they are right, and what evidence would change their view. The writer can place those points beside the recommendation. The decision-maker then sees where judgment is doing real work without reading every exchange that produced it.

After the decision, retain the rejected alternative only when it explains a condition, risk, or future trigger. For example, a company may choose the smaller launch because capacity is constrained, while recording that the larger launch becomes viable if a supplier passes a stated test. That is useful institutional memory. A list of every brainstorm is not. When conditions later change, open a new decision record that cites the earlier rationale; do not silently edit history until the old choice appears to have anticipated the new facts.

Set an expiry for time-sensitive recommendations

A memo built on prices, capacity, or legal conditions needs a date after which its recommendation must be refreshed. Put that limit near the decision request. If the decision arrives late, the owner should identify which assumptions remain valid before execution begins. This prevents a well-routed but stale memo from becoming false authority. The decision record can remain permanent while the operational permission it granted expires.