What documents does a single meeting actually need to produce?

Meeting paperwork has one job that outlives the meeting: making it possible, months later, to find out what was decided and who was going to do something about it. Almost every complaint about meeting documents (too long, never read, written for nobody), comes from documents that were built to record the conversation instead.

Here are the questions people actually ask, with the formats that answer them.

What to take away

How many documents does a meeting need?

Three, and they are different objects with different lifespans.

The agenda exists before the meeting. Its job is to let people arrive prepared and to keep the meeting from expanding to fill the time.

The minutes exist after. Their job is to be a durable record of decisions.

The action list exists between meetings. Its job is to be worked from, which means it lives somewhere people already look, not buried at the end of a document they have to reopen.

Merging the second and third is the most common mistake. Actions buried in the narrative of minutes do not get done, because nobody re-reads minutes.

Where the meeting is a public or advisory body, what must be recorded and published is set externally, not by the chair. The US framework for advisory committee management shows how specific those obligations become.

What does a useful agenda look like?

<figure class="inline-figure">
  <img src="/inline/meeting-documents-fig2-1280.webp" alt="Checklist of agenda features including outcome column and decision questions (What documents does a single meeting actually need to produce?)" loading="lazy" decoding="async" />
  <figcaption>The outcome column and the question under each decision item do most of the work. <a href="https://companyformtemplates.com/image-licence">Image: Company Form Templates</a></figcaption>
</figure>
[MEETING NAME]
[Date]  [Time]  [Location / link]

Attending      [names]
Apologies      [names]
Chair          [name]
Notes          [name]

Papers attached: [list], please read before the meeting.

--------------------------------------------------------------
#  Item                          Lead    Time   We need to
--------------------------------------------------------------
1  [Item]                        [name]  [n]m   DECIDE
   Question: [the actual question to be answered]
   Paper: [reference]

2  [Item]                        [name]  [n]m   DISCUSS

3  [Item]                        [name]  [n]m   NOTE

4  Actions from last meeting     [chair] [n]m   REVIEW

5 Any other business: [n]m
   (raise items with the chair before the meeting)
--------------------------------------------------------------
Total: [n] minutes

Two features do most of the work.

The outcome column. Marking each item DECIDE, DISCUSS, or NOTE tells everyone what is expected of them. It also exposes the meeting's real shape: an agenda where every item is DISCUSS is a meeting that will not produce anything, and an agenda where everything is NOTE could have been an email.

The question under each decision item. Writing "Q3 budget" reserves time. Writing "Q3 budget: do we approve the additional headcount in support?" means people can arrive with a view. It also, quite often, reveals before the meeting that the question is not ready to be asked.

Time estimates are worth including even though they are always wrong. They force the total to be visible, and a total that exceeds the meeting length is a problem you can fix in advance rather than at minute fifty.

What should minutes actually contain?

Decisions, actions, and the reasoning behind anything contentious. Not a transcript.

[MEETING NAME]: MINUTES
[Date]  [Start / end time]  [Location]

Present        [names, with roles if the reader may not know them]
Apologies      [names]
Chair          [name]
Minutes by     [name]

DECISIONS
D-[ref]  [The decision, stated as what will happen]
 Context: [one or two lines, enough that a reader in
                     six months understands why]
         Options considered: [briefly, if there were any]
         Decided by: [consensus / vote result / the person
                      with the authority]
         Effective: [when]
         Dissent recorded: [name and position, if any]

ACTIONS
A-[ref]  [What will be done, as a verb phrase]
         Owner: [one name]      Due: [date]
         Reports back to: [meeting / person]

DISCUSSED, NO DECISION
[Item]   [What was raised, what is unresolved, what happens next
          and who is arranging it]

NOTED
[Item]   [One line]

NEXT MEETING
[Date, time, and any item already carried forward]

The separation between DECISIONS, ACTIONS and DISCUSSED is the whole design. A reader six months later scans one section and finds what they need. A reader looking through chronological narrative minutes has to read all of it and will still miss things.

Why give decisions reference numbers?

Because decisions get revisited, and without a reference the conversation goes "didn't we already decide this?" followed by twenty minutes of searching.

A stable reference, like a sequence or year-and-number, lets you write "supersedes D-114" when a decision changes, cite a decision in a project document, and answer "when was this agreed and by whom?" in seconds.

It costs nothing to add and is the single change that makes a set of minutes a usable record. A numbered decision only helps if the document follows a consistent quotes and estimates format readers can scan.

The same applies to actions. An action with a reference can be tracked across meetings without being retyped, and retyping is where owners and dates quietly mutate.

What should be left out of minutes?

If a discussion genuinely needs a fuller record (a sensitive matter, a decision that may be examined later), write it fully and deliberately, and understand that you are creating a document with a different circulation.

How do you write an action so it gets done?

Four fields, and all four are mandatory.

A monthly management meeting that reads the profit and loss form produces actions like any other. They need the same four fields. Take the action wording from the person who will do it, in the meeting, out loud.

The gap between what the chair thinks was agreed and what the owner heard closes in that one exchange and nowhere else.

Carry unfinished actions forward with their original date visible, not a refreshed one. An action that has slipped three times looks different from a new one, and it should.

Who approves the minutes, and when?

Circulate a draft while the meeting is still fresh (within a couple of days, not a week), and give a short window for corrections. Corrections at that stage are usually genuine errors of fact.

Approval at the following meeting is the usual formal step, and it is worth keeping for anything with governance weight. But do not let actions wait for approval: the action list goes out with the draft, because a two-week gap between agreeing something and telling people to start is the most common way meeting output evaporates.

Once minutes are approved, mark them as such and stop editing them. Later corrections go in the next set of minutes as a correction, not silently into the old file. Otherwise your record of what was decided changes depending on when you look at it.

Where should all this live?

Wherever your people already go. Meeting documents fail more often through storage than through drafting.

A few things that hold up:

What about recordings and automatic transcripts?

A recording is evidence of a conversation, not a record of decisions. It is searchable in a way that helps you settle a specific dispute, and useless for the ordinary question of what was agreed, because answering that requires reading a transcript, which nobody will.

If you record or use automated notes, two practical points remain. Someone still has to extract decisions and actions into a real record, and everyone in the room needs to know it is happening.

What you are permitted to record and how long you may keep it depends on where the participants are and what the meeting covers. Check with someone who knows the rules that apply to you before making it routine.

A short pass before you send

Agenda: does every item name an outcome and, where it is a decision, the question? Does the total time fit the meeting? Are the papers attached rather than promised?

Minutes: can someone who was not there tell what was decided? Does every action have one owner and a real date? Have you removed the narrative? Is anything in here you would not want forwarded?

Where a decision changes a written procedure, the update has to reach the procedure itself and not only these minutes, or the fix exists in a record and nowhere in the work. Anything circulated outside the organization needs the covering note that any business letter would carry.

Common questions