Rules
Part of What documents does a single meeting actually need to produce?
Fixing meeting documents after the first three meetings
Meeting documents need one review after three meetings, not a redesign after one. Six questions to ask of the record, and when to add a new document.
Do not redesign a recurring meeting's paperwork after one meeting. After three, the record shows what the template gets wrong, and six questions find it. The fixes are small, and most of them are subtractions.
What to take away
- Wait for three meetings before changing the template. One meeting shows you that meeting, and three show you a pattern.
- Read the record as someone who was absent, and ask six questions of it.
- Fix the template, not the people. A record nobody consults is usually too long, not ignored out of carelessness.
- Add a new document only when a specific thing breaks.
Why three meetings and not one
A first meeting is dominated by novelty. People are learning the agenda columns, the note-taker is learning the structure, and everything that goes wrong is blamed on the newness of it.
By the third meeting the novelty has gone. What remains is the real friction: the same item squeezed out of time, the same action with no date, the same paragraph nobody reads. That friction is what the template should be changed to remove, and the meeting documents overview describes what the finished set looks like.
The six questions to ask of the record
Lay the three records side by side and read them as a stranger would. Each question below has a likely cause behind a "no", and a place to fix it.
| Question | A "no" usually means | Where to fix it |
|---|---|---|
| Could someone absent tell what was decided? | Decisions are buried in narrative | The record's structure |
| Does every action have one owner and a real date? | Actions are living inside the minutes | The action register |
| Was anything discussed twice that was not on the agenda? | A recurring topic has no slot | The agenda |
| Did the time estimates bear any relation to reality? | Estimates were copied, not set | The agenda times |
| Is anything in the record you would not want forwarded? | Too much was written down | The record's scope |
| Did anyone consult the previous record between meetings? | The record is too long to use | Its length and layout |
A "no" on the last question deserves the most attention. It usually means the record is too long, not that people are careless, so the repair is to cut rather than to remind. The usual mistakes behind a record nobody reads are laid out in meeting documents mistakes.
When the review says the meeting itself is wrong
Sometimes no template change helps. Three meetings in a row with an empty decision block is data, and acting on it is more useful than improving the template.
A meeting with nothing to decide probably should not exist in its current form. If it informs rather than decides, a written update does the same job without the calendar slot.
Deciding or informing meeting?
Does this meeting decide or inform?
pre-reads and a decision log
written update, probably no meeting
Repairing the agenda
Two of the six questions point at the agenda. An off-agenda topic that surfaces twice has earned a place on it, with a lead and a time. A time estimate that never matches reality should be reset from what the last three meetings actually took.
Agenda template rules
- Columnsitem, lead, time, expected outcome
- No item without a named lead
- No decision item without a written question
- Set standing items last, not first
Resist the urge to add columns. Most agendas open with the items that never change and run out of time before the ones that matter, so the usual repair is to move the standing items to the end.
Repairing the record and its note-taker
If an absent reader cannot tell what was decided, look at the shape before the writer. Narrative notes hide decisions inside paragraphs, while a structured record keeps separate blocks for decisions, actions, unresolved items and noted items.
Structured record vs narrative notes
Structured record
- Shape
- Separate blocks
- Blocks
- Decisions, actions, unresolved, noted
- References
- On decisions and actions
- Result
- Usable record in 15 minutes
Narrative notes
- Shape
- Continuous prose
- Blocks
- None fixed
- References
- Rarely
- Result
- A diary
Then look at who writes. A note-taker who was never appointed is the most common cause of a poor record, because the most junior person ends up doing it while trying to contribute.
Say three things out loud
- Who writes the record
- They may interrupt to confirm wording
- The record goes out within a day
Rotating the role works if the structure is fixed. It fails when each person invents their own format, which the worked examples of different meeting types make easy to see.
Repairing the action register
If actions lack an owner or a date, the register is the fix, not the minutes. Keep actions in a register of their own, updated as things complete rather than at the next meeting.
Each line needs at least the action, one owner, a real date and its status. The figure below shows the full set of six.
Action register fields
- Reference
- Action as a verb phrase
- One owner
- Original due date
- Revised due date
- Status
Make reading the register the first agenda item every time. That single habit is what separates meetings that produce work from meetings that produce minutes. The fielded skeletons in the meeting documents template show how a register is laid out.
Checking where it all lives
The review is also the moment to check storage. Each recurring meeting should have one location holding agenda, papers and record together, with files named so they sort by date rather than by upload order.
Storage decisions on day one
- One location per recurring meeting
- Agenda, papers and record together
- Name files so they sort by date
- Decide who can see what
- Decide retention now
Check who can see what, particularly where a meeting occasionally handles personal or commercially sensitive material. Then settle retention. The National Archives guidance governs federal records, so for a company it is a model, not a rule.
Its principle is that each record series must be scheduled for appropriate disposition, and a recurring meeting's records are a series. The office also publishes guidance on records creation, management, and disposition. For the period itself, see the retention rules for meeting minutes and your own contracts and counsel.
Adding a document only when something breaks
Resist adding documents during the review for their own sake. Adding all of them at the start is the most reliable way to end up with none maintained, so wait for a specific failure.
- Two people ask whether something was already decidedadd a decision log.
- Items keep being deferred for lack of informationadd pre-reads.
- A formal body starts citing papers in its minutesadd cover sheets.
- Outside readers arrivetighten scope and wording, and read the record once as an outsider would.
Common questions
Who should chair, the accountable person or someone neutral?
Whoever can stop a discussion. If the accountable person cannot do that without it reading as suppression, use someone else and let the accountable person argue their case like everyone else.
How soon should the record go out?
Within a day. Corrections at that point are usually genuine errors of fact. A week later they are renegotiations.
Should we record the meeting?
A recording is evidence of a conversation, not a record of decisions, and someone still has to extract the decisions afterwards. Everyone present has to know it is happening, and what you may keep and for how long depends on where the participants are.
