Building a Decision Log the Executive Team Actually Reuses

Start with the decision, not the meeting

A decision log should answer what was decided, who owns the next step, and when the team will revisit it. Start the entry at the moment a meeting produces a choice, not at the end of the quarter when someone tries to reconstruct it. The log belongs beside the agenda and the minutes, not in a separate tool that only one person opens. A short entry written during the meeting is more useful than a polished summary written later.

Write the decision in a complete sentence that a new team member could understand without the recording. Avoid labels such as approved or noted that do not say what was approved or noted. If the team deferred a choice, record the deferral and the condition that must change. The entry should make the next conversation possible without asking the original attendees to explain it again.

Do not copy the entire discussion into the log. Capture the options considered, the reason the team chose one, and the facts that would reopen the question. A log that repeats every comment becomes unreadable and stops being maintained. The useful test is whether a reader can see why the decision made sense at the time. A reader should be able to compare the choice with the alternatives in one pass.

Give every entry a named owner and review date

Every decision needs a person who owns the next action, not a department or a meeting. Write the owner's name and the date the team will check the action. If the owner is a committee, name the chair who will bring the item back. An entry with no owner becomes a historical note rather than a working record. The owner should be able to say what done looks like without asking for context.

The review date should match the pace of the decision. A hiring decision may need a check in two weeks, while a policy change may need a review after the next board cycle. Do not use a default date that no one checks. Put the date in the same calendar or task system the owner already uses. A review that nobody owns is only a hope that the decision stays current.

When the owner changes, update the entry instead of creating a second decision. Record the transfer and the reason so the history remains visible. A new owner should inherit the context, the open questions, and the next review date. That continuity is what makes the log reusable across staff changes. That handoff note should name the date and the person who accepted the item.

Separate the decision from the rationale

The decision is the choice the team made. The rationale is the evidence and trade-offs behind it. Keep them in separate fields so a later reader can see whether the facts changed without rewriting the decision. A rationale that is mixed into the decision text is difficult to test and easy to misquote. The two fields can sit side by side in the same entry without merging.

Record the source of the evidence, the date it was reviewed, and any assumption that could expire. If the team relied on a forecast, say so. If the team accepted a risk, name the person who accepted it. That detail helps the next meeting decide whether to revisit the choice. Keep the source link with the entry so the next review can check it.

Do not edit the original rationale when a new fact arrives. Add a note with the date and the change, then decide whether the decision still holds. The history should show how the team learned, not just what it currently believes. A decision log that hides its own revisions cannot support accountability. A revision note should say what changed and whether the decision still stands.

Make the log searchable and short

Use a consistent set of fields so the log can be filtered by owner, date, topic, and status. Keep the field names stable even when the template looks plain. A searchable log is more valuable than a beautiful document that no one can query. The team should be able to find every decision about a client, a budget line, or a policy.

Limit free text to the parts that need judgment: the decision, the rationale, and the next action. Use controlled options for status, such as open, decided, deferred, or closed. That structure makes review faster and reduces the chance that two entries describe the same decision differently. Use a picklist for status and a short text box for the rationale. That keeps the entry consistent without flattening the judgment.

Review the log for duplicate entries and stale open items before each leadership meeting. Merge duplicates with a cross-reference rather than deleting one. Close items that are complete and record the evidence. A short, current log earns more trust than a comprehensive archive that is never cleaned. Delete nothing; archive closed items with a link to the evidence and the closure date.

Review reuse at the next meeting

At the start of the next meeting, show the decisions that are due for review and the actions that are still open. Ask the owner to report the result, not just the activity. If the action is complete, record the evidence. If it is not, decide whether to change the owner, the date, or the approach. The review should take minutes, not become a second meeting.

Track how often the log is opened or cited outside the meeting. A log that is only read by the person who maintains it is not yet part of the operating rhythm. Use a short review question: did anyone use the log to answer a question this week? The answer shows whether the team is reusing the record. A simple counter in the meeting note is enough to track it.

Choose one improvement based on the review, such as a clearer owner field or a shorter review cadence. Test it for a month and compare how many decisions are closed on time. The goal is not a perfect template but a log the executive team reaches for before reconstructing a conversation. Keep the change for one month before judging whether it worked.

Related resources

• Preparing a Chief of Staff Weekly Agenda from Open Decisions
• Measuring decision log reuse across executive team meetings
• Measuring agenda preparation against open decision ownership

Frequently asked questions