How an Executive Assistant Can Run a Weekly Decision Log Routine
Byline: RemoteExecutiveSupport Editorial Team
Executives rarely struggle because every decision is difficult. More often, a small approval sits in email, a meeting ends without an owner, or two people assume the other person will follow up. A decision log gives those loose ends a visible home.
The log is not a transcript. It is a short record of what needs a decision, who owns the next step, and when the matter should move. A remote executive assistant can maintain it with a brief weekly review.
Capture decisions at the point of need
Add an item when someone asks for approval, a meeting creates a commitment, or a blocked task needs an executive choice. Use plain language. “Approve the vendor renewal by Thursday” is easier to act on than “Vendor discussion.”
Each entry should include:
- the decision or action required
- the person who must decide
- the requested date
- the recommendation or relevant context
- the next owner after approval
Do not copy an entire email thread into the log. Link to the source and summarize the part the executive needs to decide.
Review the log before the weekly meeting
The assistant should clean the list before presenting it. Close decisions that are complete, merge duplicates, and move routine items into the normal task system. Then group the remaining entries by deadline or consequence.
Put the oldest unanswered items first. An item that has been waiting for two weeks may need a clearer recommendation, a different owner, or an explicit decision to stop the work.
Write recommendations that can be approved
A useful recommendation names the choice and its consequence. For example:
Approve the revised briefing format for next month, or keep the current version? The revision removes two unused sections and gives the team more room for decision notes.
The assistant should show the source of the recommendation and identify uncertainty. The executive can then approve, change, or reject it without reconstructing the whole history.
Separate approval from coordination
Not every open item belongs in a decision log. Scheduling a routine meeting, requesting a missing document, or updating a task owner usually needs coordination rather than executive approval. Keep those items in the appropriate operating system.
Include an item when delay could change a commitment, create a material risk, or block another person. When the boundary is unclear, keep the context short and escalate instead of making a sensitive judgment alone.
Close the loop after the decision
Record the decision in the same entry. Add the date, the person who approved it, and the next action. Then notify the owner and link the decision from the relevant task or project note.
Do not leave “approved” as the final state. A decision is useful only when someone knows what changes now. If the decision creates a new deadline, add that deadline to the source system rather than relying on the log as a second calendar.
Keep access narrow
Decision logs can contain personnel, legal, financial, or customer information. Store them in the approved workspace, use named accounts, and grant the minimum access needed. Put sensitive details in the controlled source document and keep the log summary neutral.
The assistant should also review old entries for stale links and people who no longer need access. Remove or archive records according to the organization’s retention rules.
A 20-minute weekly cadence
Most teams can maintain the routine in a short weekly pass:
- Spend five minutes closing completed entries and removing duplicates.
- Spend five minutes checking deadlines and missing context.
- Spend five minutes preparing recommendations for the executive.
- Spend five minutes recording decisions and assigning next actions.
The exact timing matters less than the handoff. The executive should receive a small list that can be answered, not a second inbox.
What to measure
After a few weeks, review how many decisions remain open past their requested date, how often an entry lacks an owner, and how many items return because the recommendation was unclear. Also ask whether the log reduces follow-up messages or simply adds work for the assistant.
If the list grows, tighten the entry rule. The goal is not to document every conversation. It is to make consequential decisions easy to find and easy to move.
FAQ
Should the decision log replace a task manager?
No. Use it for decisions and approvals, then put the resulting work in the system that owns the task.
How many items should the executive see at once?
Show the items that need attention now. Archive completed entries and group longer-term decisions by the date they become relevant.
Can the assistant decide which items to close?
Close routine items when the source confirms completion. Escalate anything involving legal, financial, personnel, safety, or reputation-sensitive judgment.