Feed a messy 45-minute project-meeting transcript through AI to produce minutes, a decision log, and an owner-dated action table, then draft the follow-up email — and catch the trap: a decision that was made, argued over, and reversed. The final position must be recorded, not the loudest one.
Dev Prasad coordinates fit-out projects at Northwind Interiors Pvt Ltd, a fictional commercial-interiors firm. Tuesday's project review for the "Corvus office" job ran long, half the room talked over the other half, and the client expects minutes by end of day. Dev has the auto-generated transcript — which means he has everything anyone said, including the things they later took back. Transcripts don't mark which statements survived the meeting. AI extracts structure from transcripts brilliantly, but it weights confident, repeated statements — and in this meeting, the wrong version of a key decision got said three times before being overturned once, quietly, near the end. Minutes that record the loud version instead of the final one would send the project off in the wrong direction with the client's written blessing.
An excerpt covering the decision-heavy stretch of the meeting. Treat it as the authoritative record. Speakers: Dev (coordinator), Meena (project head), Sanjay (procurement), Alka (design lead), Ravi (site engineer).
[00:14:22] Meena: Okay, flooring. We said Duraline for the vinyl,
correct? Sanjay, where are we?
[00:14:31] Sanjay: Duraline quoted 11 lakh, delivery in 3 weeks.
I say we lock Duraline today. They are reliable, we have used
them on four jobs.
[00:14:50] Alka: The client's design intent says acoustic rating -
Duraline's standard range does not meet it. FloorTech does.
[00:15:05] Sanjay: FloorTech is 13.2 lakh and they slipped delivery
on the Meridian job. Duraline. Let us not overcomplicate.
[00:15:20] Meena: Noted. Let us go Duraline then - Sanjay, start
the paperwork.
[00:15:26] Ravi: [crosstalk] --the site measurement--
[00:15:29] Sanjay: Great, Duraline it is. I will raise the PO.
[00:19:44] Dev: Parking the flooring PO for one sec - Ravi, you had
the electrical point?
[00:19:52] Ravi: Yes, the DB room layout changed, I need revised
drawings before the electrician can quote. Someone has to send
them. Not sure who owns that now.
[00:20:04] Meena: Alka, your team? Or the consultant? Sort it out
between you. It is needed by Friday.
[00:20:15] Alka: We will figure it out.
[00:31:10] Alka: Coming back to flooring - I checked the spec
while we talked. The contract SLA with Corvus commits to acoustic
class 33. Duraline standard is class 32. If we install Duraline
standard, we are in breach. It is not a design preference, it is
contractual.
[00:31:38] Meena: That changes it. Sanjay, hold the Duraline PO.
[00:31:44] Sanjay: We agreed Duraline twenty minutes ago.
[00:31:49] Meena: And now we know it breaches the SLA. FloorTech,
or Duraline's acoustic range if it certifies to 33 and lands
under 12.5. Sanjay, get both numbers by Thursday. Decision
stands: not Duraline standard.
[00:32:10] Sanjay: Fine. I will get quotes. For the record I think
we are overpaying for a rating nobody will measure.
[00:32:19] Meena: Noted for the record. Moving on. Handover date -
client asked to prepone to the 24th. Ravi, feasible?
[00:32:40] Ravi: Only if flooring materials land by the 10th.
Otherwise the 24th is fiction. The original date, the 28th, is
safe either way.
[00:33:01] Meena: Then tell the client: we hold the 28th, and if
materials land by the 10th we will surprise them early. Dev,
draft that note for my review - do not commit to the 24th.
[00:33:30] Dev: Got it. Also the snag list from the last walkthrough
- who is closing the paint touch-ups?
[00:33:41] Meena: Site team. By Friday the 21st.
[00:33:52] Ravi: Friday is the 22nd this month, Meena.
[00:33:58] Meena: Whichever - by that Friday. Next item...
Read the transcript with a highlighter mindset. Before prompting, read it once and mark three things in your notes: every point where a decision is stated, every point where a previously stated decision is modified or reversed, and every action that floats without a clear owner. Transcripts reward slow first reads — the reversal pattern ("we agreed X" ... "that changes it") is easy to see once you look for it and easy for summarizers to miss.
Extract decisions with a reversal-aware prompt. Paste the transcript with: "Extract every decision from this transcript as a table: topic, initial position (if any), final position, who ratified it, timestamp of the FINAL statement, and status (firm / conditional / pending information). Where a decision was changed during the meeting, show both the superseded and final versions explicitly. Do not merge them." The explicit superseded-vs-final structure is the guard rail — a generic "summarize decisions" prompt is how reversals get lost.
Audit the decision table against your step-1 notes. Check the big one: what does the table say about flooring? The correct final position is specific and conditional — verify the table captures the condition (certification and price ceiling), the deadline for the missing information, and that Duraline-standard is recorded as rejected, not chosen. Check the handover-date decision the same way: the recorded position must be the one Meena instructed Dev to communicate, not the client's request.
Build the action table — and chase the orphans. Prompt: "Extract all action items: action, owner, deadline, source timestamp. Mark any action with an unclear owner or ambiguous deadline as UNRESOLVED rather than guessing." Then resolve the unresolved yourself, the way a coordinator actually would: an action with no owner gets assigned in the minutes with a note ("owner to be confirmed between X and Y — flagged"), and an ambiguous date gets resolved against a calendar. Never let "we will figure it out" survive into a circulated action table unowned.
Fix the calendar facts. One deadline in this meeting was stated with a date that does not exist as spoken. Check every date in your action table against the correction made in the room, and record the resolved date with a note. Dates are the highest-frequency transcript error class — names and numbers are second and third — so make this a standing check in every minutes pass.
Generate the minutes. Prompt: "Write meeting minutes from this transcript for circulation to the internal team and the client PM: attendees, 5-8 bullet summary of discussion, the decision log table, the action table, and open items. Neutral tone. Where the meeting recorded a dissent for the record, include it factually in one line. Do not include verbatim crosstalk or attribute emotions." Review: the flooring section must read as one coherent final decision with the history compressed to a line, and Sanjay's on-record dissent should appear as stated fact, not color.
Draft the two follow-up emails. First, the internal follow-up: actions, owners, dates, and the two information deadlines (quotes by Thursday; drawings by Friday). Second, the client note Meena requested — and here precision is contractual: it must hold the original handover date and frame the earlier date only as an unpromised possibility. Prompt the AI with Meena's exact instruction pasted in, then verify the draft against it word by word: any sentence a client could read as committing to the 24th fails.
Human-confirm before circulating. The last step of a real pipeline: send the decision log (just that table, not the full minutes) to the meeting chair for a yes/no confirmation before wide circulation. In this lab, simulate it — reread the transcript one final time checking only the decision table, then stamp the minutes "decisions confirmed against transcript". Commitments circulate fast and retract slowly; the 3-minute confirmation loop is what makes an AI minutes pipeline safe enough to run weekly.
A transcript records everything said, including everything later unsaid — always extract decisions with superseded and final versions shown separately, and record the final position.
Meetings decide things by revising them, and transcripts preserve every draft of the decision — so extract with superseded-versus-final structure, resolve owners and dates like a coordinator, and get the decision log human-confirmed before anything circulates. The pipeline is fast; the confirmation loop is what makes it trustworthy.