The problem
Meetings generate hours of audio and almost no usable record: someone takes hurried notes, half the decisions are forgotten, and action items evaporate. Manual minutes are slow and biased toward whoever writes them. This project automates the full chain — speech-to-text, dialogue summarization, and structured extraction — using open models and public meeting data. Whisper transcribes the recording, then a BART summarizer fine-tuned on dialogue summaries (SAMSum) produces the minutes, while a rule-and-model extraction stage identifies action items ("Rahul will share the API spec by Friday") and explicit decisions. Training and evaluation use the AMI Meeting Corpus, the standard public corpus of instrumented meetings with reference summaries, so every claim about quality is grounded in a real benchmark. The demo runs the pipeline on a realistic sample meeting with four speakers.
Uploads a meeting recording and reviews the generated minutes.
Follow the working sequence
How it works
- Meeting audio is transcribed with Whisper (base/small), producing timestamped segments that are grouped into speaker turns.
- Speaker turns are formatted as a dialogue transcript and chunked to fit the summarizer's input length, with overlap to preserve context.
- The fine-tuned BART model generates an abstractive summary per chunk; chunk summaries are merged into the final minutes.
- Action items are extracted by scanning for commitment patterns (future-tense verbs, "will", "by
", assignee names) and verified with an NER pass for person names and dates. - Decision sentences are detected from agreement patterns and collected with their surrounding context into the decision log.
- The demo renders all four artifacts — transcript, minutes, action items, decisions — from one pipeline run, with ROUGE scores shown for the summarizer.
Tech stack:
- Python 3.11, openai-whisper (ASR)
- Hugging Face Transformers, BART-large (facebook/bart-large)
- SAMSum dialogue summaries (summarizer fine-tuning)
- AMI Meeting Corpus (evaluation)
- spaCy (NER for owners and dates)
- Flask + HTML/CSS/JS (demo)
- ROUGE scoring (evaluation)
Dataset & model details
- Dataset: AMI Meeting Corpus (Carletta et al., IDIAP/Edinburgh) — 100 hours of instrumented meetings with manual transcripts and reference summaries; plus SAMSum (Gliwa et al., 2019) — ~16k messenger-style dialogues with human-written summaries for fine-tuning. Sources: groups.inf.ed.ac.uk/ami/corpus and Hugging Face datasets.
- Task: (1) ASR: audio → transcript; (2) abstractive dialogue summarization: multi-speaker transcript → minutes; (3) extraction: transcript → action items and decisions.
- Model: Whisper (base/small) for transcription; BART-large fine-tuned on SAMSum for summarization; spaCy NER + dependency patterns for action-item/decision extraction.
- Metrics: Word Error Rate (WER) for transcription on AMI; ROUGE-1/2/L for summaries against AMI reference summaries — both reported as design targets from the training run, never pre-claimed.
| Parameter | Value |
|---|---|
| Audio input | WAV/MP3, 16 kHz mono recommended |
| Transcription | Whisper base/small, WER design target on AMI |
| Summarizer | BART-large fine-tune (~406M parameters) |
| Summary ROUGE | ROUGE-1/2/L design targets on AMI (reported after training) |
| Pipeline latency | Approximately 1–3 min per 30-min meeting on GPU (expected) |
| Demo | Single-file web app with preloaded sample meeting |
| Fine-tuning | Approximately 3–6 h on a single GPU (expected) |
Project features
- [Whisper transcription] OpenAI's Whisper transcribes meeting audio to timestamped text; the demo shows the full speaker-labeled transcript it works from.
- [Abstractive minutes generation] A BART-large model fine-tuned on dialogue-summary data writes concise minutes in natural prose, not stitched-together quotes.
- [Action-item extraction] Sentences containing commitments are detected and paired with owners and deadlines using named-entity recognition plus dependency patterns.
- [Decision log] Explicit decisions ("we agreed to…", "let's go with…") are collected into a separate decision register with the discussion context.
- [Speaker-aware pipeline] Speaker labels flow through every stage, so minutes attribute statements and action items carry an owner.
- [ROUGE-evaluated] Summarizer quality is measured with ROUGE-1/2/L against AMI reference summaries; the report shows the scores honestly.
- [Live web demo] Upload-style demo walks a sample meeting through transcript → minutes → action items → decisions in one screen.
What is included
- Full pipeline source (transcription → summarization → extraction)
- Fine-tuned BART summarizer weights
- Training notebook (SAMSum fine-tuning, AMI evaluation, ROUGE scoring)
- Web demo with a realistic preloaded 4-speaker meeting
- Evaluation report (WER + ROUGE tables on AMI)
- Project report PDF (background, ASR + summarization theory, methodology, results)
- PPT presentation for final review
- Viva Q&A preparation document (Whisper, BART, ROUGE, abstractive vs extractive)
Limitations & prerequisites
- Whisper accuracy drops with heavy accents, crosstalk and poor microphones; the report documents WER on AMI honestly.
- Abstractive summarizers can hallucinate details — the demo keeps the source transcript one click away for verification.
- Action-item extraction is pattern-assisted and can miss implied commitments; it is an aid, not a replacement for a human note-taker.
- ROUGE scores are design targets until the training run executes; the report records the achieved figures.
- Long meetings are chunked, so cross-chunk references may be summarized less coherently.
Frequently Asked Questions
Which datasets are used?
The AMI Meeting Corpus (100 hours of real meetings with reference summaries) for evaluation and SAMSum (16k dialogues with summaries) for fine-tuning the summarizer — both public and standard for this task.
Is the summary extractive or abstractive?
Abstractive — BART writes fresh prose rather than copying sentences, which is why the minutes read naturally. The demo also keeps the extractive transcript visible for verification.
How are action items found?
Commitment language ("will", "by Friday", named owners) is detected with dependency patterns and spaCy NER for people and dates, then presented as an owner–task–deadline table.
Can I run it on my own meeting recording?
The pipeline accepts WAV/MP3; the demo ships with a preloaded sample meeting so it works instantly in a browser.
What hardware does training need?
A single GPU with 12GB+ VRAM for BART fine-tuning; transcription and inference run on CPU, slower but usable.
Is this project suitable for a final-year project?
Yes — for Computer Science, IT and AI/ML programs. It chains speech recognition, transformer summarization and information extraction into one demonstrable system. Suitable for B.E./B.Tech final-year projects in Computer Science, IT and AI & Machine Learning.
Components & software requirements
- Python 3.11, openai-whisper (ASR)
- Hugging Face Transformers, BART-large (facebook/bart-large)
- SAMSum dialogue summaries (summarizer fine-tuning)
- AMI Meeting Corpus (evaluation)
- spaCy (NER for owners and dates)
- Flask + HTML/CSS/JS (demo)
- ROUGE scoring (evaluation)
Dataset & model details
- Dataset: AMI Meeting Corpus (Carletta et al., IDIAP/Edinburgh) — 100 hours of instrumented meetings with manual transcripts and reference summaries; plus SAMSum (Gliwa et al., 2019) — ~16k messenger-style dialogues with human-written summaries for fine-tuning. Sources: groups.inf.ed.ac.uk/ami/corpus and Hugging Face datasets.
- Task: (1) ASR: audio → transcript; (2) abstractive dialogue summarization: multi-speaker transcript → minutes; (3) extraction: transcript → action items and decisions.
- Model: Whisper (base/small) for transcription; BART-large fine-tuned on SAMSum for summarization; spaCy NER + dependency patterns for action-item/decision extraction.
- Metrics: Word Error Rate (WER) for transcription on AMI; ROUGE-1/2/L for summaries against AMI reference summaries — both reported as design targets from the training run, never pre-claimed.
Delivery information
Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.
Support terms
Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.
Download free synopsis (PDF)
Enter your name and WhatsApp number — the synopsis PDF downloads immediately. We may send occasional project updates on WhatsApp; no spam.