How project managers keep meeting notes and a decision log

A delivery week is mostly conversations

Count the meetings in a normal sprint week. Five standups. Backlog refinement, sprint planning, sprint review, retro. Two or three one-on-ones. A vendor call. A steering committee, monthly if you are lucky and weekly if the project is in trouble. Plus the four or five unscheduled conversations that happen when someone catches you after standup and a decision gets made standing up.

That is fifteen to twenty conversations a week for one person. Almost all of them produce something that has to be written down: a decision, a risk, a dependency, a date that moved, a person who agreed to do a thing.

What most project managers do is type while half-listening, which produces a document that is neither good notes nor a good contribution to the meeting. Or you write it up at six in the evening from memory, which means you write down what you remember, and that is not the same as what happened. The parts that get lost are predictable.

• The reasoning behind a decision. You capture "we are going with option B" and lose the three reasons why, which are the only part anyone asks about later.
• Who actually agreed. Notes say "the team decided". Four months later you need a name.
• The quiet objection. Someone raised a concern, it was not resolved, and it was not loud enough to reach the summary. It becomes the issue that hits you in delivery.
• The exact date someone committed to. "Next week" in the room becomes a guess in the notes.
• Everything said in the corridor. No agenda, no notes, real decisions.

The decision log is the argument, not the notes

Every project methodology tells you to keep a decision log. Almost nobody maintains one past week three, because it is a separate document that only gets updated when you remember to update it, and you are busy.

The thing worth understanding is what a decision log is for. It is not for the team. The team already knows. It is for the moment months later when a sponsor, an auditor, a new stakeholder or a supplier asks why something is the way it is. At that moment you need five specific facts, and a normal set of meeting notes gives you two of them.

A recording gives you all five, without you maintaining anything.

Here is the situation this actually solves. A sponsor asks why the integration was descoped. You believe it was agreed in a steering committee in March, on the basis that the supplier could not commit to an API date.

With a searchable archive of recordings you type the word "descope" into search, get every note where it was said, open the March steering committee, and tap the transcript line to hear that exact ten seconds of audio. You can read who said it, see the timestamp, and export the section as a PDF to attach to your reply. That is not a better memory. It is evidence.

Two unglamorous features make this work. Search across every note's title and AI notes, so you find the conversation without knowing which meeting it was in. And synced playback, where tapping a transcript line plays the audio from that moment, so you can check the context rather than trusting one line in isolation. Being able to ask questions across all your meeting notes at once turns the archive into something you can interrogate instead of something you have to remember.

Kept that way, the decision log stops being a document you maintain and becomes a by-product of recording. Every entry carries the five facts that matter later.

• What was decided. The exact wording, not your paraphrase written up hours later.
• Who decided it. Speaker labels tell you which voice said the deciding sentence.
• When. The date of the recording and a timestamp on the segment itself, so you can say "14 March, 32 minutes in".
• On what information. The five minutes of discussion before the decision, which is normally the part that never gets written down at all.
• What was rejected and why. The options that lost. This is the single most useful thing to have when the same debate reopens in month six.

Where a project manager actually has to capture

The ceremonies are spread across formats, which is why single-format tools fail this role. A tool that only sends a bot into video calls misses half your week. Microsoft 365 Copilot has a sharper version of the same problem, because it only writes the recap for meetings held inside Teams — see what to use for meeting notes when the meeting is not in Teams. Here is the map.

What to get out of each ceremony

One recording can be reshaped into different documents, because the output style changes the format without changing the source. This is the biggest time saving in the role, so be deliberate about which style each ceremony needs.

The six styles are: minutes of meeting, key bullet points, email, to-do list, formal report, and custom instruction (you describe in your own words exactly how you want it written). Map them like this.

A worked example: one steering committee, three documents

A 50-minute steering committee. Sponsor, tech lead, finance, and the supplier's account manager. Three things came out of it: the phase two date moved to November, the integration was descoped, and finance asked for a revised cost view by the 20th.

You record the room from your phone. It keeps running with the screen locked, so you can put the phone face down and take part in the meeting instead of typing. Afterwards you run the same recording three ways.

Run one, minutes of meeting. You get a structured record: attendees, what was discussed, decisions with the reasoning that led to them, and the open points. This is the version that goes into the project file and becomes the decision log entry. It is the one you will be glad about in month four.

