Level 10 Meeting Template: A 90-Minute Implementation Guide

More meetings aren't what's required. Instead, teams need one meeting that drives the week.

The pattern is familiar. Monday starts with a leadership sync. Ten minutes disappear waiting for late arrivals. Someone gives a long update that should've been in Slack. A customer issue hijacks the room. Finance wants a decision. Ops wants clarity. Sales wants help. The meeting ends with a vague sense that important things were discussed, but nobody leaves with clean ownership, a ranked issue list, or confidence about what happens next.

That's where a level 10 meeting template earns its keep. Not because the template itself is magical, but because it forces discipline on a team that would otherwise default to status theater. When teams run it properly, the weekly meeting stops being a dumping ground and starts acting like an operating system.

Moving from Meeting Mayhem to Focused Execution

I've seen the same failure mode in startups, service businesses, and larger cross-functional teams. The weekly meeting becomes a mix of reporting, reacting, and revisiting the same unresolved problems. People come prepared to defend their area, not solve company issues. The loudest topic wins. The hardest topic gets postponed.

That style of meeting creates a hidden tax. Leaders walk out with different interpretations of what was decided. Action items live in someone's notebook. The next week, the same issue comes back dressed in slightly different language.

A strong operating rhythm fixes that. If your team hasn't already set clear behavioral expectations, it helps to start with practical ground rules in meetings so the agenda has something solid to sit on.

What changes with an L10

A Level 10 meeting comes from EOS and works because it is not open-ended. EOS describes it as a fixed 90-minute weekly cadence with this sequence: 5 minutes Segue, 5 minutes Scorecard Review, 5 minutes Rock Review, 5 minutes Customer/Employee Headlines, 5 minutes To-Do List Review, 60 minutes IDS, and 5 minutes Conclude. EOS also recommends holding it at the same time and same day each week, starting and ending on time, and using a consistent facilitator and scribe to keep the room on schedule, as outlined in EOS Worldwide's Level 10 meeting guidance.

That structure sounds rigid until you've sat through the alternative.

Practical rule: If your weekly meeting doesn't protect most of its time for solving real issues, it will get consumed by updates.

The biggest shift is mental. Teams stop treating the meeting like a place to “talk about everything.” They use it to review signals quickly, surface what's off track, and spend the bulk of the time solving the few issues that matter most right now.

What works and what fails

Here's the blunt version.

Meeting habit	What happens
Open discussion with no time boxes	Tangents eat the meeting
Status updates in detail	Real decisions get squeezed out
No issue list	Problems stay vague
No scribe	Commitments vanish after the call
Fixed L10 cadence	Teams build weekly accountability

A level 10 meeting template works when the team respects the clock and treats the agenda as operational discipline, not a suggestion. It fails when leaders say they're using the format but keep making exceptions for every tangent.

The Anatomy of the 90-Minute Agenda

The agenda matters because each segment does a different job. If you compress them all into “weekly team updates,” you lose the design logic that makes the meeting effective.

EOS-based guidance describes the Level 10 format as a highly standardized 90-minute agenda broken into Segue, Scorecard, Rock Review, Customer/Employee Headlines, To-Do List, IDS, and Conclude. It also notes that teams typically rate the meeting on a 1 to 10 scale at the end so the process improves week by week, as summarized in this overview of the Level 10 meeting template.

Segue and scorecard

Segue is short for a reason. You're not warming up forever. You're getting people mentally into the meeting and establishing presence. Good news, quick personal wins, brief connection. Then move on.

Scorecard is where a lot of teams go wrong. They turn it into a mini board meeting. Don't. Review the numbers, spot what's off, and drop issues to the list.

If you're still building your operating rhythm, it can help to use AI prompts to generate effective meeting agendas before you lock your recurring weekly format. Just don't let the tool overcomplicate what should remain simple.

Rock review, headlines, and to-dos

Rock Review is a checkpoint on quarterly priorities. The right answer here is often just “on track” or “off track.” If it's off track, it becomes an issue. This is not the place for a ten-minute explanation.

Customer/Employee Headlines gives the room situational awareness. Something notable happened with a customer. Someone on the team needs context. A personnel update matters. Share it, log anything that needs discussion, then keep moving.

To-Do List Review is where accountability becomes visible. Done or not done. Teams that soften this section into long explanations usually have a follow-through problem.

The fastest way to ruin an L10 is to let every section become IDS.

IDS is where the meeting earns its value

