A meeting produces pages of notes, yet the team later disagrees about what was decided. A short decision note can preserve the outcome more clearly than a chronological account of every contribution.
Write the decision first
State the chosen option, the date and who had authority to decide. If the discussion produced only a recommendation, label it accordingly. Do not upgrade a tentative preference into approval.
Add the scope. “Use the shorter form for the pilot” is different from “replace the form everywhere”. That boundary matters when someone applies the note later.
Preserve the reason that mattered
Summarise the main criterion and any important limitation. An invented example might be: “The pilot uses the shorter form because the test concerns completion time; optional background questions remain outside this round.”
You do not need to attribute every passing comment. Keep sensitive or irrelevant personal details out of the record and follow the organisation’s information-handling rules.
Give the decision a next step
Identify the person implementing it and any condition that will trigger review. A decision can be definite for a pilot while remaining open to revision after evidence arrives.
Link the note from meeting actions or the relevant task record so it can be found. The useful test is whether a colleague can explain what was chosen, why and for which situation without asking someone to reconstruct the meeting.

