An action tracker vs decision log comparison comes down to two different questions: what has the team authorized, and who must do what next? A decision log preserves an approved choice and its limits; an action tracker follows the work needed to carry it out. Use both when a decision creates several tasks, especially when contracts, money or deadlines are involved.
Action tracker vs decision log: the difference at a glance
Imagine an operations team choosing a new courier vendor for a six-month contract. The purchasing manager must approve the commercial choice, but the coordinator still has to collect documents, inform colleagues and schedule the transition. Recording everything as one vague “vendor approved” task loses the reasoning. Recording only the approval leaves nobody accountable for implementation.
| Question | Decision log | Action tracker |
|---|---|---|
| What does it answer? | What was decided, by whom and why? | What must happen next, by whom and when? |
| Typical unit | One consequential choice | One specific deliverable or follow-up |
| Key person | Authorized decision maker | Accountable action owner |
| Useful status | Proposed, approved, rejected, superseded | Not started, in progress, blocked, complete |
| Evidence | Approval note, quote comparison, policy | Completed file, email, signed contract |
| Change handling | Keep old decision and link replacement | Update progress without erasing history |
Build one fictional vendor-contract example
For the example, a fictional company called Harbor Services must replace a courier whose service agreement ends on December 31. Vendor North quotes $2,800 per month, while Vendor East quotes $2,650. The operations team prefers East, but the manager must confirm the price, service coverage and maximum commitment before anyone signs. All names, dates and prices below are illustrative, not supplier recommendations.
On November 9, the manager approves a six-month pilot with Vendor East, capped at $2,650 per month before any additional charges. The approval is conditional on legal review of the contract and written confirmation of weekend coverage. It is not permission to sign immediately. That distinction is precisely why a decision record should separate the approved direction from conditions that remain open.
Completed decision log entry
| Field | Example value |
|---|---|
| Decision ID | DEC-017 |
| Question | Which courier should handle the six-month pilot? |
| Decision | Choose Vendor East, conditional on legal and coverage checks |
| Approver | Operations Manager, Maya Chen |
| Date | November 9, 2026 |
| Rationale | Lower quoted monthly fee; coverage still to be confirmed |
| Limit | $2,650 monthly; six months; no signing until conditions clear |
| Evidence | Approved quote comparison and manager email |
| Status | Conditionally approved |
Translate the decision into an action tracker
The coordinator now creates individual tasks, each with one accountable owner and an observable completion condition. “Move vendor” is too broad: it hides legal review, coverage confirmation and communication inside one status cell. Splitting those steps makes the outstanding conditions visible without pretending the contract is already approved for signature.
| Action ID | Linked decision | Owner | Next step | Due | Status |
|---|---|---|---|---|---|
| ACT-041 | DEC-017 | Jordan, Legal | Review contract clauses and return comments | Nov 12 | In progress |
| ACT-042 | DEC-017 | Leah, Operations | Obtain written weekend-coverage confirmation | Nov 11 | Blocked |
| ACT-043 | DEC-017 | Sam, Procurement | Prepare signature package after both checks clear | Nov 16 | Not started |
| ACT-044 | DEC-017 | Leah, Operations | Notify dispatch staff after signed agreement | Nov 20 | Not started |
These statuses describe the example on November 10. The blocked item does not mean Vendor East failed; it means the team is waiting for evidence. ACT-043 must not be marked complete simply because the manager selected the vendor. Its completion requires a signature package and confirmation that the conditions have been satisfied.
When someone asks why the vendor was selected, open DEC-017. When someone asks why the transition is late, filter ACT-041 through ACT-044. The shared identifier connects the explanation to the execution without duplicating all details in both places.
Set up the two logs in Excel without complex automation
Create separate worksheets named Decisions and Actions. Put the field names from the examples in row 1, then enter each record on its own row. Select the populated range and use Home > Format as Table, confirming that your table has headers. Microsoft documents this workflow in its Excel table guide. Tables make sorting and filtering easier as the list grows; they do not approve decisions or send reminders.
Keep the decision ID and action ID as text, including leading zeros if your numbering convention uses them. A simple hyperlink to the shared evidence folder is more useful than pasting confidential contract language into a widely distributed workbook. Limit editing access to the team responsible for maintaining the records.
For the Actions worksheet, use a controlled status list: Not started, In progress, Blocked and Complete. Excel’s data-validation drop-down guidance explains how to create a selectable list. A drop-down reduces inconsistent spelling; it does not prove a status is accurate. Assign one person to check that completion claims have supporting evidence.
To show overdue work, add a seventh column called Overdue and enter this formula in row 2, assuming E holds an actual Excel date and F holds status: =IF(OR(E2="",F2="Complete"),"",IF(E2<TODAY(),"Overdue","")). Copy it down. For the November 10 snapshot, none of the four example due dates is overdue; on November 12, ACT-042 would show Overdue if it remains Blocked and its November 11 date has not changed. TODAY updates with the workbook’s calculation date, so use a fixed reporting date if you need a reproducible historical snapshot.
For more detailed control over spreadsheet changes, see the Office Logs and Trackers hub. For a deeper explanation of documenting choices, read how to keep a work decision log. The Excel structure here is a simple teaching example, not a claim that every organization needs the same columns.
How to hand off from approval to execution
The handoff should happen at the moment the decision is confirmed, not several days later when someone notices a missed deadline. The meeting facilitator reads back the approval, its conditions and the name of the person responsible for creating follow-up actions. The coordinator records DEC-017, assigns ACT-041 through ACT-044, and sends a short message linking both records.
Copy-ready handoff: “Decision DEC-017: Vendor East is conditionally approved for a six-month pilot at no more than $2,650 per month. No signature is authorized until Legal confirms the contract and Operations obtains written weekend-coverage confirmation. Jordan owns ACT-041 by November 12; Leah owns ACT-042 by November 11. Sam will prepare the signature package only after both conditions are cleared. Please update the action tracker with evidence, not just a status change.”
Notice that this message does not claim the contract is signed or that approval conditions are already met. It states the boundary between permission to proceed with checks and permission to commit the company. That makes the handoff safer than “Approved, please handle.”
Review both logs in a weekly meeting
Start with actions that are blocked or overdue, then review decisions awaiting approval or approaching their review dates. Do not read every completed row aloud. Ask the owner what evidence is missing, who can unblock it and when the next update is expected. If a new fact changes the approved price or term, return to the decision maker rather than letting the action owner quietly change the commitment.
For this example, the November 13 review might show ACT-041 complete, ACT-042 still blocked and ACT-043 not started. The appropriate summary is: “Vendor selected conditionally; legal review complete; weekend coverage unconfirmed; signature not authorized.” It is not “Vendor switch 75% complete,” because four tasks do not carry equal business weight and the approval condition remains unresolved.
If you need an editable starting point, the Office Control Logs & Trackers Kit is US$12 and includes an Action Tracker, Decision Log, Exception Log, Change Log, Waiting For and Handover Register, plus a calculated dashboard and guide. It is a macro-free Excel workbook, not an automated approvals platform. Use the free example above first to decide whether a fuller workbook would save your team setup time.
Common mistakes and quick answers
Can one spreadsheet contain both logs?
Yes. Use separate worksheets or clearly separated tables with their own columns. The important distinction is the purpose of each record, not whether it lives in one file. Link the rows through stable IDs so that a later reader can trace an action to the decision that authorized it.
Who owns a decision log entry?
The named approver owns the authority for the decision. A coordinator may own the administrative work of recording it. Those are different responsibilities. Never put the coordinator’s name in the approver field merely because they typed the row.
Should a blocked action change the original decision?
Not automatically. Record the blocker in the action tracker and escalate it. If the blocker makes the original choice impractical, ask the authorized decision maker to issue a new decision and mark the old one superseded. Keep the earlier rationale available for future review.
What if a task was assigned before approval?
Mark it as preparation or pending approval, and make the dependency explicit. Collecting quotes can be authorized before vendor selection; signing a contract may not be. The action tracker should not turn an unapproved proposal into an apparent commitment.
Bottom line
A decision log preserves the reason and authority behind a consequential choice; an action tracker makes the next steps accountable. For a vendor contract, record the approval and spending limit once, then assign legal review, coverage checks, signature preparation and staff communication as separate actions. Review the linked records together so a completed task never gets mistaken for permission the team has not actually received.