Section 6Data & Knowledge

Meeting Intelligence Framework

Extracting maximum value from Teams meetings, transcripts, and recordings — automated action tracking, risk logs, and decision management.

The Meeting Intelligence Opportunity

Tax and Finance professionals spend 30-50% of their time in meetings. Most meeting value is lost within 24 hours because:

  • Action items are not systematically tracked
  • Decisions are not formally recorded
  • Risks mentioned casually are never logged
  • Context discussed verbally never reaches documentation

Copilot for Microsoft 365 (Pro license) can transform meetings into a structured knowledge source.

What Copilot Can Extract from Meetings

Element Extraction Method Output Format
Action items Post-meeting summary Owner, task, deadline
Decisions made Copilot recap Decision, rationale, participants
Risks mentioned Targeted prompt Risk description, owner, severity
Open questions Targeted prompt Question, who raised it, follow-up needed
Key discussion points Auto-summary Topic, positions taken, outcome
Follow-up meetings needed Targeted prompt Topic, suggested attendees, timeline

Workflows

Workflow 1: Action Tracking

During meeting (Copilot in Teams): Real-time: "What action items have been assigned so far in this meeting?"

After meeting:

"Review the transcript of today's [meeting name]. Extract all action items in this format: | Action | Owner | Deadline | Priority | Dependencies |. Include implicit commitments ('I'll look into that') not just explicit assignments."

Weekly follow-up:

"Based on action items from my meetings this week, create a consolidated to-do list grouped by: (1) Due this week, (2) Due next week, (3) Ongoing/no specific deadline. Flag any that conflict with each other or appear duplicated."

Workflow 2: Risk Tracking

After each IDF project meeting:

"Review this meeting transcript and identify any risks, concerns, or potential issues mentioned by participants. For each, capture: (1) Risk description, (2) Who raised it, (3) Potential impact (schedule/cost/quality/scope), (4) Suggested mitigation (if discussed), (5) Status (new/existing/escalated). Format as rows for our RAID log."

Monthly risk consolidation:

"Review all IDF meeting transcripts from [month]. Compile a comprehensive risk register update showing: new risks identified, risks that were resolved, risks that have escalated, and any patterns or themes emerging across multiple meetings."

Workflow 3: Decision Logs

After decision-making meetings:

"From this transcript, extract all decisions made. For each decision, document: (1) What was decided, (2) Alternatives considered, (3) Rationale for the chosen option, (4) Who made/approved the decision, (5) Conditions or caveats, (6) Effective date. Format as a formal Decision Record."

Why this matters: Six months from now, when someone asks "Why did we choose vendor X?" or "Why did we take this VAT position?", the answer exists in a searchable, structured format — not buried in a transcript nobody will re-watch.

Workflow 4: Stakeholder Management

After multi-stakeholder meetings:

"Analyze this meeting transcript for stakeholder dynamics: (1) Who contributed most/least? (2) Were there disagreements? Between whom? On what? (3) Who seemed disengaged or unclear on their role? (4) Were there any concerns raised that were not fully addressed? (5) What follow-up communication is needed and to whom?"

Quarterly stakeholder analysis:

"Based on meeting transcripts from the last quarter involving [project/topic], create a stakeholder engagement assessment: Who has been consistently present? Who has reduced engagement? What topics generate the most discussion/disagreement? Where do we need better alignment?"

Workflow 5: IDF Steering Committee Intelligence

Pre-meeting:

"Based on the last 3 IDF steering committee transcripts, identify: (1) Recurring concerns from specific members, (2) Decisions that were deferred and need revisiting, (3) Commitments made that should be reported on, (4) Topics that should be proactively addressed to avoid escalation."

Post-meeting:

"Generate the formal steering committee minutes from this transcript. Format: (1) Attendees and apologies, (2) Previous actions — status update, (3) Decisions made (numbered), (4) New actions (numbered, with owner and deadline), (5) Risks escalated, (6) Next meeting date and agenda items."

Meeting Templates for AI Optimization

To maximize AI value from meetings, structure them for extraction:

Recommended Meeting Format

Segment Duration Purpose AI Extraction Target
Opening 2 min State meeting objective Context for all decisions
Status updates 10-15 min Factual progress Milestone tracking
Discussion items 20-30 min Analysis and debate Decision rationale
Decision points 5-10 min Explicit decisions Decision records
Actions & next steps 5 min Assignments Action items
Risk round 3-5 min Any new risks? Risk register updates

Key principle: Verbally state decisions clearly. Say "So the decision is..." before moving on. This gives Copilot a clean extraction target.

Governance

Transcript Retention Policy

Meeting Type Retain Transcript Duration Storage
IDF Steering Committee Yes 7 years SharePoint - IDF
Tax Advisory Discussions Yes 7 years SharePoint - Tax
Team Stand-ups No Auto-delete 30 days Teams
One-on-ones No Personal choice Personal OneDrive
External (with advisors) Conditional Subject to privilege review Restricted library

Access Controls

  • Transcripts inherit meeting sensitivity label
  • AI queries should respect the same access boundaries
  • External meeting transcripts require explicit consent from all parties
  • Privileged discussions (legal advice) should have transcription disabled

Measuring Impact

Metric Without Meeting AI With Meeting AI Improvement
Action item capture rate ~40% ~90% 125% improvement
Time to produce minutes 30-60 min 5-10 min 80% reduction
Decision traceability Poor (email search) Full (structured log) Qualitative step-change
Risk identification Reactive Systematic Early warning capability
Follow-up completion rate ~60% ~85% 42% improvement