What the Committee Actually Decided: A Plain-English Record Members Can Use

Associations rarely suffer from a shortage of committee activity. They suffer from a shortage of visible committee activity. Members see the newsletter, the annual report and perhaps the conference programme, but the ordinary work of deciding, prioritising and adjusting is often hidden in minutes that are technically available and practically unread.

A decision log is a modest remedy. It is not a new governance layer, a consultation exercise or a replacement for proper minutes. It is a short, plain-English record published after each committee meeting, giving members a clear view of what was decided, why it matters and how they can respond where a response is genuinely invited.

The habit can be captured in five lines. Done consistently, it builds more trust than another long update because it shows members how the association works, not merely what the association says afterwards.

Why visibility matters more than another bulletin

Most members do not want to read the full papers behind a committee meeting. They want to know whether a decision affects them, when it takes effect and whether their view can still make a difference. A decision log answers those questions directly.

This matters for trust. When members only see polished summaries, they may assume decisions are taken elsewhere by people they cannot identify. When they see a short record of the decision, the reasoning and the route for feedback, the committee becomes legible. Legibility is not the same as agreement, but it is a precondition for confidence.

The log also helps the committee itself. Writing five clear lines forces a meeting to end with clarity about what has actually been agreed, who owns the next step and what members will be told. Vague outcomes are harder to disguise in a short public record.

The five-line format

After each meeting, publish the same five fields in the same order. Consistency matters more than elaborate design.

1. Decision. State what was agreed in one sentence. Use plain English and avoid acronyms that only regular attendees understand.
2. Reason. Give the main rationale in one sentence. This is not a full debate record; it is the reason a member needs in order to make sense of the outcome.
3. Who it affects. Identify the relevant member groups, regions, sectors or committees. Be specific enough to be useful.
4. When it takes effect. Give a date or a clear trigger. If implementation depends on a later step, say so.
5. How and when to respond. Provide one route and one deadline where feedback is invited. If the decision is final and no response is sought, say that plainly rather than implying an open consultation.

Where a meeting produces several decisions, repeat the five-line block for each. Where it produces none, publish a short note saying so and give the date of the next meeting. Silence after a meeting is easily read as secrecy, even when nothing of substance has happened.

What belongs in the log, and what does not

The decision log is not a substitute for minutes. It should not record who said what, personal remarks, commercially sensitive detail or legally privileged advice. It should not become a diary of discussion. Its purpose is to make the outcome and its implications visible, not to replay the meeting.

For sensitive decisions, publish what can be published. It is usually possible to state that a decision has been taken, identify the area affected and explain when further information will be available. A consistent approach to confidentiality is more credible than an inconsistent one. Members understand that some matters cannot be disclosed in full; they are less understanding when disclosure appears arbitrary.

Use member-facing language. Replace internal shorthand with ordinary terms. Link to the relevant paper only where that paper is suitable for circulation. A short glossary of recurring committee terms can help, but the better solution is to avoid jargon in the first place.

Making the response route meaningful

A decision log should not create the impression that every decision is open for negotiation. That undermines both the committee and the members who take time to respond. State clearly whether feedback will inform implementation, shape a future review or simply be noted.

Use channels members already have. A short form in the member hub, a named email address or a standing item at regional meetings is usually sufficient. Set a realistic window, such as ten working days, and honour it. If no response is invited, say so and explain why. Clarity of this kind is not discouraging; it is respectful.

The log should also show what happened to previous feedback. A brief line in the next log or a quarterly summary can note that comments were received and how they were considered. This closes the loop without creating a separate engagement programme.

The discipline behind five lines

Assign an owner. In most associations, the committee secretary or chair is best placed to draft the log, with a quick check from the meeting chair before publication. Publish within five working days. Keep a simple archive in the member hub so that members can search past decisions rather than rely on memory or rumour.

Review the format quarterly. Are members using it? Are the response routes working? Are the lines still short? The log should not drift into a newsletter, a press release or a defensive explanation. Its value lies in brevity and consistency.

Common objections, answered briefly

Members may not read it. Some will not, but a short searchable record is more accessible than long minutes, and it gives those who do read it something accurate to share.

It may invite criticism. Criticism is usually preferable to rumour. A visible decision process makes it easier to correct misunderstanding and harder to sustain suspicion.

There is no time. Five lines after a meeting take less time than drafting a vague summary later. The discipline also reduces repeated queries because the answer is already published.

Some matters are confidential. Publish the decision at the appropriate level and explain when more will be known. Consistency is the safeguard.

A small habit with a visible effect

Trust in an association is built in ordinary months, not only at the annual conference. A decision log will not resolve every governance question, but it gives members a reliable way to see how committee work turns into action. Five lines after each meeting are enough to make the committee visible, the process legible and the invitation to respond honest.