Run two, to-do list. The same 50 minutes comes back as commitments. "Finance to produce revised cost view by the 20th." "Supplier to confirm API availability before next committee." "PM to update the plan and reissue." Action items are pulled out automatically, so this is mostly a matter of checking rather than writing.

Run three, formal report. The sponsor does not want minutes. They want status, the change, the impact and the ask. The formal report style produces that shape from the same audio, and you edit the top line rather than starting from a blank page.

Three documents, three audiences, one recording, none of them written from memory. Then export: PDF for the project file, Word if the PMO template needs the text pasted in, plain text or rich-text copy for the email.

Action items with an owner and a date, and chasing them next week

Action items get pulled out of every recording automatically. That solves capture, not quality. An item only survives the week if it has a task that starts with a verb, one named owner, a real calendar date and a done-condition anyone can check. The recording gives you the raw material for all four, but you still have to insist on them in the room. There is a full breakdown of the four fields in the action items list template.

One habit makes the automatic extraction much better: close every ceremony by saying the commitments out loud, with names. "So Priya sends the revised estimate by Thursday the 14th." If it is spoken, it gets captured. If it lives only in a head nod, nothing can capture it.

When a name or a system term comes back wrong, edit the transcript and re-run the summary. The summary picks up the correction, so the action item ends up with the right owner rather than a phonetic guess. The mechanics of that are covered in editing an AI transcript and re-running the summary.

Chasing is where the archive earns its keep. Next week you do not want to reread five sets of notes, you want to ask a question. AI chat works across all your notes at once, so you can ask what was committed in the last three sprint reviews, or whether the API date has come up since March. Keep a folder per project and search stays clean two years in.

Status reporting to a sponsor, in the sponsor's language

Sponsor reporting is the task most project managers are worst at, because it happens on Friday afternoon when you are tired and the information is scattered across a week of conversations you half remember.

Working from recordings changes the order of the job. You are not reconstructing the week. You are selecting from a set of documents that already exist, each one produced from the meeting it describes, in the shape that meeting needed.

A sponsor report is a different document from minutes, and the difference is what you leave out. The sponsor wants the status, what changed since last time, what it costs in time or money, and what they have to decide. Run formal report on the one or two meetings that actually moved the picture, take the slipped dates out of the minutes you already filed, and edit the top line so it says what you want it to say. An hour of remembering becomes fifteen minutes of choosing.

If the squad switches language mid-sentence, the transcript still holds the decision, because language is tagged word by word rather than locked to one language for the whole recording and you never pick a language before you press record. That matters for sponsor reporting because the sentence you have to report is often the one you did not fully follow in the room. The detail is on the multilingual meeting transcription page.

If the sponsor is in another country, translate the finished note. Translation covers 18 languages: Arabic, Chinese (Simplified), Chinese (Traditional), Dutch, English, French, German, Indonesian, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Thai, Turkish and Vietnamese. Run the meeting in the language the team speaks, send the report in the language the sponsor reads.

For the covering email, a Custom instruction lets you spell out the tone you want rather than accepting something that reads like a machine wrote it. That matters more than it sounds, because a sponsor update that does not sound like you invites questions about whether you actually understand the project.

A realistic week, step by step

1. 1Monday, connect the calendar once. Google Calendar syncs on both iPhone and Android, and the Microsoft or Outlook calendar connection is iPhone only. Either way the meetings that need a bot are already listed and you are not pasting links every morning.
2. 2Standup, one tap. On iPhone, start the recording from the Control Center widget before you walk into the room. Fifteen minutes later, stop it. Run key bullet points.
3. 3Say the commitments out loud at the end of every ceremony. Name plus task plus date. Ten seconds of discipline that decides whether the action item list is any good.
4. 4Refinement and planning, run to-do list. Copy the items across to your board while the context is fresh.
5. 5Sprint review, send the bot. It joins Zoom, Google Meet, Microsoft Teams, and Webex if you are on iPhone, and you take part in the review instead of typing during it.
6. 6Fix names in the transcript, then re-run. Do this once, on the meetings that produced real decisions. Do not do it on the standups.
7. 7Steering committee, run minutes of meeting first. That is your decision log entry. File it before you write anything else, because it is the artefact that has to survive.
8. 8Then run formal report on the same recording for the sponsor, and edit the top line so it says what you want it to say.
9. 9Friday, ask across all your notes. What was committed this week, what slipped, what is still open. Then export what you need as PDF or Word and paste the rest where it has to go.
10. 10Keep one folder per project. Not per sprint. You will search across the whole project, not a fortnight.

