Decision Register vs Action Log: Why Boards Need Both

A proposal that keeps coming back

Say you sit on the board of a 40-bed nonprofit hospital, and three meetings ago the board voted 6-2 to outsource laundry services starting next fiscal year. Minutes were taken, the vote was recorded, and everyone moved on. Two meetings later, a newer trustee — who missed that session — raises the exact same proposal, unaware it was ever discussed, and the board spends twenty minutes re-debating something that was already settled. Nobody did anything wrong. The decision just wasn't easy to find, and the follow-up tasks that came out of it were buried somewhere in a shared drive instead of tracked anywhere useful.

This is a structural problem, not a people problem, and it's why boards need two separate records instead of one messy one.

What is the difference between a decision register and an action log?

A decision register is a permanent record of what a board decided — the vote count, the date, who voted and how, and the reasoning behind it. An action log is a working list of the tasks that follow from a decision — who owns the follow-up, when it's due, and whether it's done. The register is meant to stay fixed once a decision is logged; the action log is meant to change constantly, right up until the last task closes.

Confuse the two, or keep them in the same document, and you end up with a record that's neither a reliable history nor a useful to-do list.

Side-by-side: register vs log

| | Decision Register | Action Log | |---|---|---| | Purpose | Permanent record of what was decided | Working list of what needs to happen next | | Typical contents | Motion text, vote tally, date, rationale, dissent noted | Task owner, due date, status, linked decision | | Changes over time? | No — once logged, it's historical | Yes — status updates until closed | | "Done" means | Nothing — it stays as evidence of the decision | The task is completed and can be archived | | Who checks it | Anyone questioning "did we already decide this?" | Anyone asking "who owns this and is it late?" | | Risk if missing | Boards re-debate settled questions | Decisions get made but never actually executed |

Why mixing them leads to re-litigating decisions

When a decision and its follow-up tasks live in the same running notes document, a few predictable things happen. The record gets long and hard to search, so people stop checking it before raising a topic again. Task status updates get mixed in with the original vote language, so it's unclear months later whether the board actually changed its mind or just updated a status note. And because minutes are often treated as something you write once and file away, nobody goes back to mark action items as resolved — so the board can't tell at a glance what's still open versus what was decided and executed long ago.

The fix isn't more detailed minutes. It's separating the two functions so each one does its job well: the register answers "what did we decide and why," and the log answers "is the work from that decision actually moving."

What belongs in a decision register

A decision register works best when it captures the same fields every time, regardless of topic:

• The exact motion or resolution as voted on
• The date and meeting at which it was decided
• The vote tally, and who voted which way if your board records individual votes
• Any declared conflicts of interest tied to the vote
• A short note on rationale, so a future board member understands why, not just what

How formally you record votes, abstentions, and conflicts should follow your organization's bylaws — this isn't something a vendor should tell you how to do, so check with your governance counsel or your own policies before standardizing the format. What a platform can do is give the register a fixed, searchable home instead of letting it drift through whichever document happened to be open during the meeting. That's the role a dedicated governance record like Kahrbon's board meeting and minutes workspace plays — it keeps votes, dissent, and rationale attached to the meeting they came from instead of scattered across emails and shared drives.

What belongs in the action log instead

Once a decision is made, the real work usually isn't the vote — it's the five or six tasks that follow it: get a quote from the new vendor, update the insurance certificate, notify affected staff, schedule a follow-up review. None of that belongs in the permanent record of the decision itself. It belongs in a log where someone can see, at any point, who owns each item and whether it's overdue.

This is also where most boards quietly lose momentum. A decision gets made, enthusiasm is high in the room, and then the follow-up tasks live in someone's notebook until the next meeting, when half of them have slipped. An action-tracking view that's separate from the minutes — something closer to Kahrbon's Loop action tracker or a Kanban-style task board — makes it obvious which commitments are still open going into the next session, instead of relying on someone remembering to ask.

Keeping both without duplicating work

The two records don't have to live in separate systems to stay conceptually separate — they just need distinct structures and a link between them. A clean setup looks like this: the meeting is planned with a timed agenda so discussion doesn't run long, decisions and votes are captured in the permanent register during the meeting itself, and any resulting tasks are pushed into an action log the moment the vote closes, each one tagged back to the decision that created it. If you're already running board sessions with a structured agenda planner, that handoff from "decided" to "assigned" can happen in the same workflow instead of as a separate manual step afterward.

The test for whether you've got this right is simple: can a new board member, six months from now, find out what was decided and why without re-opening the debate, and can the board chair see which action items from that decision are still outstanding without scrolling through old minutes? If both answers are yes, the register and the log are doing their separate jobs.

Frequently Asked Questions

Should action items ever be deleted once they're complete?

Most boards are better served by marking action items as closed rather than deleting them, since a closed item still shows that a decision was followed through — which can matter later if anyone asks whether the board actually acted on something it voted for. Your record retention approach should follow your own bylaws or your auditor's guidance rather than a general rule.

Who should own updating the action log — the board chair, the secretary, or task owners themselves?

Practice varies by organization, but many boards have individual task owners update their own status and leave the secretary or chair responsible for reviewing the log before each meeting. What matters more than who updates it is that the log is checked at the start of every meeting, so open items don't quietly age out.

Does a decision register replace formal board minutes?

No — a decision register is usually a structured extract of the minutes, built to answer "what did we vote on and how" quickly. Formal minutes typically include more context, discussion summary, and attendance, and the format and required contents of your minutes should be set by your bylaws or legal counsel, not by a vendor.

Can a register of interests live in the same place as the decision register?

It often makes sense to, since conflicts of interest are usually declared in relation to a specific vote. Many boards link the two so that anyone reviewing a decision can also see which members declared an interest and whether they were recused from that vote.

What's a reasonable way to review old decisions before raising a similar proposal again?

A quick search of the decision register before a meeting — rather than relying on memory — is the simplest safeguard. If your board handles a high volume of recurring topics, keeping the register in a searchable tool rather than a stack of PDF minutes makes that check realistic to do every time instead of only when someone happens to remember.

If your board is still tracking votes, minutes, and follow-up tasks in the same running document, it's worth seeing what a separated setup looks like in practice. You can book a walkthrough or start a free trial to see how decisions and action items stay linked but distinct.