Executive Decision Log Template: Assumptions, Evidence, Owners and Review Dates
An executive decision log is not a list of meeting minutes. It is a compact record of what was decided, why it was decided, which assumptions matter, who owns execution and when the decision should be revisited.
Without that record, teams often repeat old debates, misremember the original rationale or continue executing after the evidence has changed. This guide provides a copyable template, a decision-quality check and a worked example.
Which decisions belong in the log?
Record a decision when at least one condition applies:
- it reallocates meaningful people, capital or executive attention;
- several functions must act differently because of it;
- the choice depends on uncertain assumptions;
- reversal would be costly or slow;
- a regulatory, customer or reputation consequence is possible; or
- future leaders will need to reconstruct the rationale.
Do not turn every routine approval into governance overhead. The log should preserve material decision memory, not become another task tracker.
The TRACE-6 decision record
| Field | Question | Minimum content |
|---|---|---|
| T — Trigger | Why is a decision needed now? | Event, deadline, problem and consequence of delay |
| R — Recommendation and rejected options | What was chosen, and what credible alternatives were not? | Decision statement and trade-offs |
| A — Assumptions | What must remain true for the choice to work? | Testable assumptions with confidence level |
| C — Consequences and commitments | What changes because of the decision? | Owners, resources, dependencies and risks |
| E — Evidence | Which facts support the choice? | Sources, dates, gaps and contradictory signals |
| 6 — Six review controls | Can the decision be governed after approval? | Owner, date, indicator, threshold, escalation and closure rule |
Copyable executive decision log
Decision identity
Decision ID:
Title:
Decision owner:
Decision date:
Required-by date:
Status: proposed / approved / superseded / closed
Trigger and scope
Decision question:
Why now:
In scope:
Out of scope:
Consequence of no decision:
Options and decision
| Option | Expected benefit | Main cost/risk | Reversibility | Decision |
|---|---|---|---|---|
| A | ||||
| B | ||||
| C |
Approved choice:
Rationale in three sentences:
Dissent or unresolved concern:
Evidence and assumptions
| Item | Type | Source/date | Confidence | Test or next evidence |
|---|---|---|---|---|
| Fact / estimate / assumption | High / medium / low |
Execution commitments
| Commitment | Owner | Due date | Dependency | Completion evidence |
|---|---|---|---|---|
Review controls
Review owner:
Review date:
Leading indicator:
Outcome indicator:
Reconsideration threshold:
Escalation route:
Closure or supersession rule:
Worked example: a pricing test
Assume a software company must decide whether to raise the price of its mid-market plan.
Trigger: gross margin has declined while support demand has increased.
Decision: test a 12% increase with new customers in two segments for eight weeks; existing customers remain unchanged during the test.
Rejected option: a universal immediate increase was rejected because churn sensitivity is unknown.
Critical assumption: qualified conversion will not fall by more than 8%.
Evidence: segment contribution margin, win-loss interviews and support cost by cohort.
Owner: Chief Revenue Officer; Finance owns the economic readout.
Review: week four operational check and week eight decision.
Reconsideration threshold: pause if qualified conversion falls more than 8% or complaint volume breaches the agreed threshold.
The example is useful because it preserves both the decision and the conditions under which it should change.
Separate the log from three neighbouring tools
| Tool | Primary purpose | Why it is not the decision log |
|---|---|---|
| Meeting minutes | Record discussion and events | Often chronological and too broad |
| Action tracker | Track tasks and deadlines | Does not preserve rationale or assumptions |
| Risk register | Track exposures and treatment | May not state the business choice that created or accepted risk |
| Decision log | Preserve choice, rationale and review logic | Connects evidence to execution and reconsideration |
Link the tools rather than duplicating them. A decision can point to actions and risks while remaining the authoritative record of the choice.
A five-minute quality check
Before approval, ask:
- Can a reader state the decision in one sentence?
- Are at least two credible options visible?
- Are facts separated from assumptions?
- Does every commitment have one accountable owner?
- Is the review date tied to evidence rather than habit?
- Is there an explicit threshold for reconsideration?
- Can the record be understood without attending the meeting?
If the answer to any of the first six questions is no, the record is probably an action note rather than a governed decision.
Operating cadence
Use three cadences:
- at approval: complete the decision and commitments;
- during execution: update evidence and actions without rewriting the original rationale;
- at review: close, continue, adapt or supersede the decision with a new linked record.
Never silently replace the original assumption. Preserve what leaders believed at the time and add the evidence that changed the choice.
Practical conclusion
A decision log creates organisational memory only when it records uncertainty and a path to reconsideration. TRACE-6 keeps the record short enough to use while connecting the executive choice to evidence, ownership and review.
For related decision tools, see MTF's AI SWOT evidence-first workflow and Strategic Finance Decision Stack.