IDS means Identify, Discuss, Solve. This is the engine room. It gets the largest block because root-cause problem solving takes time and attention.

The mistake I see most often is teams “discussing” without ever identifying the core issue. They circle around symptoms. A deadline slipped. A customer escalated. A launch is late. None of those statements are necessarily the actual issue. They are signs that something underneath needs to be named cleanly.

Once the issue is identified, the team discusses enough to make a decision. Not enough to satisfy every curiosity in the room. Enough to solve or to assign the next concrete move.

Conclude without drift

The last segment should feel crisp. Confirm to-dos. Make sure owners are clear. Rate the meeting. Note what needs tightening next time.

A simple way to think about the whole agenda is this:

• Segue: Start as a team, not as scattered individuals.
• Scorecard: Check business signals fast.
• Rocks: Protect quarterly priorities from neglect.
• Headlines: Share important context without derailing.
• To-Dos: Verify follow-through in plain language.
• IDS: Solve the highest-value issues.
• Conclude: Leave with clarity, not interpretation.

Why the time boxes matter

A level 10 meeting template is effective because each segment limits behavior.

Segment	What it prevents
Segue	Abrupt, disengaged starts
Scorecard	Opinion-heavy reporting
Rock Review	Quarterly priorities going stale
Headlines	Important context getting buried
To-Do Review	Silent non-completion
IDS	Surface-level problem solving
Conclude	Confusion after the meeting

When a team says the format feels restrictive, that usually means the old meeting allowed too much drift. The point of the template is to force trade-offs. You cannot solve everything in one session. You can solve the right things.

Your Copyable Template and a Filled Example

A useful level 10 meeting template should be easy to paste into Notion, Google Docs, Obsidian, or any team workspace. If it takes effort to reuse, people stop maintaining it.

Teams that want better consistency across meetings usually also benefit from documenting adjacent processes. This is the same discipline behind building operational playbooks, where repeatable work gets turned into a shared system instead of tribal knowledge.

If you want a simpler document-first starting point, this meeting agenda template for Google Docs is useful for adapting the format into a collaborative note.

Blank template

# Level 10 Meeting

**Date:**
**Time:**
**Facilitator:**
**Scribe:**
**Attendees:**

## Segue
- Good news:
- Good news:
- Good news:

## Scorecard
- Metric:
  - Owner:
  - Goal:
  - Actual:
  - Status:
- Metric:
  - Owner:
  - Goal:
  - Actual:
  - Status:
- Metric:
  - Owner:
  - Goal:
  - Actual:
  - Status:

## Rock Review
- Rock:
  - Owner:
  - Status:
- Rock:
  - Owner:
  - Status:

## Customer and Employee Headlines
- Headline:
- Headline:
- Headline:

## To-Do List Review
- To-do:
  - Owner:
  - Due:
  - Status:
- To-do:
  - Owner:
  - Due:
  - Status:

## Issues List
- Issue:
- Issue:
- Issue:

## IDS Notes
### Issue 1
- Identify:
- Discuss:
- Solve:
- To-do owner:
- Due:

### Issue 2
- Identify:
- Discuss:
- Solve:
- To-do owner:
- Due:

### Issue 3
- Identify:
- Discuss:
- Solve:
- To-do owner:
- Due:

## Conclude
- New to-dos:
- Cascading messages:
- Meeting rating:
- Notes for improvement:

Filled example for a fictional company

Below is a realistic example for Innovatech, a software team using the template in a weekly leadership meeting.

# Level 10 Meeting

**Date:** Tuesday
**Time:** 9:00 AM
**Facilitator:** COO
**Scribe:** Chief of Staff
**Attendees:** CEO, COO, Head of Product, Head of Sales, Head of Customer Success

## Segue
- Product launch landing page finally approved
- Customer success manager returned from parental leave
- Sales team closed a delayed renewal last Friday

## Scorecard
- Demo-to-proposal conversion
  - Owner: Head of Sales
  - Goal: Weekly target
  - Actual: Below target
  - Status: Off track
- Open critical bugs
  - Owner: Head of Product
  - Goal: Weekly target
  - Actual: Above target
  - Status: Off track
- Onboarding completion time
  - Owner: Head of Customer Success
  - Goal: Weekly target
  - Actual: On target
  - Status: On track

## Rock Review
- Release self-serve onboarding flow
  - Owner: Head of Product
  - Status: Off track
