Keep the decision log current for the quarter-start review
A decision log that keeps the decision, the owner, the date, and the reopen condition in one reviewable place.
Why the decision log needs a quarter-start check
At quarter start, decision log is often described in meetings rather than in a record. The gap becomes visible when the executive is travelling and the decision register holds three versions of the same request. The check should establish which version governs, who may change it, and what evidence proves the change happened. Write the rule where the work is assigned so the next shift does not need a meeting to interpret it. Name the system of record and the person who may change the rule.
Choose one recent case, such as a pricing exception agreed in a steering meeting, and trace it end to end before writing the rule. Note where the request entered, which fields were copied, and where the decision was recorded. A decision without an owner is only a discussion. That trace also shows which fields were checked against a source and which were copied from a similar item.
What the decision log record must show
The record needs four facts: decision, decision owner, date, and review trigger. Each fact should have a named source and a timestamp, because a later reviewer cannot tell whether a blank means none or unknown. If a field is missing, write missing and route the gap instead of borrowing a value from a similar item.
Keep the entry short enough to finish during a busy day. Link the meeting note and the follow-up action to the same decision identifier. A four-line note with dated facts beats a long narrative that nobody updates. The note should be readable in under a minute and still answer who, what, when, and what happens next.
Where the assistant's role stops
The assistant may prepare, compare, and route decision log items, but the executive keeps the decision. The boundary belongs in the queue itself, not only in a handbook that new hires read once. A boundary that lives only in a training call disappears during the first busy week.
When a request crosses that line, preserve the request, state the missing approval, and send it to the executive. An escalation is a finished step, not a failure. The chair confirms the decision and the owner accepts the action. The record should show that the handoff happened, who received it, and what answer came back.
The daily decision log routine
Open the decision register list at the same time each day and work from the oldest unresolved item. Record what moved, what is waiting, and which dated source supports the next action. Do not start with the newest message just because it looks urgent.
The routine is to capture decisions in the meeting and confirm them the same day. End the shift with a note that names the next owner and the next check date, even when nothing moved. A short daily note is easier to trust than a dashboard that nobody reconciles.
Exceptions that should pause the work
Pause the item when two meetings produce conflicting decisions. These cases change obligations rather than wording, so the assistant should not resolve them from memory. The assistant may gather facts and draft a summary, but should not choose the outcome.
Superseded entries stay visible with a dated reason so the change can be explained later. Log the reason, the person notified, and the time of the handoff. A recurring exception points to a rule that needs rewriting, not a person who needs retraining. Name the rule that failed, not the person who followed it.
How to confirm and close the record
Close the decision log item only after the destination record shows the approved change and the reviewer who confirmed it. A sent message or a screenshot alone proves activity, not completion. The confirmation belongs with the original request, not in a separate success folder.
Check open decisions against the action list and close only those with evidence. Sample one ordinary item, one exception, and one reopened item at the quarter-start review; the mix says more than a clean average. Use a weekly decision review before the leadership meeting as the working rhythm. Write the next check date before the review ends.
Keep planning
Questions people ask
What should the team check first on decision log?
Start with the oldest open item and confirm the four record fields: decision, decision owner, date, review trigger. If any field lacks a source or a timestamp, mark it missing instead of guessing.
Which decisions stay with the executive?
Anything that changes money, access, policy, a legal obligation, or a client promise. The assistant prepares the record, compares the sources, and routes the exact missing approval.
How should the quarter-start review test the record?
Sample one ordinary item, one exception, and one reopened item. Compare each against the destination record and note one process change, one owner, and one check date.
Reference notes
These links are a starting point for general context. They are not custom legal, tax, hiring, or cybersecurity advice.
- NIST SP 800-53 Rev. 5: Control guidance used for audit, ownership, and record integrity.