Template

L10 meeting template (EOS Level 10)

The fastest way to run L10 consistently: same agenda, same timeboxes, minutes that actually stick.

Build a customized L10 pack
Template
Copy → paste → ship
# EOS Level 10 (L10) Meeting

**Team:** {Team}
**Date/Time:** {YYYY-MM-DD} · {Start–End}
**Facilitator:** {Name}
**Attendees:** {Names}

---
## Agenda (90 minutes)
- Segue (5)
- Scorecard (5)
- Rock review (5)
- Headlines (5)
- To-dos (5)
- IDS (60)
- Conclude (5)

---
## Segue (5)
- Personal best:
- Professional best:

---
## Scorecard (5)
Metric | Goal | Actual | On track? (Y/N)
---|---:|---:|:---:
{Metric} | {Goal} | {Actual} | {Y/N}

---
## Rock Review (5)
Rock | Owner | Status (On/Off) | Notes
---|---|---|---
{Rock} | {Owner} | {On/Off} | {Notes}

---
## Headlines (5)
- Customer headline:
- Employee headline:

---
## To-dos (5)
Owner | To-do | Due | Done?
---|---|---|:---:
{Owner} | {To-do} | {Due} | {Y/N}

---
## IDS (60)
Issue | Owner | Priority | Notes / Solve
---|---|---|---
{Issue} | {Owner} | {High/Med/Low} | {Notes}

---
## Conclude (5)
- New to-dos (recap):
- Cascading messages:
- Rate the meeting (1–10): {Score}
How to use
  • Timebox aggressively — save stories for IDS.
  • Only track decisions and to-dos in minutes.
  • Ship the recap within 30 minutes after the call.
Common mistakes
  • Turning IDS into status updates.
  • Capturing notes without owners + due dates.
  • Letting the scorecard become a debate instead of a signal.
AI note‑taker fit
  • L10s are name + number dense — validate the Names and Numbers tests.
  • If overlap is common, diarization errors will poison to-do ownership.
  • Prioritize export/copy so your L10 recap can ship to Slack/Docs.
Want the cheapest tool that can populate this template?
Use Tool Finder, then validate the failure mode that matters.