- Improve enterprise renewal process
  - Owner: Head of Customer Success
  - Status: On track

## Customer and Employee Headlines
- Enterprise prospect requested security review sooner than expected
- Two support agents flagged confusion in the escalation path
- Positive customer feedback on the new analytics dashboard

## To-Do List Review
- Finalize pricing FAQ
  - Owner: Head of Sales
  - Due: Last meeting
  - Status: Done
- Publish onboarding checklist draft
  - Owner: Head of Customer Success
  - Due: Last meeting
  - Status: Not done
- Confirm release rollback process
  - Owner: Head of Product
  - Due: Last meeting
  - Status: Done

## Issues List
- Demo conversion slipped for the second week
- Self-serve onboarding rock is off track
- Support escalation path is unclear
- Security review requests are slowing deals

## IDS Notes
### Issue 1
- Identify: Reps are getting demos booked, but follow-up quality is inconsistent
- Discuss: Messaging differs by segment and proposal turnaround is uneven
- Solve: Create one post-demo follow-up standard and train reps this week
- To-do owner: Head of Sales
- Due: Next meeting

### Issue 2
- Identify: Onboarding rock is delayed because product and success teams disagree on scope
- Discuss: Product wants a smaller release, success wants a broader workflow
- Solve: Lock phase-one scope by Thursday and move remaining items to backlog
- To-do owner: COO
- Due: Thursday

### Issue 3
- Identify: Support agents don’t know when to escalate technical issues
- Discuss: Current documentation is outdated and ownership is fuzzy
- Solve: Publish a one-page escalation map and review it in team standup
- To-do owner: Head of Customer Success
- Due: Friday

## Conclude
- New to-dos:
  - Head of Sales to publish follow-up standard
  - COO to approve phase-one onboarding scope
  - Head of Customer Success to publish escalation map
- Cascading messages:
  - Product and Success will align on phase-one only
- Meeting rating:
  - 8
- Notes for improvement:
  - Scorecard review ran too long

A good template doesn't just capture discussion. It makes ownership impossible to hide.

Essential Facilitation Skills for Meeting Success

A level 10 meeting template by itself won't save a weak meeting. The facilitator does that.

I've watched teams adopt the exact right agenda and still get poor results because no one in the room was willing to enforce the rules. Once that happens, the meeting becomes politely chaotic. People interrupt the sequence, solve issues too early, and turn every update into a debate.

The facilitator's real job

The facilitator is not there to dominate the room. The job is to protect the format, keep energy clean, and force clarity.

The scribe has an equally important role. If decisions, dropped issues, and to-dos aren't captured in real time, the meeting loses integrity. Teams remember conversations selectively. Written notes don't.

When leaders want to improve how they guide teams under pressure, I often point them toward practical reading on tactics for calm project leadership. The overlap is real. Calm leaders run better IDS conversations.

How to run IDS without losing the room

Noota's guide highlights a core discipline of the format: during IDS, the team should surface issues, rank them, and work only the top three priorities instead of trying to solve everything. It also emphasizes using a pre-built agenda with fields for good news, scorecard metrics, rocks, to-dos, and issues so the meeting stays on track and captures action items, as explained in this guide to the Level 10 meeting template.

That point matters because many teams confuse openness with effectiveness. They think a good meeting lets every issue breathe equally. It doesn't. A good meeting makes hard choices about what deserves this week's attention.

A practical breakdown looks like this:

• Surface the issues: Pull from scorecard misses, off-track rocks, headlines, and incomplete to-dos.
• Rank them: Don't debate endlessly. Decide what matters most.
• Work the top items only: If you try to solve everything, you solve nothing well.
• Assign a concrete next move: Every solved issue should end with ownership.

Here's a useful visual walkthrough of facilitation in action:

<iframe width="100%" style="aspect-ratio: 16 / 9;" src="https://www.youtube.com/embed/tAIRlnnGgO0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>

What skilled facilitators stop immediately

Poor facilitation usually shows up in predictable ways.

Failure mode	Correction
Team debates symptoms	Ask for the underlying issue
One person dominates	Pull in quieter voices directly
Updates become discussions	Drop the item to IDS
No clear close on a topic	Restate the decision and owner

If the facilitator won't interrupt drift, the agenda is decorative.

The best facilitators are polite, but they're not passive. They keep the team honest about what is being decided, what is being deferred, and who owns the next step.

Integrate Your L10 Meeting into Your Workflow

