How to separate meeting decisions from parking-lot topics

Meeting notes should separate decisions from parking-lot topics so readers know what changed and what is only waiting for another conversation.

A messy recap often mixes three things: decisions made, questions deferred, and ideas someone mentioned. When those appear in one list, people may treat an idea as approved or a deferred concern as forgotten. The result is rework, duplicate meetings, and arguments about what the team actually agreed to.

Use three sections. Decisions: what changed after the meeting, who owns the follow-up, and where the decision applies. Parking lot: topics worth returning to, with owner and review date if they matter. Notes: context that helps future readers but does not require action. This structure makes the recap useful for people who were absent.

A parking-lot topic should not be a graveyard. If the topic matters, give it a return path: next meeting, async thread, research owner, or explicit decision to drop it. If no one owns it and no date exists, label it as an idea rather than an open issue.

This separation is especially useful for cross-functional meetings. Engineering may hear risk, sales may hear customer promise, and operations may hear process change. The recap should show which of those became decisions.

A good rule: if someone could act on the line tomorrow, put it under decision or action. If no one should act yet, put it in parking lot or context.

How to separate meeting decisions from parking-lot topics

// COMMENTS

ON THIS PAGE