Overview
Engineering teams generate valuable knowledge in meetings, but capturing and organizing this information is often manual and error-prone. This pipeline automates the extraction of:- Action Items: Tasks, assignees, and deadlines
- Decisions: Key decisions and their rationale
- Technical Entities: Services, technologies, metrics, and incident references
- Team Analytics: Workload distribution and productivity metrics
Features
Native Transcript Parsing
Built-in support for parsing transcript formats with speaker and timing information.
Semantic Extraction
LLM-powered extraction of technical entities, action items, and decisions.
Structured Processing
Transform unstructured meeting content into queryable DataFrames.
Team Analytics
Generate workload metrics and productivity insights automatically.
Sample Data
The example processes three types of engineering meetings:- Architecture Review - Technical discussions about system design and bottlenecks
- Incident Post-Mortem - Analysis of outages and mitigation strategies
- Sprint Planning - Task allocation and project prioritization
Pipeline Steps
Parse Transcripts
Use
fc.text.parse_transcript() to convert raw text into structured segments with speaker and timing data.Extract Segments
Break down transcripts into individual speaking segments using
explode() and unnest().Apply Semantic Extraction
Use
fc.semantic.extract() to identify structured information from natural language.Implementation
Step 1: Parse Transcripts
The
generic format handles transcripts in the format:Step 2: Extract Speaking Segments
Step 3: Define Extraction Schemas
Step 4: Apply Semantic Extraction
Step 5: Generate Analytics
Expected Output
Action Items Summary
| meeting_id | meeting_type | assignee | task_description | deadline |
|---|---|---|---|---|
| ARCH-2024-1 | Architecture Review | Mike | investigate Redis implementation | next Friday |
| INC-2024-12 | Incident Post-Mortem | Sam | review batch processing code | tomorrow EOD |
| SPRINT-23 | Sprint Planning | Lisa | create migration plan | Wednesday |
Team Workload Distribution
| assignee | assigned_tasks |
|---|---|
| Mike | 2 |
| Lisa | 1 |
| Sam | 1 |
Technology Mentions
| technologies | mention_count |
|---|---|
| Redis | 3 |
| PostgreSQL | 2 |
| JWT | 2 |
Use Cases
Engineering Managers
Track team workload and action item distribution across meetings.
Technical Program Managers
Monitor project decisions and technical debt accumulation.
DevOps Teams
Analyze incident patterns and response procedures.
Architecture Teams
Identify technology adoption trends and system bottlenecks.
Running the Example
Extensions
The example can be extended to:- Integrate with calendar systems for automatic transcript ingestion
- Export to project management tools (Jira, Linear, etc.)
- Build dashboards for engineering metrics
- Create automated follow-up reminders
- Analyze team communication patterns
Technical Notes
- Uses
gpt-4.1-nanofor fast and cost-effective semantic extraction - Handles mixed transcript formats automatically
- Caching with
.cache()prevents re-running expensive LLM operations
