Action Items Extraction from Meeting Transcripts Implementation
Action Items are concrete tasks with assignee and deadline that emerge during discussion. They must be extracted precisely from an hour-long transcript: miss none, capture no hypothetical promises.
Extraction Approach
Direct prompt with instruction "find all tasks" produces noise—the model includes discussions and questions as tasks. Better approach—two-stage:
-
Phrase Classification — model passes through transcript marking fragments as:
action_item,decision,question,discussion -
Structuring — only
action_itemfragments are processed for field extraction
class ActionItem(BaseModel):
task: str # task description
assignee: str | None # assignee name (if mentioned)
deadline: str | None # deadline (if mentioned)
context: str # original quote from transcript
confidence: float # model confidence
Handling Uncertainty
Transcripts contain conditional commitments: "We should probably", "Maybe Ivan will handle it". Model must distinguish:
- Clear commitment: "Peter, do it by Friday" → confidence 0.95
- Potential task: "We need to figure out this issue" → confidence 0.6, flag for review
Action Items with confidence < 0.7 are placed in separate section "Require clarification".
Task Tracker Integration
Automatic task creation in Jira / Linear / Asana / Trello via API after user confirmation (or automatically for tasks with confidence > 0.9). Assignee mapped to real users via fuzzy name matching.







