Turning three months of meeting transcripts into a leadership status report
A vendor implementation had been running for months across two overlapping weekly meeting series, and leadership's picture of it depended on whoever remembered the most from the room. Rebuilding that picture from the transcripts instead surfaced a scope change, a staffing conflict, and a data-migration gap that had been sitting there the whole time, just never in one place at once.
Category
Meeting-record synthesis and status reporting.
What I was trying to accomplish
A leadership-ready status report and tracker for a months-long vendor implementation, built from what was actually said in meetings, without anyone re-watching recordings.
The data challenges
About three months of calendar events and Teams transcripts, and a scheduling quirk where two different meeting series shared one identifier, which meant retrieving transcripts by explicit date and time windows instead.
The result
A Word report, executive summary, chronology, progress against plan, decisions log, ranked risks, open actions, recommendations, and a four-tab Excel tracker, which surfaced a vendor scope change, a staffing conflict, and a data-migration gap that were easy to miss scattered across many meetings.
Technical details
Tools: claude.ai with the Microsoft 365 connector (Outlook calendar and Teams transcripts), Word, Excel
A practice group was several months into implementing a new matter-management platform with an outside vendor. Progress lived in two recurring weekly meeting series, and leadership needed a clear picture of scope, timeline, risks, and open decisions.
Claude found the meetings through the calendar, retrieved every available transcript, wrote structured notes per session, and then assembled the report. One quirk shaped the retrieval method: the two meeting series shared the same underlying meeting identifier, so transcripts had to be pulled by explicit date and time windows, widened to allow for drift between scheduled and actual meeting times.
The value was in surfacing what was easy to miss across many meetings: a change in the vendor's scope estimate that needed leadership attention, a staffing conflict with the go-live target, and a data-migration gap with no automated path. This is one of the most reusable patterns: if the meetings are recorded, the status report can be rebuilt from the record.
Pull up a chair.
Let's talk through where things stand, and where they could go.