Most articles stop at the agenda. That's where the actual operational problem starts.

A team can run a clean L10 and still get weak results if the outputs stay trapped in meeting notes. Rocks, to-dos, and IDS decisions need to move into the systems where work happens. Otherwise the meeting becomes a parallel universe. It feels productive in the room, then disappears by afternoon.

Where teams break the chain

This is a common gap. A 2023 enterprise collaboration survey noted that 60% of teams using structured meeting formats still struggled with action-item follow-through because meeting artifacts stayed in meeting-specific formats rather than integrated backlogs, according to Notion's discussion of Level 10 meeting workflow gaps.

That finding matches what a lot of operators already know from experience. Good meeting hygiene does not automatically produce execution hygiene.

The connected workflow that actually works

A modern L10 should feed other systems immediately. That usually means some version of this flow:

1. Capture the meeting
   Record or transcribe the session so no one relies on memory.

2. Structure the outputs
   Separate scorecard flags, rock status, open issues, solved decisions, and new to-dos.

3. Assign ownership cleanly
   Every action item needs one owner, not a department.

4. Push tasks into execution tools
   Move work into Notion, Asana, Trello, Jira, or another active system.

5. Bring unresolved items back next week
   Prior issues should not vanish between meetings.

If you want a practical model for the handoff from note to action, this guide on tracking action items is a useful companion process.

Where AI tools fit

AI can make the level 10 meeting template much more useful. Instead of manually rewriting notes after the call, teams can use meeting transcription and summarization tools to turn the raw conversation into structured outputs.

For example, SpeakNotes can capture meeting audio, transcribe it, generate structured summaries, and help extract action items that can then be reviewed and pushed into a team workflow. The operational value isn't “better notes.” It's reducing the lag between decision and execution.

What matters most is not the brand. It's the workflow design.

• If your notes stay in a doc, people forget them.
• If your decisions become tasks, teams can track them.
• If unresolved issues return automatically, the L10 becomes a weekly control system.

The meeting should be one node in your operating workflow, not a standalone artifact.

That's the difference between using an L10 as a meeting format and using it as an execution rhythm.

Frequently Asked Questions about Level 10 Meetings

Teams usually hit the same few questions once they've run the format for a couple of weeks. Most of them come down to discipline, not complexity.

What if we can't solve an issue during IDS

Don't force closure just to feel productive. If the team can't solve it in the room, decide the next best action. That might be assigning research, pulling in a missing decision-maker, or narrowing the issue statement so it can be solved next week.

What you should not do is let the issue dissolve into general discussion. The point is to leave with a next move.

Can creative teams use a rigid format

Yes, if they understand what the structure is doing. Creative teams still need priorities, issue triage, and follow-through. The format doesn't kill creative work. It stops creative teams from letting operational confusion drain their energy.

The agenda should stay fixed even if the content is more exploratory.

How do remote or hybrid teams run this well

Use one shared agenda on screen, one facilitator, and one visible issue list. Remote teams struggle when people can't see what has been captured, what has been dropped to IDS, or what was assigned. A shared workspace matters more than ever in a distributed setting.

Keep the meeting behavior tight:

• Cameras on when possible: It's easier to read engagement.
• One source of truth: Don't split notes across chat, docs, and private notebooks.
• Clear verbal closes: Remote meetings create more ambiguity if the facilitator doesn't summarize decisions out loud.

How many metrics should go on the scorecard

Keep it narrow. EOS-related guidance recommends tracking only 5 to 15 key numbers in the scorecard, focused on a quick pulse of business health and activity-based leading indicators. In practice, strong templates also use accountability targets such as 95%+ attendance for core members, an 80%+ issue-resolution rate, and average meeting length trending toward 90 minutes or less, according to Strety's guide to Level 10 meeting agendas.

That guidance matters because overloaded scorecards create noise. If everything is important, nothing stands out.

How long does it take to get good at this

Usually a few meetings just to stop breaking the format, then longer to get good at IDS. The first sign of progress is not that the meeting feels elegant. It's that the team starts bringing sharper issues and leaving with clearer ownership.

That's when the level 10 meeting template stops feeling like a script and starts functioning like muscle memory.

---

If your team is already running Level 10 meetings, the next improvement usually isn't a new agenda. It's better capture and follow-through. SpeakNotes can help by turning meeting audio into structured notes and action items so your weekly L10 connects more cleanly to the work that happens after the meeting ends.