Bridge

Free tool

AI Decision Extractor

Find every decision in a meeting transcript, with the reasoning, who made the call and the options that were turned down.

Meeting transcript

Drag & drop a transcript, or click to upload

.txt, .vtt, .srt, .md or .pdf up to 1 MB, from Zoom, Google Meet, Microsoft Teams and more

or paste it

0 / 75,000

How it works

Add the transcript

Upload a .txt, .vtt, .srt or PDF export from Zoom, Google Meet or Microsoft Teams, or paste the text.

Get the decision log

Bridge lists each decision with its rationale, decision maker and alternatives, then what is still open.

Add it to your log

Copy the entries into Notion, Confluence, a spreadsheet or your project wiki, or share the link.

Example output

Decision Log: EU Launch Readiness Review

A sample decision log. Yours follows the same layout.

Decisions

  1. 1

    Move the EU launch from March 1 to April 15.

    Why: the Frankfurt data center won't be certified before the end of March, and customers in Germany require EU hosting.

    Owner: Sofia Lindqvist
    • Considered: Launch on March 1 with US hosting as a temporary fallbackSet aside: legal said two of the pilot customers would not sign.
    • Considered: Launch in the UK only on March 1Set aside: too little demand to justify a separate launch.
  2. 2

    Price the EU plans in euros at the same numbers as the US dollar plans.

    Why: simpler for sales, and the difference is within the planned discount range.

    Owner: Jonas Weber
  3. 3

    Hire the German-speaking support lead before launch instead of using an agency.

Open or deferred decisions

  • Do we offer the pilot customers a free first quarter to make up for the delay?

    Finance wants to see the revenue impact first.

    Owner: Jonas WeberDue: next Tuesday

Decisions to revisit

  • April 15 launch date

    If certification slips past March 31.

Remember why, not just what

Three months after a meeting, the question is rarely "what did we decide?". It is "why on earth did we decide that?", and "did anyone think about the other option?". Without a written record, teams relitigate settled choices, new joiners repeat old debates, and nobody can tell whether the conditions behind a decision have changed. A decision log fixes that, but only if someone writes it.

The AI Decision Extractor writes the entries for you. It reads the transcript and separates the choices the group actually settled from the ideas that were only floated. Each decision is stated so it stands on its own in a log, with the specifics that were said, the reason given for it, who made the call or whose proposal won, and the alternatives that were considered along with why they were set aside.

It also lists what is still undecided: questions that were deferred, escalated or ran out of time, with what is blocking them and who will bring them back. When the group named a trigger for reconsidering a choice ("if the bugs aren't fixed by the 13th", "after the pilot"), that goes under decisions to revisit. A maybe is never upgraded into a decision, and no reason is invented when none was given.

Who keeps a decision log

Leadership and steering meetings

Executives and program leads keep a dated record of strategic calls and the reasoning behind them, ready for the next quarterly review.

Architecture and design reviews

Engineering and design teams capture the trade-offs behind a choice, much like a lightweight architecture decision record.

Product prioritization

Product managers show stakeholders what was cut, what was deferred and why, instead of re-explaining it in every meeting.

Handovers and new joiners

Someone taking over a project reads the decision log first and understands which debates are already closed.

Frequently asked questions

What is a decision log?

A running record of the important choices a team makes: the decision, the date, who made it, the reasoning and the alternatives considered. It lets anyone check later why something was done and whether the reasons still hold.

How does it tell a decision from a discussion?

It looks for agreement: "let's go with", "agreed", or a clear call by the person in charge that nobody objected to. Proposals that were debated but never settled are listed as open decisions rather than recorded as decided.

Why record the options that were rejected?

Because the same alternatives tend to come back. Writing down what was considered and why it lost saves the team from re-arguing it, and shows when a changed situation makes a rejected option worth another look.

What if nobody said why a decision was made?

The rationale is left empty. The tool only records reasons that were stated in the meeting, so a blank is a useful prompt to ask the decision maker and add the reason yourself.

Who can see the decision log?

Whoever you share its link with, and nobody else. Links are long and random, decision logs are not listed publicly or indexed by search engines, and the transcript you upload is not used to train AI models.

Can I keep a decision log across all my meetings?

Yes. With a free Bridge account every meeting is recorded and transcribed, and you can ask the AI assistant what was decided about any topic across all your past calls. Learn more →

Meet thoughtfully, meet on Bridge.