A meeting can end with everyone remembering the same conversation and disagreeing about what it authorized. Someone heard enthusiasm for a proposal; someone else heard permission to proceed. Useful notes preserve that difference. The aim is to identify what was actually decided, what remains a proposal and what further answer is needed, so that an attractive idea does not acquire a budget, owner or deadline merely by being written under a heading called decisions.
Listen for the status of the statement
Consider three clearly hypothetical statements about an event invitation. The first is that a printed version could be attractive. The second is a suggestion to ask a printer for an estimate. The third is an explicit decision by the appropriate decision-maker to use a named option within an agreed limit. They concern the same invitation, but they do not establish the same next action.
The first belongs with ideas or discussion. The second can become an action to investigate, if someone has actually agreed to do it. The third may belong in the decision record, with its scope and conditions. Do not compress all three into a line saying printed invitations approved. Doing so loses the distinction between exploring an option, gathering information and committing to it.
Keep the approved scope narrow enough to be accurate
If the meeting agreed to obtain a quotation, record that as the action. It does not follow that the person obtaining it can place the order. If the group selected a design but left quantity unresolved, preserve that boundary. A decision can be real and still have conditions; the notes should not silently fill in the missing ones.
In the hypothetical invitation case, an accurate record might say that the team selected a design direction, that the coordinator will obtain a quote for the proposed quantity, and that purchasing remains subject to a named approver's response. Each part answers a different question. The coordinator can move the enquiry forward without being represented as having authority to spend money that was never approved.
Identify who could make the decision
A confident statement is not enough to establish authority. Use the organization's actual decision arrangements to determine whose agreement matters for the particular issue. If that is unclear, ask the meeting owner or appropriate person to resolve it. Do not use seniority, silence, a nod or the number of people present as a substitute for a decision process nobody has defined.
Atlassian's Confluence decision template offers a useful example of separating roles and status. Its DACI approach identifies a driver, approver, contributors and informed parties, and includes decision status and outcome. A team can use another system, but the underlying questions remain practical: who is moving this forward, who decides, and what has actually been decided? Filling in a template does not itself give someone authority their organization has not granted.
Preserve reasons without recreating the whole conversation
For a real decision, a short account of the selected option, relevant conditions and principal reason can make later review much easier. Keep alternatives identifiable where they explain the choice. Avoid turning a preference voiced during discussion into a formal reason unless it actually informed the decision. The notes should help another reader understand the outcome rather than simulate a transcript with an invented certainty at the end.
Suppose the team chose a simpler invitation because the more elaborate version could not be evaluated within its timetable. Record the timetable constraint if it was part of the decision. Do not add a claim that the simpler design is objectively better, cheaper or more sustainable unless the meeting actually established the relevant basis. A reason can be specific and modest without becoming a sweeping judgment.
Resolve a disputed note as a disputed note
When participants disagree about what the meeting decided, expose the disagreement and seek clarification through the appropriate route. Keep the unresolved status visible until an answer is obtained. Do not let a polished summary settle a substantive question merely because its author wrote first or used more decisive language.
Likewise, separate correction from a later change of mind. A corrected note should explain the actual meeting outcome accurately. A subsequent decision should be recorded as a subsequent decision, with its own scope, rather than rewritten as if everyone had agreed to it all along. That distinction helps the people doing the work understand which instruction currently applies and why.
Sources & further reading
Published sources for the details and examples discussed in this story.
