↓Skip to main content

Running remote and hybrid teams, one habit at a time

Meeting notes template, with filled-in examples for remote teams

Good meeting notes are not a transcript. Nobody rereads a transcript. They’re a short record of what was decided, who’s doing what, and what’s still open, written so that someone who missed the call can act on it in two minutes.

For remote teams this matters more than usual. Half your colleagues may be asleep during the meeting, and the notes are the meeting as far as they’re concerned.

The structure, top to bottom

Order matters. Put the parts people need first at the top, because most readers stop after a few lines.

  1. Header: meeting name, date, who attended, who wrote the notes.
  2. Decisions: numbered, one line each, in plain language.
  3. Actions: owner, task, due date. One owner per action, never “the team”.
  4. Open questions: things raised but not settled, with who will chase them.
  5. Discussion notes: short bullets under each agenda item, only if they add context a reader needs.
  6. Next meeting: date and anything that must be ready for it.

If you only fill in sections 2 and 3, the notes have done their job.

Filled-in example 1: weekly team meeting

Weekly ops sync, 18 November
Attended: Ana, Ben, Chidi, Dee (notes)   Absent: Eli

DECISIONS
1. Move the client reporting deadline from Monday to Tuesday from December.
2. New starters get laptop and accounts before day one, not on day one.

ACTIONS
- Ana: tell the three affected clients about the reporting change, by 22 Nov
- Ben: update the onboarding checklist with the laptop step, by 25 Nov
- Chidi: draft a December cover rota, by 29 Nov

OPEN
- Do we need weekend cover over the holidays? Dee to ask finance about overtime budget.

NOTES
Reporting: Monday deadline clashes with two clients' own month-end. Tuesday has no clashes.
Onboarding: last two starters lost most of day one waiting for access.

NEXT: 25 November. Chidi brings the rota draft.

Eli, who missed it, now knows the two changes and that nothing is waiting on them. That’s the test.

Filled-in example 2: one-to-one

One-to-one notes are usually shared only between the two people. Keep them in one running document, newest at the top, so patterns show up over months.

1:1 Sam / Priya, 19 November

PRIYA'S TOPICS
- Wants to lead the Q1 survey project. Agreed in principle.
- Late-evening calls with the US team three times last week.

SAM'S TOPICS
- Feedback on the board update: clear, but too long. Aim for one page.

ACTIONS
- Sam: confirm Priya as survey lead with the director, by 26 Nov
- Sam: move the Thursday US call 30 minutes earlier, by 21 Nov
- Priya: one-page version of the board update for December

CARRY OVER
- Training budget for next year (both to check figures)

Note what’s missing: no commentary on mood or performance beyond what was actually said. If notes could end up in a dispute, write only what both people would agree was said.

Filled-in example 3: project kickoff

Kickoffs produce more decisions than most meetings, so give each one a reason. Six months later, “why did we choose X?” is the most common question.

Kickoff: help centre rebuild, 20 November
Attended: Jo (lead), Kai, Lin, Mo (notes)

GOAL
New help centre live by end of February, replacing the old FAQ pages.

DECISIONS (with reasons)
1. Keep the current URL structure. Reason: avoids breaking links in old emails.
2. Launch in English first, other languages in phase 2. Reason: one writer available.
3. Jo signs off content; Kai signs off design. Reason: avoid committee review.

ACTIONS
- Lin: audit existing articles, mark keep/merge/delete, by 4 Dec
- Kai: two layout options, by 11 Dec
- Jo: weekly 20-minute check-in set up, by 22 Nov

RISKS
- Holiday period cuts available time in late December.

NEXT: 27 November check-in.

Habits that make notes useful

  • Write as you go. Notes written two hours later are half-remembered. Share them within the hour.
  • Rotate the note-taker. If the same person always takes notes, that person never fully joins the discussion. A rota fixes that.
  • Read decisions back. Spend the last two minutes reading decisions and actions aloud. It catches the “wait, I didn’t agree to that” moment while everyone is still there.
  • Post them where the work lives. The project channel or doc, not a private folder. Our async communication rules explain why written-first teams waste less time.
  • Link the agenda. If the meeting had an agenda (it should; see our virtual meeting etiquette rules), the notes can follow its headings.
  • Short meetings, shorter notes. A daily standup needs only blockers and owners, not minutes.

The blank template

[MEETING NAME], [DATE]
Attended:            Absent:            Notes by:

DECISIONS
1.
2.

ACTIONS (one owner each, with a date)
- [Name]: [task], by [date]
- [Name]: [task], by [date]

OPEN QUESTIONS (who is chasing?)
- 

NOTES (only what a reader needs for context)
[Agenda item 1]:
[Agenda item 2]:

NEXT MEETING: [date]. Bring: [what must be ready]