When Recommendations Go Nowhere

A committee does its work. Careful discussion. Different perspectives. The kind of preparation that makes governance meaningful.

By the end of the meeting, there is a clear recommendation. Well-reasoned. Properly minuted. Shared with the board ahead of the next meeting.

And then it waits.

Not because anyone is being careless. The board agenda is full. Timing does not align. Other matters take priority.

A month passes. A related issue comes up at board level — the same territory, slightly different framing. Someone vaguely remembers the committee's recommendation. Someone else thinks it was already covered. The chair is not sure whether it is still pending or was addressed informally somewhere.

So the ground is covered again. Not because the committee's work was forgotten — but because there is no structure that holds a recommendation between the meeting where it was made and the meeting where it needs to land.

Meanwhile, the committee does not know where their recommendation sits. Whether it has been seen. Whether it influenced anything.

Over time, that erodes something. Committee members start to wonder whether their work matters. Whether the recommendations they make are reaching the board with the weight they were given — or whether they are being absorbed quietly into the institutional background.

The problem is not intent. It is visibility.

Recommendations do not fail because people are careless. They fail because most governance structures treat a recommendation as the end of a process — when it is actually the beginning of the next one. It is minuted, shared, and then released. There is no live record of where it sits. No way to see whether it is pending, adopted, or quietly lost.

There is also a cost that compounds across the year. A committee that produces three recommendations per meeting, meeting four times a year, generates twelve items that need to land somewhere. Multiply that by the number of committees a board operates, and the volume of governance work moving through informal channels becomes significant. Without a tracking mechanism, the loss rate is not a question of if. It is a question of how much.

Some governance teams have started treating the recommendation differently. Not as a minute entry that gets filed — but as a tracked object with a status. Where it came from. What it is requesting. What the board has done with it. The committee can see it moving. The board can see what is pending. Nothing sits in a gap, rediscovered by accident, covered again from scratch.

Platforms like Loom structure this as part of the decision register. Committee recommendations sit alongside board decisions — visible, tracked, with a clear status that reflects where they are in the flow: pending, under consideration, adopted, or rejected.

Not buried in minutes. Not dependent on whoever happens to remember.

Because the work of a committee is only as valuable as its ability to reach the board. And for that to happen, it needs somewhere to live.