Skip to content

Case Study · Operations

Case Study: Ops Team Turns Meeting Recordings into Action Items

How a remote ops team automated meeting notes to structured action items in Linear — with owner, due date, and human approval before ticket creation.

Professional ServicesNorthline Remote (fictional)Stack: GPT-4.1 mini + Sonnet, Whisper API, Zapier, Linear API, Notion
MeetingsProductivityLinearAutomationHuman-in-the-Loop
Edited by The AIKnowHub team · Editorial team

Results

Meetings processed / week

40

Median notes to draft tickets

15 min

Action item approval rate

81%

Missed commitments (tracked)

-29%

Background

Northline Remote ran 40 internal and client meetings weekly. Notes lived in Google Docs — action items fell through. Linear tickets were created manually days later.

The problem

  • Facilitators hated note-taking
  • Action items lacked owners and dates
  • Client commitments were missed

They built from Meeting Notes to Action Items.

Pipeline

Recording uploaded to shared drive (Zapier trigger)
  → Whisper transcription
  → Mini: extract action items JSON
      { task, owner, due_date, quote, timestamp }
  → Draft Linear tickets in approval queue (Notion table)
  → Team lead approves/edits
  → Zapier creates Linear issues on approve

No auto-create without approval after pilot incidents.

Results (10 weeks)

MetricBeforeAfter
Time from meeting end to tickets2-3 days15-45 min
Action items with owner + date52%94%
Missed client commitments / quarter75

Human gate

81% of drafted tickets approved with minor or no edits. Rejected items usually had wrong owner inference — fixed by adding attendee list to prompt context.

Cost

~$0.40/meeting (Whisper + LLM). 40 meetings/week ≈ $65/month.

Takeaway

Meeting automation works when output matches your ticket schema and humans approve external commitments. Speed without approval creates wrong assignments. See human-in-the-loop patterns.

Lessons learned

  • 01

    Transcript quality beat model choice — invested in room mics before upgrading models.

  • 02

    Structured output with owner, due_date, and verbatim quote reduced approval friction.

  • 03

    Auto-create tickets without approval created 3 wrong assignments in pilot week — approval gate stayed.

  • 04

    Linking each action to transcript timestamp let approvers verify in 10 seconds.

  • 05

    Mini model for extraction, Sonnet for ambiguous owner inference only.

Frequently asked questions

Native tools summarized well but Linear ticket structure was wrong. Custom pipeline matched their action item schema.