Module 4 of StartCloud's Microsoft 365: Everyday Skills learning pathway, in five short units with a knowledge check: why four lines of agenda in the invite changes the meeting, where Teams recordings and transcripts are stored and therefore who can watch them later (the organiser's OneDrive for normal meetings, the team's SharePoint site for channel meetings), how to write notes and actions that survive the hour, and four honest questions for working out when a meeting should have been a message.
Meetings Worth Attending
An agenda in the invite
Look at your calendar for tomorrow. Most invites contain a title, a time, and a join link. That is a request for an hour of somebody's working life with no explanation of what the hour is for, which is why so many meetings spend the first ten minutes working out why they are happening.
The fix is three or four lines typed into the invite before you send it. Not a formal agenda with roman numerals. Just enough for someone to know what they are walking into and whether they are needed.
Why we are meeting. One sentence. Not the topic, the reason. "The Kwinana quote is due Friday and we cannot agree on the scope" tells people far more than "Kwinana catch-up".
What we need to decide or produce. Name the thing that has to exist by the end. A decision, a number, a draft, a plan for the week. If you cannot name one, that is worth noticing before you send the invite, not after.
What to look at first. Link the document, the quote, the dashboard. Two minutes of reading beforehand saves ten minutes of catching everyone up while four people wait.
Who is running it. Usually you, and saying so is not bossy. It just means somebody has agreed to keep the thing moving and call time at the end.
- People arrive having thought about it, instead of thinking out loud
- Anyone who is not needed can say so, politely and early
- You know when the meeting is finished, because you named the finish
- The half hour that would have been forty-five minutes stays a half hour
- Everyone turns up cold and the first ten minutes are recap
- Nobody can tell whether they are essential or decorative
- The conversation wanders, because there is nothing to wander from
- It ends because the hour ended, not because anything was settled
Teams meetings can carry a shared set of notes that you add to the invite before the day. Everyone can type in it at once, and it holds the agenda, the notes and the follow-up tasks in the same place. Start it a day early with your four lines in it, and by the time the meeting begins, half the thinking has already happened. We come back to this in unit three.
Recording a meeting is now one button, so people press it without thinking much about it. Worth thinking about, because a recording and its transcript are files, and files live somewhere with permissions attached. Where they land, and therefore who can watch them months later, depends on how the meeting was set up.
There are two cases, and the difference between them surprises almost everyone.
Anything scheduled in a calendar, plus one to one and group calls. The recording and transcript go into somebody's personal OneDrive, in a Recordings folder.
- For a scheduled meeting it is the organiser's OneDrive, even if someone else pressed record, and even if the organiser never showed up
- For a spur of the moment call it is the OneDrive of whoever pressed record
- People from your business who were invited get a link automatically, usually view only
- Anyone outside the business gets nothing unless the owner shares it deliberately
Schedule the meeting in a Teams channel and the recording goes to the team's SharePoint site instead, in a Recordings folder alongside the team's other files.
- Permissions come from the channel, not from the guest list of the meeting
- Everyone with access to that channel can watch it, including people who were never in the room
- That is genuinely handy for a team update people should be able to catch up on
- It is the wrong place for a difficult conversation about one person's work
A transcript is a written, searchable record of who said what, and it is stored in the same place with the same permissions as the recording. Most people are relaxed about being filmed and much less relaxed about a word for word account of their thinking out loud. Worth remembering before you turn it on for a conversation that needs people to be candid.
Recordings and transcripts are set to expire by default. Microsoft's out of the box setting deletes them after 120 days, and your business can lengthen it, shorten it or switch it off entirely. When one expires it goes to the recycle bin. If something in a meeting genuinely matters, write it down. Do not rely on being able to rewatch it next year.
Teams announces that recording has started, and some businesses require people to agree before they can speak or share. That is the legal minimum, not the courteous one. Saying "I am going to record this so Priya can catch up, sing out if you would rather I did not" costs five seconds and keeps everyone comfortable.
Would everyone here still speak freely if they knew this could be watched, months from now, by people who were not invited? For a project update the answer is usually yes and recording is a gift to whoever is on leave. For a performance chat, a difficult client call, or anything where someone needs to be able to think out loud and be wrong, the answer is no. Take notes instead.
You know the meeting where everyone nodded, it felt productive, and three weeks later nothing has moved and two people remember it differently. That is not a memory problem. It is a nobody wrote it down problem, and it is the cheapest thing on this whole list to fix.
One person types, and everyone can see it happening
Teams meetings can hold a shared set of notes that everyone edits at the same time, and it is designed to carry three things: the agenda, the notes, and the follow-up tasks. When it is up on screen, people watch their own action being written down, which is a remarkably effective way to stop the quiet disagreements that surface a fortnight later.
- Add it to the invite before the day, with the agenda already in it
- Anyone can fix a line they know is wrong, live, rather than emailing later
- Tasks you assign in there follow the person into their own task list
Write decisions and actions, not a transcript
Nobody reads a wall of text describing everything that was said, and you already have a recording if you truly need the play by play. What people come back for is short: what did we decide, what changed, and who is doing what. Six useful lines beat two pages every time.
- Decisions, in plain words, including the ones that were only implied
- Anything that changed since last time
- Actions, and nothing else pretending to be an action
Every action gets a name and a date
"We should look into that" is not an action, it is a feeling. An action has a person and a day attached, and if nobody will put their name to it, that is useful information right there. Read the actions out in the last two minutes, out loud, and watch how quickly one of them gets renegotiated on the spot.
- A person, not a team or a department
- A date, even a rough one, because someday means never
- Read them aloud at the end while everyone is still there
Notes that stay inside the meeting are only ever found by people who remember the meeting existed. Post the decisions and actions into the channel the work belongs to, in a short message anyone can scroll back to. That is the same habit from the last module: things the team needs later belong to the team, not to a calendar entry from March.
Under the covers, those live notes are a file that belongs to whoever started them, sitting in their OneDrive. Usually that is invisible and everything works. Occasionally it means someone gets an unexpected access message, or a meeting booked by a room or a shared mailbox behaves oddly. If a set of notes matters beyond the hour, copy the decisions into the channel as well. Ten seconds of duplication beats an awkward hunt in six months.
Time for the honest one. Every business has a set of meetings that exist because they have always existed, and everybody privately knows it. Nobody wants to be the person who says so, so the invite goes out again, and again.
You do not need permission to think about this, only four questions, asked before you send the invite.
Am I just telling people something? Then it is a channel post, and everyone can read it in the ninety seconds it takes rather than the half hour you were about to book. If it needs showing rather than telling, record a two minute walkthrough of your screen and post that.
Am I collecting updates one at a time? Six people taking turns while five listen is five sixths waste. Ask for updates in the channel and read them. Meet when the updates disagree with each other, which is the only interesting part anyway.
Could this be a document with comments? Reviewing a draft together, line by line, on a screen share, is a slow way to do something everyone could do properly in their own time. Share the document, ask for comments by Thursday, and meet only about the parts people disagreed on.
Is there a real decision, with real disagreement? Then meet, and meet properly. Anything with tension, bad news, or a genuine choice between options deserves faces and voices. This is what meetings are actually good at, and it is why the pointless ones are such a shame.
An hour is a default, not a measurement. Most conversations that get an hour would have finished in twenty five minutes with an agenda and someone keeping time. Try booking half of what you would normally book. If you genuinely run out of time, that is easy to fix, and it almost never happens.
"Happy to skip this one if you just need the numbers, I will send them across beforehand and read the notes" is a completely reasonable thing to send your manager. Most organisers invite widely out of politeness, not necessity, and quietly appreciate someone saying it first.
A recurring meeting nobody has prepared for in two months is a standing appointment with a habit. Cancelling it is not a criticism of anyone. Say what it was for, say it is done, and offer to bring it back if the work picks up again. People will be relieved, and at least one of them will say so.
It is about the ones you keep being worth the time. A meeting with a reason in the invite, a person keeping it moving, notes that get written while people are still in the room, and actions with names on them is a genuinely good use of an hour. The rest were always a message, and now you have four questions and a polite way to say so.
- Microsoft Learn: Teams meeting recording and transcript storage and permissions in OneDrive and SharePoint
- Microsoft Learn: Manage Teams recording expiration policy
- Microsoft Learn: Overview: recording and transcription for Teams meetings, events and calls
- Microsoft Learn: Overview of Loop components in the Microsoft 365 ecosystem
- Microsoft Learn: Overview of Teams and SharePoint integration
All of this was current at the time of writing (August 2026). Storage rules and the default expiry for recordings can be changed by whoever administers your Microsoft 365, and Teams renames its buttons often, so check with your IT people or the links above if something looks different on your screen.
Knowledge check
5 quick questions. Get 4 right and the module is yours.
1. You scheduled a Teams meeting from your calendar. A colleague pressed record. Where does the recording end up?
2. You schedule the weekly update as a channel meeting and record it. Who can watch the recording later?
3. Your manager says the important bit is in a Teams recording from a year ago. What should you expect?
4. Which of these is a real action item from a meeting?
5. You are about to book an hour to walk six people through a new process. What is the better move?