Pricing when you are one PM or a small delivery team

Meeting tools are mostly priced per seat, which punishes this role. A project manager is often the only person who needs the notes, but per-seat billing charges for everyone whose meetings get recorded.

Noter AI is $9.99 a month or $49.99 a year, flat per person, with no per-seat multiplier and no admin or workspace surcharge. Be precise about what flat means, because it is easy to read it as something it is not. It is not one account that covers the whole squad. It is an individual product, so each person who wants their own recordings holds their own subscription. Five people who all need it means five subscriptions, not one invoice. The saving is in the rate per person, not in buying a single seat for everybody.

On annual billing those numbers drop hard. $49.99 for the year is about $4.17 per person per month, so three people cost roughly $12.50 a month between them, five cost about $21, and ten cost about $42. The honest comparison is $4.17 to $9.99 per person against $10 to $19 per seat, plus no AI credit cap, no monthly summary allowance and no separate charge for translation or the meeting bot. Nothing runs out on the 20th of the month.

What the per-seat price buys elsewhere is the part to weigh against that. A shared workspace, one invoice for the PMO, admin control over who recorded what, and search across everyone's meetings rather than just your own. If your programme needs those, a per-seat tool is what you are actually buying and the extra money is not waste. If you are one PM, or a squad where each person just wants their own ceremonies captured, it is infrastructure you will never open. The per-seat pricing comparison works the numbers both ways.

That rate is still the argument. Here is what the same team costs a month, with everyone on their own subscription.

The honest limits, and where to start small

This is the part that decides whether the workflow fits your setup, so it is worth being blunt about it.

There is no Jira, Asana, Linear, Trello or Monday integration. Action items do not appear as tickets. You get a clean list with owners and dates, and you copy it into your tracker yourself. For most project managers that is two or three minutes after a ceremony, and the manual pass catches items that should never have become tickets. But if you were hoping for automatic ticket creation, it does not do that. Same for Slack, Notion, Zapier and any CRM. Export and paste is the workflow.

There are no live captions during the meeting. Transcription happens after the recording finishes. If your accessibility need is real-time text on screen while people are speaking, this is the wrong tool.

Video files do not import. Only audio. M4A, MP3, WAV, AAC and the other formats iOS handles natively. If a colleague sends you an MP4 of a recorded call, you cannot drop it in. There is also no YouTube or URL import, and no PDF import, so you cannot feed it a specification document and ask questions about it.

Transcription happens in the cloud, not on the device. Audio is encrypted in transit and at rest and you can delete your data at any time, but if your programme runs under a rule that says recordings never leave the device, that rules it out. Check that before you record a steering committee, not after.

It is an individual product, not a team platform. There is no shared workspace, no centralised billing and no admin console. Each person on the team holds their own subscription, so a ten-person team means ten subscriptions rather than one invoice. Your notes are yours and nobody else on the project can search them. If the PMO needs one purchase order and admin oversight of what was recorded, this is the wrong shape of tool and a per-seat product is the right one.

It does not maintain your RAID log or your plan. It produces the text. The project artefacts are still yours to keep.

Do not roll it out across the programme in week one. Pick the meeting where a bad record costs the most, usually the steering committee or the kickoff, and record only that for a fortnight. Two recordings tell you whether the minutes are good enough to file.

If it is a new project, the kickoff is the natural place to begin, because it is the meeting that sets the decisions everything else refers back to. The structure to aim for is on the project kickoff meeting template page.

The free version caps recordings at about five minutes, which is enough to judge transcript quality on a real conversation before you pay. Audio import needs a subscription, so a full steering committee is a paid test rather than a free one. Noter AI is on the App Store for iPhone and iPad, and on Google Play for Android.

One caveat on the week described above: it is written for iPhone. On Android the calendar sync is Google only, there is no Outlook connection, the bot covers Zoom, Google Meet and Microsoft Teams but not Webex, and there is no tablet layout. The recording, the output styles and the search all work the same. The Android note taker page lists the differences in full.

If most of your ceremonies happen with people in a room rather than on a call, the in-person meeting recording page covers that side in more detail.