Maintenance
Part of What documents does a single meeting actually need to produce?
Meeting documents format: block structure, header strip, and how to name the file so it sorts
Meeting document format: block structure instead of narrative, reference columns at the left edge, a header strip, table limits, and a file name that sorts by date.
Nobody reads meeting minutes end to end. They open them looking for one thing: a decision, an action, a date. Every formatting choice below exists to shorten that search, and most of them cost nothing.
Content is covered in the meeting documents overview. This page is about the page itself.
What to take away
- Block structure beats chronology. Decisions in one place, actions in another, everything else after.
- References go in the left margin where the eye scans, not inside the sentence.
- The file name is part of the format, and it is the part that decides whether the document is ever found again.
Blocks, not narrative
A record written in the order the conversation happened forces every reader to read all of it. A record written in blocks lets a reader go straight to the block they need.
Block order and why
Block
- Decisions
- First
- Actions
- Second
- Discussed, unresolved
- Third
- Noted
- Fourth
- Attendance and admin
- Last or header
Position
- Decisions
- Most searched, lasting weight
- Actions
- Worked from this week
- Discussed, unresolved
- Carried forward by someone
- Noted
- Read once, by few
- Attendance and admin
- Never why anyone opened it
Reason
- Decisions
- Actions
- Discussed, unresolved
- Noted
- Attendance and admin
The order that works, and why it is this order:
| Block | Position | Reason |
|---|---|---|
| Decisions | First | The most-searched content, and the only part with lasting weight |
| Actions | Second | The part someone has to work from this week |
| Discussed, unresolved | Third | Needed by people carrying an item forward |
| Noted | Fourth | Read once, by almost nobody |
| Attendance and admin | Last, or in a header strip | Necessary, never the reason anyone opened the file |
Putting attendance and apologies at the top is convention rather than design, and it pushes the decisions below the first screen. A one-line header strip does the same job in a tenth of the space.
Reference formatting
References belong at the left edge, in a fixed column, in a form that can be typed into a search box.
Scannable versus buried references
Do
- Position
- Left edge, fixed column
- Form
- Typed into a search box
- Continuation
- Indent to same column
- Owner and due
- Own line, fixed order
Don't
- Position
- Inside a sentence
- Form
- Parenthetical in prose
- Continuation
- Wrapped at random
- Owner and due
- Scattered in text
D-114 Approve the revised supplier onboarding route.
Effective [date]. Supersedes D-097.
D-115 Adopt [name] as the single reporting template
for all site meetings from [date].
A-238 Circulate the revised route to site leads.
Owner [name] Due [date]
A-239 Withdraw the old template from the shared folder.
Owner [name] Due [date]
Three formatting decisions do the work, and the reference sits alone at the left so a reader scanning down finds it without reading the text. Continuation lines indent to the same column, so the block reads as one item.
The owner and due date sit on their own line, in fixed order. An eye moving down a page of actions lands on the name every time.
Never bury a reference inside a sentence. "It was agreed (D-114) that the route would change" is unscannable, and it is how references stop being used.
Tables, and when not to use one
A table is right for actions when there are more than about six, and wrong when the action text is long enough to wrap. A four-column table where every cell wraps three times is harder to read than a list.
Table or indented block
Are there more than about six actions?
Use a table
Use an indented block
The practical rule: use a table when every cell is short and the columns are genuinely comparable. Use an indented block when one field is a sentence and the rest are labels.
If the record will be read on a phone, a table of more than three columns will need side-scrolling, which most readers will not do. The same constraint drives the layout advice in invoices and receipts format, where a wide table on a small screen loses the figure the reader came for.
Typography and space
- One heading level for blocks, one for items inside them. A record with four heading levels is a document that will not be maintained.
- Bold the decision or action text, or bold nothing. Bolding names or dates trains readers to skip the rest of the line.
- Leave a full blank line between items. Density costs more here than length does.
- Do not use color as the only distinction between a live and a completed action. Pair it with a word, which the federal notes on creating accessible documents treat as a baseline for anything sent outside the room.
- Keep line length short enough that a reader can return to the left edge without losing the line.
The header strip
Everything administrative in one compact block above the first decision.
Header strip fields
- 1Body and meeting name
- 1Date on the same line
- 3Present, chair, notes
- 2Quorum and status
[BODY] [Meeting name] [date]
Present [n] of [n] Chair [name] Notes [name]
Quorum [met / not required] Status [draft / approved]
Previous [reference or link] Next [date]
The status field is the one that gets left out and matters most. A draft circulating without the word draft on it becomes the record by default, and later corrections then look like revisions to an approved document.
The file itself
Name it so it sorts. Body, then date in year-month-day order, then document type. A folder of files named this way is chronological without any effort, and a file found on its own still identifies itself.
File naming and handling
- Namebody, then year-month-day, then type
- Send a fixed format for anything approved
- Keep agenda, papers and record in one folder
- Never edit an approved record in place
- Put corrections in the next record
Send a fixed format for anything approved. An editable file reflows on another machine, and the version someone prints is not the version you laid out. Where the record leaves the organization, the notes on creating accessible PDFs are worth ten minutes before you settle on a house style.
Keep agenda, papers, and record together. One folder per recurring meeting. A reader looking for context wants all three, and hunting across three locations is where people give up and ask someone instead.
Never edit an approved record in place. Corrections go in the next record as a correction. Otherwise the answer to "what did we decide" changes depending on when you look.
A layout pass before circulating
- Are the decisions on the first screen?
- Does every decision and action carry a reference at the left edge?
- Does every action show one owner and a real date in a fixed position?
- Is the word draft on it, if it is a draft?
- Does the file name identify the body and sort by date?
- Have you opened it once on a phone?
The material those checks protect is set out in meeting documents template, and the failures that layout alone cannot fix are collected in the notes on building a set from scratch in how to create meeting documents.
