Matters arising, and nobody has done it
The education committee meets every quarter. At the last meeting, it agreed that a staff member would draft revised guidance on CPD for part-time members, a volunteer would contact two universities about accreditation, and the chair would raise a funding question with the board. These actions were written in the minutes, which were circulated three weeks later.
At the next meeting, matters arising reveals that the guidance was not drafted because the staff member thought it was waiting for board approval, the volunteer changed jobs and forgot, and the chair did raise the question but nobody recorded the answer. Meanwhile, the board is asking what happened to a decision the membership committee made a year ago, and nobody can find where it was recorded.
Why agreed actions drift
Actions are recorded in prose, in documents that nobody opens between meetings.
- Actions are buried in the minutes text rather than listed separately.
- Minutes are circulated weeks after the meeting.
- Owners are not reminded between meetings.
- Dependencies between committees are not tracked.
- Decisions are recorded in minutes but not in a searchable log.
- Volunteer owners have limited time and many other commitments.
The heart of the problem is that the minutes are a record of the meeting, not a tool for getting things done.
What drifting actions cost
Work agreed by council and committees is delayed by a quarter or more at a time. Volunteers become frustrated when meetings revisit the same items. Staff spend time chasing and searching minutes. When the board asks about a past decision, the answer depends on someone's memory.
For a membership body that relies on volunteer governance, meetings that achieve little discourage the members you most want to keep involved.
How we build the action and decisions log
- During or straight after the meeting, the secretary records each action with an owner, a due date and the agenda item, on a simple form alongside the draft minutes.
- Decisions are recorded as separate entries, with the committee, date, item and wording, and linked to the paper that supported them.
- Owners receive their actions by email the day after the meeting, not when the minutes are approved.
- Reminders go to owners before due dates, and owners can update progress or mark complete from the email.
- Actions that depend on another committee or the board are linked, so the dependency is visible to both.
- Before each meeting, the matters arising list is produced from the log, showing status and updates.
- The decisions log is searchable by committee, date and topic.
| Entry | What is recorded | Where it shows |
|---|---|---|
| Action | Owner, due date, item, status | Owner's reminders and matters arising |
| Decision | Wording, committee, date, supporting paper | Searchable decisions log |
| Dependency | Action awaiting another committee | Both committees' logs |
| Overdue action | Days overdue and last update | Secretary's dashboard |
The formal minutes are still written and approved as your governance requires. The log sits alongside them.
Between meetings afterwards
The day after the committee meets, every owner has their actions. The volunteer who is contacting universities gets a reminder two weeks before the due date and replies with a quick update. The staff member sees that the guidance is not waiting on the board, because the dependency is not there. The matters arising list for the next meeting is produced automatically.
When the board asks about a past decision, it is found in the log in seconds, with the paper that supported it.
Does this happen at your committees?
- Actions are only visible in the minutes.
- Matters arising reveals actions not done.
- Owners are not reminded between meetings.
- Past decisions are hard to find.
- The same items come back meeting after meeting.