Board Action Register: How to Track Board Decisions and Actions

9 min read

Boards make decisions in the room and lose them in the weeks that follow. The action register is the instrument that prevents that. It is a live record of what the board decided, what must happen as a result, who owns it, when it is due and whether it is done — and it is almost always maintained by the board administrator rather than by the directors themselves.

Decisions and actions are not the same thing

Keeping the two distinct is the difference between a register that works and a spreadsheet nobody trusts.

  • A decision is what the board resolved. It lives permanently in the minutes and, in many organizations, in a separate decision register that is never closed off.
  • An action is work arising: something a named person must do by a named date. Actions are opened, worked and closed.
  • One decision can generate several actions, and some actions arise from discussion without any formal decision at all.

Our guide to writing board meeting minutes covers how decisions should be worded in the record itself; this article covers what happens to the work that follows them.

Capturing actions in the meeting

Actions captured after the meeting from memory or from a recording are always weaker than actions captured in the room. Three habits make capture reliable.

  1. Keep a running action column in your note-taking template, filled in as the discussion happens rather than at the end.
  2. Confirm each action aloud before the item closes: the wording, the owner and the date. Ambiguity resolved in the room is never resolved later.
  3. Read the full list back at the close of the meeting, so the board leaves agreeing on what was committed.

Write each action as an instruction with a verb and an observable end point. "Discuss the funding model" cannot be closed; "bring options for the funding model to the March meeting" can.

A sample board action register structure

A register can live in a spreadsheet, a governance platform or a board portal. The columns matter more than the tool.

  • Reference: a stable identifier, such as year and sequence, that never changes once assigned.
  • Meeting and date raised: which meeting the action came from.
  • Agenda item and minute reference: the link back to the record, so anyone can read the context.
  • Action: the instruction, in the wording agreed in the meeting.
  • Source: decision, discussion, committee recommendation or calendar obligation.
  • Owner: one named individual, not a team or a department.
  • Due date: a specific date, or a named meeting if the action is to report back.
  • Status: open, in progress, at risk, completed, deferred or closed as no longer required.
  • Update: the latest progress note, dated, in the owner's own words where possible.
  • Closure: date closed, closed by, and what evidence or outcome closed it.

Optional columns worth considering

  • Forum: board, or the specific committee, where a single register spans several bodies.
  • Confidentiality: so restricted actions can be filtered out of the reported extract.
  • Original due date: retained alongside the revised date, so repeated slippage is visible.

Owners and due dates

Two rules carry most of the discipline. Every action has exactly one owner, and the owner is a person who was present or who has been told directly. Shared ownership is the most common reason actions stall, because each holder reasonably assumes the other has it.

Every action also has a real date. "Ongoing" and "next meeting" are not dates; they are how registers accumulate items nobody intends to finish. Where an action genuinely recurs, it belongs in the governance calendar rather than the action register, and our annual governance calendar guide covers that distinction.

Status conventions

Keep the status list short and define each term in writing, so the same word means the same thing to every owner.

  • Open: agreed but not yet started.
  • In progress: work underway and expected to meet the due date.
  • At risk: work underway but the due date is unlikely to be met, with a reason recorded.
  • Completed: the work is done and the outcome is available to the board.
  • Deferred: the board or the chair has agreed a revised date, recorded with the original date retained.
  • Closed, no longer required: circumstances changed and the board has agreed the action lapses. This must be a board or chair decision, never an administrative one.

Running the register between meetings

The register is only useful if it is refreshed on a rhythm, not the night before the pack goes out.

  1. Within two working days of the meeting, update the register from the draft minutes and issue each owner their own items in writing.
  2. At the midpoint between meetings, request a status update from every owner with an open item.
  3. Two weeks before the next meeting, chase anything still outstanding and flag at-risk items to the chair.
  4. With the pack, publish the register extract as a standing agenda item.

Chasing is a service, not an imposition. Owners generally want to arrive at the meeting with their items closed, and a predictable reminder rhythm is what allows that.

Reporting to the board

Reporting the register badly wastes meeting time; reporting it well takes a few minutes. Publish the full extract in the pack for reading, and bring only the exceptions to the table: items at risk, items overdue, items proposed for deferral and items proposed for closure as no longer required. Completed items are noted as a block rather than narrated one by one.

A short summary line at the top of the extract — the number of items open, completed since the last meeting, overdue and at risk — gives the board an immediate sense of follow-through without reading every row.

Closing items properly

Closure is the step most registers handle loosely, and it is the step that determines whether the register can be relied on later.

  • Record what actually closed the item: a paper presented, an approval granted, a policy published, a report received.
  • Record who confirmed closure and the date, and where the closure is evidenced.
  • Have the board note closures rather than closing items administratively, particularly where the action arose from a formal decision.
  • Keep closed items in the register rather than deleting them. The history of what the board asked for and what followed is itself a governance record.

Common failure patterns

  • Actions worded as topics rather than instructions, so completion cannot be judged.
  • A register that only appears in the pack, never between meetings, so owners see it four times a year.
  • Long-outstanding items rolled forward silently, until the register loses credibility with the board.
  • Actions owned by a role that has since changed hands, with no reassignment.
  • Committee actions and board actions kept in unconnected lists, so escalations fall between them.

Tracking is the fourth discipline in the meeting cycle, sitting between recording decisions and maintaining the governance year. The Boardroom Ready flagship professional-development program and the Boardroom Ready Handbook teach it alongside preparation, assembly and record-keeping, and our resources library goes deeper on each.

Legal and regulatory requirements for boards differ by country, jurisdiction, sector and entity type, and your own governing documents may say something different again. Treat this article as practical guidance, not legal advice, and confirm the rules that apply to your organization.

Continue reading