Project & Development
Meeting Minutes and Reports: Documents People Read Within 30 Minutes
Intermediate | 1 whiteboard page · Task board: 5 columns (5 parent tasks, 13 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
The meeting minutes template for a new hire who has just been handed the minutes and is learning how to write them, opened right before the note-taking starts and again at the pre-send check. The whiteboard holds a 5W1H frame for the report, a grid showing how minutes, status reports, daily notes, and incident write-ups differ, the 30 minutes right after a meeting, a pre-send checklist with house style rules, and a running log of the corrections you get back. The task board runs Draft, Shaping, In review, Shared, and Into the template - five columns holding five parent tasks and 13 subtasks that all start untouched, from taking notes to updating your own template. Move one document as one card and feed every correction back into the template, and you stop guessing what a report should contain while the corrections per document fall month by month.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Meeting Minutes and Reports
How to use: 1. Frame it with 5W1H 2. Pick the document type 3. Draft in 30 minutes 4. Feed the corrections back into the template
1. Frame the Report (5W1H)
- Sales weekly minutes
- Who Readers are the sales manager and two absent colleagues from other teams
- What Two decisions and one action. The new plan slips to a September launch
- Why Three reasons - the build delay, a competitor price cut, and the August rush
- When Quote is due Tue, Aug 25, 5 p.m.
- Where Post in the sales weekly channel and file it on the shared drive
- How Conclusion, then reasons, then the ask - one page
2. Frames by Document Type (same material, different order)
| Minutes | Status report | Daily note | Incident report | |
|---|---|---|---|---|
| First three lines | Mon, Aug 24, 9:00-10:00, Room B Present 4 from sales / Absent 2 from other teams 2 decisions, 1 action (details below) | Proposing we move the new plan launch to September Three reasons (build delay, competitor price cut, August rush) Please decide by Fri, Aug 28 | Mon, Aug 24 - 30 calls, 2 meetings booked Hours 9:00-18:00 (2 hours of it in transit) Target was 1 meeting, so we are ahead | Fri, Aug 21, 10:12-10:48 - ordering was fully down Impact 217 orders failed (estimate, final count in review) Service is back up and still being watched |
| How the body runs | Item 1 - timing of the new plan launch Decision - launch moves to September (Diane, manager) Action - quote from Marcus by Tue, Aug 25 | Fact - July churn was 3.2% (from the CRM) Analysis - 60% of it is existing customers after the price increase Proposal - launch in September and hold current pricing | Done - 30 calls, 2 meetings booked (target was 1) Stuck - I cannot find the cost figures for the quote Priya, could I have 30 minutes with you tomorrow? | 10:12 alert fired / 10:20 failed over to the old server 10:48 service confirmed back up Cause - database connections hit the ceiling of 200 |
| How it closes | Action - quote | Marcus | Tue, Aug 25, 5 p.m. | PDF to the manager Next meeting Mon, Aug 31, 9:00, Room B Corrections to these minutes by Wed, Aug 26, noon | Decision needed - approve moving the launch to September Please reply by Fri, Aug 28, 5 p.m. Backing data - July figures (on the shared drive) | Tomorrow - 3 credit checks, 10 invoices to issue I am free from 2 to 4 p.m. Anything urgent can go in that window | Short term - alert threshold already lowered to 100 Permanent - raise the connection ceiling from 200 to 400 (Priya, Fri, Sep 4) Next update goes out Wed, Aug 26 |
3. The 30 Minutes from Meeting to Share (get it out while it is fresh)
- 1. In the meeting (0 min) Catch only decisions, actions, and numbers. Ask right there for any name you did not catch.
- 2. As it ends (+5 min) Before anyone stands up, read the decisions and actions back, and pin down owners and dates on the spot.
- 3. Frame it (+10 min) Put down the three headings, Decisions and Actions and Parked, then sort your notes under them. No prose yet.
- 4. Draft it (+20 min) One bullet per line under each heading. Stop at 70 percent and mark anything you doubt as [to confirm].
- 5. Share it (+30 min) Move it to the review column, clear the [to confirm] marks with your manager, then post it where it belongs.
4. Before You Send (conclusion and structure)
- The first line alone is enough to act on, and the conclusion is not below line three
- It is limited to decisions and actions, not a transcript of who said what
- Every action carries an owner, a due date, and what done looks like
- Minutes fit on one page and a daily note stays under ten lines
5. House Style for Names and Numbers (titles, companies, units)
- Outside contacts get Mr. or Ms. and a last name; inside, first names
- Use the legal company name, including Inc. or LLC where it applies
- Never write this week; write by Tue, Aug 25, 5 p.m. instead
- State whether an amount includes tax, and keep one unit throughout
6. Last Check Before Sending
- The To line and the CC line hold the right people
- No confidential attachment has been left on the message
- Every [to confirm] mark has been cleared
- People who missed the meeting can actually open the shared link
7. Log the Corrections and Update the Template (never get the same correction three times)
- Corrections this week - Used an internal acronym with no explanation -> spell it out on first use - Left out attendee job titles -> write the name and the title
- Corrections seen three times Shared with the team leaves the reader guessing who that is Change the recipients field in the template so it forces names
- Changes folded into the template Aug 14 - fixed the three headings Decisions, Actions, Parked Aug 21 - added owner, due date, and done to every action line
- This month's goal Keep corrections under five per document (week 1 of August was 12) Keep it under 30 minutes from the end of a meeting to sharing
Task board contents
Draft 18 items
Use a note template
Eight tenths of the document is settled during the meeting. Don't chase every word, just catch the three things you will need later.
Capture three things
Sit down with the template already open, headed Decisions, Actions, and Parked.
Ask for exact names
Spellings of names, the legal company name, what an acronym stands for - ask while the meeting is still running.
Sort into two lists
Decisions and actions are the only two things your readers hunt for. Let them blur together and nobody can tell who owes what.
Add owner and date
If it has no owner, no due date, and no description of done, don't write it down as an action.
Log why it is parked
In one line, write why it was not settled and what information would settle it.
Draft in 30 minutes
You are fastest while it is still fresh. A 70 percent draft sent the same day finishes sooner than a perfect one sent tomorrow.
Frame it in 10 min
Put the headings down first, drop each note under one, and finish all the reordering here.
Stop at 70 percent
Send it for review before you polish the wording, because wrong substance means a rewrite anyway.
Flag anything unsure
Leave any number or spelling you are unsure of marked as [to confirm] and send it anyway.
Get a manager review
Sending it is not the end. One document is finished only when you have worked through every correction.
Say when you need it
When you move the card to the review column, write down by when you need eyes on it.
Fix it the same day
Fix it while you still remember the meeting, because tomorrow you pay again just to recall it.
Check access and CC
Before you send, confirm the To line, the CC line, and who can actually open the shared link.
Update your template
Get the same correction three times and the problem is the template, not your habits.
Post edits on board
Add each correction you get back to the running log on the board, one line each.
Make repeats a field
Turn a correction you keep getting into a heading or a required field, so the template prevents it.
Count edits monthly
At month end, count the corrections per document and record whether the number is falling.
