Why resolutions stall after the vote
A board can approve a resolution in five minutes and then spend six months wondering who was supposed to act on it. The vote feels like the finish line, but the resolution is only a decision; the work starts when the meeting ends. Most trackers fail because they record the motion and omit the owner, the evidence, and the date the board expects to see progress. The support desk should treat the minute as the start of a small project.
Stalling is rarely deliberate. The executive who sponsored the paper moves to the next agenda item, the committee assumes someone else is managing the follow-up, and the resolution disappears into a folder of approved minutes. By the next meeting, nobody can say whether the action happened or whether the board changed its mind. A single register with named owners prevents that amnesia.
The register should be owned by the support desk but reviewed with the board secretary. The desk keeps the format and chases updates, while the secretary confirms that the wording matches the minute. That division keeps the record accurate without making the desk the author of a board decision. A short monthly check is enough to catch drift.
Record the decision in minutable language
Write each resolution as a short statement with a verb, an object, and a boundary. Approving a revised travel policy for implementation by the operations committee is minutable, while discussing travel is not. Include the date of the vote and the meeting where it occurred so a later reader can trace the source. The wording should be copied from the approved minute rather than paraphrased from memory.
If the board approved a range or a condition, record the condition next to the resolution. A budget approval capped at a figure, for example, should carry that cap into the register and into any purchase request that follows. The desk should not widen an approval by summarizing it loosely. Precision here saves an awkward correction later.
Assign one owner and one due date
A resolution can involve several teams, but it should have one accountable owner. That person may delegate the work, yet they remain responsible for reporting status to the board. Record the role rather than only the name so the register survives a departure. If the owner changes, update the entry instead of creating a second row.
Set a due date that reflects the board's next review point, not an optimistic guess. Some resolutions need a ninety-day report, while others need a single completion note before the next meeting. The desk should confirm the date with the owner and mark it as agreed. A date nobody owns is just a wish.
Separate evidence from assurances
Status updates often say a project is on track without showing what changed. The register should ask for one piece of evidence, such as a signed policy, a purchase order, or a dated report. The evidence does not need to be elaborate; it needs to be checkable by someone who was not in the room. That standard keeps the board conversation grounded.
When evidence is not yet available, record the next checkpoint and what will be produced. Do not mark a resolution complete because the owner feels confident. A short note explaining the gap is more useful than a green label with nothing behind it. The desk can then give the board an honest view of progress.
Review open resolutions before each board cycle
The support desk should review the register before the agenda is finalised, not after the packet is sent. Identify resolutions that are due, overdue, or waiting on a board decision. Ask each owner for a one-line update and the evidence that supports it. This rhythm keeps the board from rediscovering old commitments during the meeting.
Include a short resolution status page in the packet when there are material changes. The page should show the original ask, the owner, the due date, and the current evidence. Directors can then spend their time on exceptions rather than on a recital of routine progress. A consistent format trains owners to prepare.
Close resolutions with a short evidence note
Closing a resolution should take one paragraph, not a ceremony. State what was done, when it was completed, and where the evidence is stored. Link to the document rather than attaching a duplicate that will drift out of date. The note should be written for a director who joined after the vote.
If the resolution was superseded or withdrawn, record that outcome with the same care. A closed door is a legitimate result, and leaving it open in the register creates false work. The board should see the change and the reason. The desk should never quietly delete an item to make the list look clean.
Keep the register readable between cycles
Use a small number of fields and keep the current view short. A register with thirty columns will be updated by nobody, while a six-column table can survive a busy quarter. Archive closed items to a separate view so the active list stays legible. The goal is a working register, not a memorial to every motion.
Review the format once a year with the board secretary and the chair. Ask which fields were used and which were ignored. For related guidance, see our article on creating a board paper review checklist and our executive support services. The GAO Green Book describes documentation and monitoring practices that support this kind of follow-through.
Key takeaways
- Copy the approved minute wording and attach the vote date so the resolution stays traceable.
- Give every resolution one accountable role and one agreed due date tied to a review point.
- Ask for one piece of checkable evidence instead of a general assurance.
- Review open resolutions before the packet is sent, and show exceptions rather than routine progress.
- Keep the register short, archive closed items, and review the fields once a year.