How to keep an event decision log
Someone says the committee agreed this last month, someone else remembers it differently, and the minutes are silent.
The short answer
An event decision log is a running table of the decisions that matter: what was decided, by whom, when, on what basis, and what depends on it. It also holds the decisions still open, each with an owner and a date.
Keep it separate from minutes. Minutes record a conversation; the log records outcomes, in one place, in a form you can search.
What belongs in the log
Log decisions that spend money, change scope, date, venue or programme, commit the organisation externally, or that others are waiting on. Routine tasks do not need an entry.
Open decisions belong too. A visible open decision with a due date is more useful than one that lives in someone's head.
The fields that earn their place
| Field | Why it matters |
|---|---|
| ID and date | So people can refer to it and see when it was made. |
| Decision | One sentence in plain words. |
| Owner (Decider) | The role with authority, matching your decision-rights matrix. |
| Options considered | Prevents the same alternatives being raised again. |
| Reason | Short note on why this option won. |
| Status | Undecided, decided, reversed or superseded. |
| Depends on / blocks | Which decisions or tasks wait on this one. |
| Due date | When an open decision must be closed. |
| Communicated to | Who was told, and when. |
Habits that keep it alive
- Update the log within one working day of any decision.
- Open every committee meeting by reading the open and overdue items.
- Treat Undecided as its own status: it is not a yes and not a no.
- When a decision changes, add a new row marked as superseding the old one. Do not delete the original.
- Share the current log with the committee before each meeting.
Where it goes wrong
- The log lives with one person who then leaves. Store it where the secretariat and chair can both open it.
- Too many entries, so nobody reads it.
- Decisions recorded without an owner, so no one can reopen them properly.
- Verbal decisions by senior members that are never logged.
Using a tool
A spreadsheet works. The decision log builder lays out the same fields and highlights overdue and blocking decisions. Whatever you use, test it by entering one undecided item and one reversed item to see that both show correctly.
Worked example · Fictional example
A fictional association's venue decision
Fictional organisation and figures. Dates and amounts are illustrative.
The fictional Malaysian Institute of Packaging Professionals logged its venue choice. The first entry recorded options A and B, the owner (conference chair) and a due date. It was marked Undecided for three weeks.
On approval, the row was updated to Decided with the reason, and a dependent task for the deposit was linked. When the committee later moved the date, a new row superseded the old one and the venue row was flagged for review.
| ID | Decision | Owner | Status | Due | Blocks |
|---|---|---|---|---|---|
| D-014 | Choose venue A or B | Conference chair | Decided | 15 Mar | Deposit, AV brief |
| D-015 | Move event date by one week | Committee | Decided | 2 Apr | D-014 review |
| D-016 | Set registration fee | Treasurer | Undecided | 20 Apr | Registration page |
Use this yourself
Event decision log template
Copy this table into a shared spreadsheet and add one row per decision.
- Log within one working day.
- Open decisions need an owner and a due date.
- Do not delete changed decisions. Mark them superseded.
| ID | Date | Decision | Owner | Options | Reason | Status | Due | Depends on or blocks | Told who |
|---|---|---|---|---|---|---|---|---|---|
| D-001 | Undecided / Decided / Reversed | ||||||||
| D-002 |
Handle it in-house, or bring in help?
Your team can usually handle this when
- The secretariat updates one shared sheet and the chair reads it.
- There are fewer than about 30 decisions in the cycle.
- Committee members attend meetings consistently.
Outside planning help earns its fee when
- Several committees or organisations decide on the same event and records conflict.
- Decisions are reopened regularly and nobody can show what was agreed.
- No one has the time to keep the log current and chase open items.
Want the log kept for you?
A conference project lead can set up the decision log, record decisions as they are made, chase open items by their due dates and bring blocking decisions to the committee early. Authority to decide stays with the roles named in your own rules.
Questions organisers ask
How is a decision log different from minutes?
Minutes record discussion. The log holds the outcome, owner and status in one searchable table.
Who should keep it?
Usually the secretariat or a project lead, with the chair confirming entries.
What if a decision is reversed?
Add a new entry that supersedes the old one, with the reason. Keep the original visible.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.