How to maintain an executive assistant decision log

Decision management

Key takeaways

• Record the decision separately from the discussion that produced it.
• Name the decision authority, affected owners, and required communication.
• Use review triggers so an old choice is not treated as permanent by accident.

Operating data

Playbook

An executive assistant decision log is a controlled record of consequential choices, not a transcript of every leadership conversation. It gives the executive and team a reliable answer when someone asks what was decided, who had authority, why the choice was made, and what must happen next.

Start with an inclusion rule. Log decisions that change a priority, commitment, budget, owner, deadline, policy, or stakeholder expectation. Routine task updates can stay in the task system. If a choice could later be disputed or reopened because context was lost, it belongs in the decision log.

Use a small, stable set of fields: decision date, concise decision statement, decision owner, affected people, rationale, source meeting or message, resulting actions, communication status, and review trigger. The assistant should draft the record, but must not imply approval until the named authority has confirmed the decision.

Atlassian's decision documentation template separates the driver, approver, contributors, and informed stakeholders while capturing status, impact, due date, options, and outcome. That structure is useful even when the team uses another tool because it distinguishes participation from final authority.

Write the decision as a complete statement that survives outside the meeting notes. Replace vague entries such as ‘proceed with option two’ with the chosen action, scope, effective date, and any limit on authority. Preserve relevant rationale, but do not manufacture certainty or copy confidential discussion into a broadly shared register.

Connect each approved decision to execution. The operations follow-through service can translate the choice into named actions, deadlines, and checkpoints. When the decision changes a meeting, access rule, or protected work block, update the relevant system rather than assuming readers will infer the operational effect.

Communication is a separate field because recording a decision does not mean affected people know about it. Identify who must be informed, who will send the message, and when acknowledgment matters. For decisions that alter calendar access, the executive calendar strategy guide shows how to turn leadership intent into enforceable scheduling rules.

Review the log during the weekly operating rhythm. Flag decisions with approaching review dates, incomplete actions, missing confirmation, or new facts that may justify reconsideration. Never silently overwrite an old entry; mark it superseded and link the replacement so the history remains understandable.

The log should reduce repeated debate without freezing judgment. A review trigger might be a date, metric threshold, contract renewal, staffing change, or newly available evidence. If the trigger occurs, return the decision to its authority with current facts and the consequences of keeping or changing course.

Keep access proportional to sensitivity and verify the workflow with one real decision before expanding it. Teams that need help connecting decisions to accountable follow-through can request a tailored support plan. The system works when the executive can decide once, the assistant can route the consequences, and the team can recover the reasoning without searching across inboxes and meetings.