Target outcomes
- Commitment capture rate on audited samples
- Zero auto-sync without human approval in pilot
Initiative playbook
Typical delivery arc for this pattern in enterprise programs.
- 1Discovery2 to 4 wks
Define required fields per meeting type (standup vs steering); connect target task system fields.
- 2Pilot6 to 8 wks
Human review 100% of extractions before sync; track owner-field accuracy.
- 3Scaleongoing
Calendar integration for titles/attendees; optional Teams transcript ingestion with retention policy.
Business use case
Problem
Meetings produce notes and recordings but actions live in people's heads until someone retypes them into Jira, Asana, or email.
Who benefits
- Chiefs of staff and PMO, reliable action lists after leadership forums
- Engineering managers, standup and retro outputs structured consistently
- Customer success, QBR commitments captured before the next call
Success metrics
- ≥ 95% of explicit commitments captured as action items (human audit sample)
- Owner field only populated when notes name someone, no hallucinated assignees
- Human review step before any task system sync
Solution
Paste raw notes; Claude returns meeting title, summary, action items (optional owner and due hints), and open questions, using a dedicated schema separate from initiative charter extraction.
Technical implementation
Stack
- @ai-sdk/anthropic +
generateObject - meetingNotesSchema in
lib/demos/meeting-schema.ts
Architecture
Notes in; structured actions out, same HITL pattern as charter extraction, different schema.
Outcomes and learnings
Different schema from portfolio chartering, optimise fields for follow-through, not funding decisions.
- Optional fields reduce harmful guesswork on owners and dates
- Open questions are first-class so decisions do not get lost inside summaries
- Same API pattern as charter extraction; swap schema per document type
Where else this applies
Meeting-to-action extraction is the everyday sibling of charter extraction, optimised for operational follow-through rather than portfolio decisions.
Steering committee actions
Capture decisions, owners, and due hints from leadership meeting notes.
Sprint planning
Turn refinement discussion into draft stories and open questions for the scrum master.
Customer success QBRs
Extract commitments made to accounts before they disappear in call recordings.
Cross-functional war rooms
Incident or launch reviews produce a single action list with accountable names.
Using this stack elsewhere
Claude handles long transcripts; push JSON into Asana, Jira, or Teams task APIs after human review in the same HITL pattern as other structured outputs.
Live demo
The demo is the same code path described above, not a simplified mock UI. Add keys in .env.local when you are ready; the narrative and diagrams stand on their own without them.
Business
Paste standup or leadership notes, get action items with owners only when the notes name them.
Technical
Claude generateObject with meetingNotesSchema; separate from charter extraction at /api/demos/claude-meeting.