In short
Ask the organiser or note-taker for the notes, not the recording: decisions, action items with owners, and open questions. Check whether anything was assigned to you, reply with questions the same day, and ask for a transcript excerpt only where the exact words matter.
To catch up on a missed meeting, ask the organiser or the note-taker for the notes: what was decided, who is doing what by when, and what is still open. Check first whether anything was assigned to you, reply with your questions the same day, and ask for a transcript excerpt only where the exact words matter. The recording itself is rarely the fastest way to catch up, and it may not be yours to have.
This guide covers the steps, what a good catch-up note contains (for whoever writes one), and the etiquette of recordings when you were not in the room. Being able to skip a meeting and still keep track is also one of the ways to have fewer meetings without anyone losing the thread.
How to catch up on a meeting you missed
- Look for written notes first. Check the channel, wiki page or ticket where the team usually posts them. The answer may already be there.
- Find anything assigned to you. Search the notes for your name. An action item you do not know about is the costliest thing a missed meeting can leave behind.
- Ask a specific question. Message the organiser or note-taker: "Was anything decided about the launch date, and is anything waiting on me?"
- Ask for the notes, not the recording. Notes take minutes to read. A recording takes as long as the meeting.
- Ask for an excerpt where the words matter. If a precise commitment or quote matters, ask the person who recorded it for that part of the transcript, not the whole file.
- Reply the same day. Confirm the actions assigned to you, and raise any objection now. A decision you disagree with is easier to revisit today than next week.
- Tell the organiser you are caught up. One line saves them from chasing you.
What a good catch-up note contains
If you are the person writing notes for someone who missed a meeting, keep it short. A catch-up note is the meeting's notes, trimmed to what the reader needs:
**Catch-up: <meeting> — <date>**
**Decided:**
- <decision, and the reason in one line>
**For you:**
- <action, due date> — or "nothing assigned to you"
**Other actions:**
- <owner — action — date>
**Still open:**
- <question, and who is finding out>
**Detail:** <link to the full notes>
A worked example from a fictional team:
**Catch-up: Harbour pricing review — 24 September**
**Decided:**
- Northwind stays on the current plan until renewal; changing mid-contract was judged not worth the risk.
**For you (Marc):**
- Draft the renewal email by 1 October.
**Other actions:**
- Priya — update the pricing page copy — 29 September
**Still open:**
- Whether annual discounts apply to seat increases. Tom is checking with finance.
**Detail:** link to the full notes
The "For you" line is the most important. Write it even when the answer is "nothing assigned to you"; it tells the reader they have not missed anything they must act on.
Notes, transcript or recording
| What you get | Time to review | When it is the right thing |
|---|---|---|
| Notes | Minutes | Almost always. Decisions and actions are what you need |
| A transcript excerpt | A few minutes | When the exact words matter: a commitment, a quote, a number |
| The full transcript | Longer | When you need to understand a long discussion and search helps |
| The recording | As long as the meeting | Rarely; when tone matters, and the people recorded would expect it |
Ask for text rather than audio. The people in the meeting agreed to be recorded for a purpose, usually so notes could be written. Passing the audio to people who were not there may go beyond what they expected. A person who recorded a meeting should share text they have read and checked, not raw audio, unless there is a specific reason and the people recorded would expect it.
A recording should never be a surprise. If you learn that a meeting you missed was recorded, the people in it should have known at the time. If they did not, that is a problem to raise, not a resource to use. How to ask for consent to record covers how it should have been announced.
When you missed it on purpose
Many teams now expect people to skip meetings where they only need the outcome. That works when:
- You say so in advance. "I'll skip this one and read the notes" lets the organiser make sure notes are written.
- Notes are written every time. A meeting people may skip needs a record, or skipping means missing decisions.
- Questions go in before the meeting. If you have a view on an agenda item, post it beforehand so it is in the room without you.
Recurring status meetings are often better replaced entirely; async status updates covers that.
If you took the notes with Notey
If you recorded the meeting with Notey, having told the people in it, the transcript and notes are on your Mac. Notey has no sharing feature and no team workspace: to send a catch-up, you copy or export the text and paste it where your team works. The summary, any note, or everything export as Markdown; the transcript on its own exports as plain text. AI-written notes keep their AI-generated label when exported, so read them against the transcript before you send them. The audio stays on your disk.
Sharing meeting notes with a team covers where to post notes, and exporting meeting notes covers getting them out of a notes tool.
Frequently asked questions
How do I find out what I missed in a meeting?
Ask the organiser or whoever took notes for the decisions, the action items and the open questions. If there are written notes, read those first; then ask about anything they do not cover.
Should I ask for the meeting recording?
Usually ask for the notes instead. A recording takes as long to review as the meeting, and the people in it agreed to be recorded for the meeting's purposes, which may not include passing the audio around.
What should a catch-up note include?
What was decided, who is doing what by when (especially anything assigned to the person who missed it), what is still open, and where to find more detail. A few lines is usually enough.
How do I ask a colleague what I missed in a meeting?
Be specific. "Was anything decided about the launch date, and is anything waiting on me?" gets a faster, more useful answer than "What did I miss?"
Is it rude to skip a meeting and read the notes?
Not if you say so in advance, and the organiser knows you will read the notes. Many teams encourage it for meetings where someone only needs the outcome.