Worked meeting documents, each built around a different kind of meeting

The skeletons in the meeting documents overview fit a formal recurring meeting. Most meetings are not that. What follows is the same material bent to five real meeting types, with a note on what changes and why. Every name, figure, and reference below is a placeholder in square brackets.

The useful comparison is not between good and bad examples. It is between the same document written for two different meetings, because that is where you see which fields are load-bearing.

What to take away

Example 1: the weekly team meeting

The failure mode here is minutes that read like a diary. Nobody re-reads them, so anything recorded only there is lost.

[TEAM] WEEKLY                              [date]
Present [names]      Absent [names]

CARRIED FROM LAST WEEK
A-[ref]  [action]           [owner]  due [date]   [status]
A-[ref]  [action]           [owner]  due [date]   OVERDUE 2 weeks

DECIDED
D-[ref]  [decision, one line]        effective [date]

AGREED TO DO
A-[ref]  [action]      [owner]   due [date]

RAISED, NOT RESOLVED
[item]   [who is taking it away, and to where]

NOT DISCUSSED
[items carried to next week]

What changes from the formal template: no reasoning, no attendance apologies, no approval step. What stays: references on decisions and actions, one owner, a real date. The "not discussed" line is unusual and worth keeping, because a team meeting that never records what it dropped will drop the same item eight weeks running.

Example 2: the project status meeting

The trap is a status meeting that produces a status report instead of decisions. The document should make that visible.

[PROJECT] STATUS                           [date]  Week [n]

DECISIONS NEEDED TODAY
  [question]                        [who must decide]
  [question]                        [who must decide]

DECIDED
D-[ref]  [decision]     effective [date]

BLOCKED
  [item]   blocked by [what]   [owner of unblocking]  since [date]

SLIPPED SINCE LAST WEEK
  [milestone]   was [date]   now [date]   because [one line]

ACTIONS
A-[ref]  [action]   [owner]   due [date]

Putting decisions needed at the top, before status, changes the meeting. A project meeting with an empty first block for three weeks running is a meeting that could be a written update.

The "slipped since last week" block is the one people resist and the one that makes the record honest. A date that moves twice without a stated reason is the earliest visible sign of a project in trouble.

Example 3: the client or supplier review

Two organizations, so the document leaves your building. Everything about it changes.

[YOUR NAME] and [CLIENT NAME]: REVIEW      [date]
Attending  [names and organizations]

AGREED TODAY
  [what both sides agreed, in words both would use]

ACTIONS
  [action]     [owner, with organization]   by [date]

RAISED BY [CLIENT]
  [item]    [your response, or "to come back by (date)"]

RAISED BY US
  [item]    [their response]

NOT AGREED
  [item]    [where each side stands, plainly and without comment]

NEXT   [date]

Field notes. Attribute by organization, not by person. A named individual reading their own opinion in a circulated note makes the next meeting cautious.

The "not agreed" section stops a disagreement from being quietly recorded as resolved. Send it within a day. Write the covering message like any other business letter: what is attached, what you need back, and by when.

Where the review touches money already invoiced, keep the wording consistent with what appears on the invoice, because two documents describing the same amount differently is how a query becomes a dispute.

Example 4: the decision meeting with a vote

Where a body votes, the record has one job: to be unarguable afterwards.

[BODY]: MINUTE OF DECISION                 [date]
Quorum required [n]      Present [n]      Quorum met [yes/no]

D-[ref]  MOTION
  [The motion, as put, word for word.]
  Proposed by [name]   Seconded by [name]
  For [n]   Against [n]   Abstained [n]
  Carried / not carried
  Effective [date or trigger]
  Recorded objection: [name and position, if requested]
  Supersedes: [D-ref, or none]

Field notes. Enter the motion as put, not summarized, because the summary is what gets disputed. Record quorum before the vote, since a decision taken without one may be void.

Enter a recorded objection only when the person asks for it, and refusing that request is not the chair's call. Public bodies operate under specific rules here, and the US framework for advisory committee management shows how detailed those obligations become when meetings are open.

Example 5: the incident or post-mortem review

The only meeting type where the reasoning matters more than the decision.

[INCIDENT REF]: REVIEW                     [date]
Present [names and roles]

WHAT HAPPENED
  [Timeline, times and events only, no judgment.]

WHAT WE BELIEVE CAUSED IT
  [Findings, each marked confirmed or suspected.]

WHAT WE ARE NOT SURE ABOUT
  [Open questions, with who is answering them.]

CHANGES AGREED
A-[ref]  [change]   [owner]   due [date]   [what it prevents]

CHANGES CONSIDERED AND REJECTED
  [change]   [why not]

Two features matter: marking findings as confirmed or suspected stops a guess from hardening into an accepted cause over the following months. Recording rejected changes stops the same suggestion from arriving at every subsequent review.

Where a change lands on a written procedure, put the update in the SOP templates document itself, not this note alone. Otherwise the fix exists in minutes and nowhere else.

What all five have in common

Every example above separates decisions, actions, and unresolved items, and each references the first two, a separation that is the only structural feature surviving across meeting types.

Keep it if you keep nothing else; plain wording carries the rest. The federal plain language guidelines on writing for your audience treat it as the first decision, not a polish step.

Common questions