Everything you need in an informal meeting notes template: decisions, actions, follow-ups, and who else needs to know.
Tassia O'Callaghan
Informal meetings produce more decisions than people tend to realize. A catch-up over coffee, a five-minute corridor conversation, a quick brainstorm before a bigger meeting: each of these can shift a deadline, move a responsibility, or establish an expectation. The problem is that none of it gets written down, and two weeks later each person has a slightly different version of what was agreed.
According to the 2026 Fyxer Admin Burden Index, employees lose 5.6 hours per week to admin that could be handled by AI; and meeting notes are a significant slice of that.
This template is designed for those situations. It's intentionally lightweight: enough to capture what actually matters without turning every casual conversation into a documentation exercise.
Below you'll find the template itself, followed by guidance on using it without adding friction, handling specific formats like brainstorms and ad hoc conversations, and building a consistent informal meeting notes habit across your workday.
Informal meeting notes template to copy and edit
Most informal meetings don't need a formal record. They need a consistent one. This template is intentionally brief: it covers the things that actually matter (decisions, actions, and who else needs to know) without turning every casual conversation into a documentation exercise. Copy it, adapt it to fit how you work, and use it as a starting point rather than a script.
Participants:Meeting type: [Catch-up / Brainstorm / Ad hoc / Working session / Other]What prompted this meeting / context:[A few sentences or brief bullets on the main areas discussed. Doesn't need to be exhaustive.][Decision — be specific enough to remove ambiguity][Action] — [Owner] — [By when, if agreed][Topic or question that needs a further conversation or a decision][Anyone who wasn't in this conversation but should be aware of what was discussed or decided][Date / 'Sent as follow-up email']
Two sections in this template do the heaviest lifting. The 'decisions made' section is the most important: be precise. Not 'we agreed to review the proposal' but 'Sarah will review the draft proposal and send comments by Friday.' The 'who else needs to know' section is the one most people forget.
Vague decisions are the ones that get recalled differently later. The 'who else needs to know' section is the one most people forget. Informal conversations often have downstream effects on people who weren't in the room, and a note of who needs to be looped in prevents that from becoming a problem.
How to use an informal meeting notes template without making every chat feel like a process
The risk with any template is that it starts to feel like overhead, especially in contexts where people want to keep things light. The simplest way to avoid this is to write the notes after the conversation rather than during it. Be present in the meeting. Then take five minutes at your desk afterward to capture what came out of it.
This is a better approach for most informal meetings anyway. Note-taking during a casual catch-up can feel odd, and it splits your attention in a way that affects the quality of the conversation. Notes written immediately afterward, while the conversation is still fresh, are usually more accurate than notes taken in real time while also trying to listen and respond.
Paper works fine if that's your preference. A photo of a handwritten note sent to the other person immediately afterward achieves the same thing as a typed record. The habit matters more than the format.
When a follow-up email works better than a structured note
For a lot of one-to-one informal meetings, a brief follow-up message is a more natural way to create a record than a structured document. It's conversational, it arrives in the other person's inbox, and it implicitly invites them to correct anything you've got wrong.
Something along the lines of: ‘Good to catch up. To confirm, you’ll send over the revised scope by Thursday and I’ll arrange the intro call for next week.’ That’s not formally a meeting record, but it functions as one. Both people have seen it, and both can push back if their recollection is different. Our guide on writing follow-up emails that get a response has templates you can adapt for this.
If writing follow-up emails after every informal meeting is eating into your day, Fyxer drafts them automatically using context from your calendar and inbox; a useful option if follow-up admin is where time tends to go.
One practical consideration: follow-up emails work well for two-person conversations. For larger informal meetings involving three or more people, a more structured note shared to a group channel or document is usually clearer.
Informal meeting notes for brainstorming sessions
Brainstorms are reliably the worst-documented meeting type. Ideas come quickly, conversations overlap, and the person meant to be capturing things is usually either falling behind or half-distracted from participating. Most brainstorm notes end up either incomplete or unusably dense.
A few things make a real difference. First, use a shared whiteboard or collaborative document during the session so ideas get logged as they surface rather than reconstructed afterward. Second, assign one person explicitly to capturing, not as a secondary task but as their primary role for that session. This person doesn't need to contribute ideas; they need to keep an accurate log. Third, end every brainstorm with a two-minute synthesis: of everything discussed, what are the two or three things the group is taking forward? That synthesis is the most important part of your informal meeting notes for any brainstorming session.
A 2023 CIPD evidence review on productive meetings found that assigning a dedicated notetaker as an explicit role is one of the clearest markers of a well-run meeting. That principle is at its most useful in informal settings like brainstorms, where structure is least likely to happen naturally.
For brainstorm notes specifically, be explicit about which ideas were shortlisted and which were parked for later. 'We discussed ten ideas and landed on X, Y, Z' is a useful record. 'Here are all ten ideas with no indication of which were taken forward' is less so.
Capturing unplanned and ad hoc conversations
The informal meetings that most consistently go undocumented are the ones that weren't scheduled. Someone stops by your desk. You pull someone aside before a call. You talk through a decision during a coffee break. These ad hoc conversations often produce the most consequential agreements, precisely because they happen outside the normal meeting structure where people expect things to be recorded.
The simplest approach for unplanned conversations is a personal daily log. Two minutes at the end of each working day noting any unplanned conversations that produced a decision, a commitment, or a changed expectation. You don't need to share this log with anyone; it's for your own reference. But when a question comes up about what was agreed, or when someone remembers an unplanned conversation differently, having a note of it is significantly better than working from memory.
For ad hoc conversations that involve a commitment on someone else’s part, a brief follow-up message is worth sending. Even a simple email confirmation ensures both parties share the same record of what was agreed. This isn’t about paper trails; it’s about preventing the kind of misremembering that quietly derails projects.
Working sessions and collaborative meetings
Informal working sessions, two or three people sitting down together to work through a problem or build something, occupy an interesting middle ground between a formal meeting and individual work. They often produce decisions and clarifications that need to be documented, but they're not structured enough for the full template.
For working sessions, the most useful informal meeting notes are focused entirely on outputs: what was decided, what was built or drafted, what needs to happen next. The process of how you got there usually doesn't need to be recorded. A working session that produces a first draft of a proposal generates notes that say 'Draft proposal completed, shared with X for review by [date].' That's enough.
If a working session surfaces a disagreement or a significant pivot in direction, that does warrant more detailed notes. Not to assign blame but to create a record of why a decision was made, which is useful context for anyone coming into the project later.
Building the habit across your workday
Most people's resistance to informal meeting notes isn't the time it takes. It's the activation energy: the moment after a conversation when you have to consciously decide to write something down rather than move on to the next thing.
The most effective way to reduce that friction is to attach the note-taking to an existing habit. Notes immediately after you sit back down at your desk. Notes at the end of each meeting block in your calendar. Notes at the top of the hour if you've had a conversation since the last one. The specific trigger matters less than the consistency.
A daily log at the end of the day is a useful fallback for anything you didn't capture in the moment. It takes two or three minutes, and it ensures that informal decisions and agreements don't fall through the cracks overnight.
When informal notes end up mattering more than expected
Most informal meeting notes will never be particularly important. You write them, reference them once, and move on. That's the normal case, and it's fine.
But occasionally they become the only record of something that turns out to matter. A project where the scope shifted in an informal conversation and was then disputed. A commitment made in a catch-up that one person interpreted as final and the other as tentative. A decision about how to handle a client situation that seemed minor at the time and became significant later. In each case, having even a brief record makes a real difference to how the situation gets resolved.
The habit of keeping informal notes is cheap to build and occasionally very valuable. The effort is five minutes after a conversation; the benefit shows up in moments you can't predict in advance. If the follow-up part is where things tend to slip, Fyxer drafts those emails automatically after your meetings, so the record gets created without requiring a separate task.
Informal meeting notes FAQs
How detailed should informal meeting notes be?
As brief as possible while still capturing what matters. For a two-person catch-up, that might be three or four bullet points: what was discussed in broad terms, any decisions made, and the actions each person is taking away. For a larger informal working session, you might need a bit more context. The test is whether someone who wasn't in the meeting could read the notes and understand what was agreed and what happens next. If yes, the notes are detailed enough. If no, they need one more pass. They rarely need to be longer than a single page.
Do informal meeting notes need to be signed or formally acknowledged?
Not usually. The main purpose of informal meeting notes is shared understanding, not formal documentation. A quick follow-up message saying 'Good to connect, here's what I have as our next steps' is usually sufficient for catch-ups and working sessions. The exception is when an informal meeting produces a commitment or agreement that has material consequences, like a scope change on a project, a decision about resourcing, or a verbal agreement about a delivery. In those cases, getting written acknowledgment from the other party, even a simple 'yes, that's correct' reply to your follow-up, creates a record that both sides have confirmed the same understanding.
What's the best way to store informal meeting notes?
Wherever you'll actually find them. A personal note-taking app, a shared project folder, a pinned Slack thread, or a simple daily log document all work. The most important thing is consistency: one place, not several. Informal notes that are scattered across three different apps are functionally as lost as notes that were never taken. For notes that relate to an ongoing project, attaching them to the project record or folder makes them easier to find later. For one-off conversations, a simple date-ordered log is usually enough. The format matters much less than the habit.
