Leadership Meeting Notes: A Format That Records Decisions

Think of the notes as the team's memory of commitments. Capture:

• Decisions: the choice made, in one sentence, with the reason if it isn't obvious.
• Actions: a verb, an owner and a due date, written so the owner can act without asking anyone.
• Parked topics: what was raised but deferred, and when it returns.
• Scorecard exceptions: the red rows discussed and what was decided about each.
• Announcements: only items that change someone's work.

Leave out the debate, side conversations and background readers already know. If the reasoning behind a big decision matters later, add two lines under it: options considered and why this one won. That short record saves an hour of relitigating six months later.

Use this outline for every meeting so people know where to look:

1. Header: date, attendees, absentees and who took notes.
2. Scorecard: only the red rows and what was decided, with a link to the leadership team scorecard.
3. Decisions: numbered, one sentence each.
4. Actions: a short list of owner, task and due date.
5. Parked: topic, who raised it and the date it comes back.
6. Next meeting: the top three agenda items already known.

Number the decisions with the date, such as 2026-09-15-2. A stable label lets people reference a decision in chat and find it later with search.

Here's the shape of a good entry, using a made-up example:

Decision 3: We'll move customer onboarding from the sales team to delivery starting next month. Reason: sales handoffs were the most common cause of late kickoffs. Owner: VP of Delivery.

Action: Write the handoff checklist. Owner: Delivery lead. Due: Friday.

Action: Tell the three current accounts about the change. Owner: Account manager. Due: Wednesday.

Parked: Whether to hire a second onboarding specialist. Return: next month, once we see the first two onboardings.

Notice what's missing: no names of who argued which way, and no meeting chronology. A reader learns what changed and who does what by when.

Rotate the scribe weekly. A rotating scribe keeps one person from carrying the job, and it makes everyone practice stating decisions clearly. Two habits make the difference:

1. Read each decision aloud before moving on, so the room confirms the wording.
2. Assign every action an owner and date before the topic closes. An action with no owner in the room has no owner.

Circulate the notes within a day. Notes sent a week later are a history exercise. Ask owners to react or reply if their action is wrong, so errors surface early. Then, at the start of the next meeting, spend two minutes going through last week's actions before any new topic. Anything missed carries forward with a flag, and anything missed twice gets an explicit decision: do it, delay it or drop it. If the group finds itself spending too long in these meetings, the meeting reduction framework is a good next read.

Put them in one searchable place with one page per meeting and a running index of decisions. Notion suits teams that want a database of decisions with filters by owner and date, and Slite suits teams that want async notes with AI summaries. Confirm in a trial that search finds a decision by its keywords and that permissions keep sensitive topics restricted to leadership.

Don't scatter notes across personal documents. Keep one home, link it in the meeting invite, and archive by quarter. If you're moving from scattered files, migrating from Google Docs to Notion covers that path, and the company wiki structure shows where leadership notes fit in a broader knowledge base.