How to Track Decisions Across Recurring Meetings on Mac

The simplest way to track decisions across recurring meetings is a decision log: one row per decision, with the date, what was decided, any condition, who approved it and the meeting it came from. Update it after every meeting, and change a row only when a later meeting clearly changes that decision. Rebrief for Mac helps by recording each meeting and listing its decisions in the notes, so the log starts from what was said instead of from memory.

Without a log, weekly meetings slowly change the plan and two people end up remembering different versions. The log is the one place that says which choice applies now.

What to put in a decision log

Keep each entry short enough to read in a few seconds. A useful entry answers:

• What was decided, in one sentence.
• Any condition that has to be met first.
• Who approved it.
• Which meeting it came from, with the date.
• Whether it is current, or which later entry replaced it.

Leave out discussion that didn't settle anything. Ideas, estimates and "let's look into it" belong in the meeting notes or as open questions, not in the log.

Decision log template

Copy this table into the project document or tracker your team already uses. The first row is a filled example.

Never delete an old entry when a decision changes. Mark it as replaced and point to the new one, so an older agreement still makes sense when someone finds it.

Worked example: a pilot decision that changed

This short example is made up for illustration, not a Rebrief result. In one weekly meeting, the team agrees to let three organizations join a pilot. A week later, the project lead says:

"We can increase it to six once the daily export limit is ready. Until then, keep it at three."

The person doing the work says the limit is unfinished. A log entry saying "Pilot increased to six" would send the team ahead too soon. After checking the conversation, the entry should read:

Keep the pilot at three organizations. Expansion to six is approved once the daily export limit is ready. Confirm that work is complete before inviting the additional organizations.

Add the meeting date and the passage you checked. The team can see the choice that applies today, what would change it, and why three still holds when someone remembers hearing six.

The meeting shows that someone committed to building the limit. It doesn't show that the work shipped. Check the delivery task or ask its owner; silence in the next meeting does not mean it is done.

How to update the log after each meeting

1. Record the meeting in Rebrief and wait for the transcript and notes. Notes are written after the call, not live.
2. Read the Decisions section of the notes, then open the transcript around each decision. Read the reply that follows it: "Let's expand the pilot" may be followed by "once support confirms cover".
3. For each real decision, add a row or mark an older row as replaced. A later mention doesn't automatically replace an earlier decision; someone may only be suggesting an option or asking for an estimate.
4. Check speaker names and numbers against the audio when they matter.
5. Move anything left unsettled to the agenda for the next meeting, with the person who can decide.

You can copy Rebrief's meeting notes as Markdown to help write the entries. Rebrief has no shared team workspace, so putting the log where your team works is a separate step you do yourself.

When two people remember a different decision

Search the meetings instead of arguing from memory. In Rebrief's Ask, try "What did we agree about the export pilot's size, and what changed in the recent project meetings?" It answers across your recorded meetings and shows the lines it used, so you can open the meeting where the plan changed. For how to phrase questions and check the sources, see how to search past meeting transcripts by asking questions.

If a decision changed in an email or chat message, add that message to the log as the source yourself. Rebrief only knows the meetings you recorded, and a newer written approval wins over an older meeting.

Before the next recurring meeting

Open the log and list the conditions still waiting, such as "expand once the export limit is ready". Bring each one to the meeting and ask whether it has been met or whether the team is changing the agreement. Afterward, update the row.

Recording the meetings

Ask for permission before recording and follow your organization's rules; tell people you're recording, as recording laws differ by place. Rebrief records your microphone and the call audio with no bot in the call, and works with Zoom, Google Meet, Teams and other call apps. If your project meetings run on Teams, see how to record and summarize Teams meetings on Mac without Copilot. Start recording manually if you're only listening.

Rebrief needs an Apple Silicon Mac with macOS 15 or later, and the support guide covers setup. Free recordings stop at 15 minutes, so a longer project meeting needs the one-time unlock. Start with the next decision someone disputes: find its source, write the log entry, and share it where your team works.