Level 10 meeting template (EOS weekly meeting, free)

What’s in the template

The minutes open with these details:

• Company
• Team (e.g. leadership team)
• Date
• Time started (same day and time each week)
• Time ended
• Facilitator
• Scribe
• Present
• Absent
• Quarter (for the rocks being reviewed)

Then the body follows the meeting in this order:

1. 1. Segue (5 minutes) — Each person shares one piece of personal good news and one piece of business good news. Note that it happened; do not minute the content.
2. 2. Scorecard review (5 minutes) — Five to fifteen weekly numbers, each with an owner and a goal. Read each as on track or off track. Off-track numbers go to the issues list. No discussion here.Measurable: · Owner: · Goal: · This week: · On track / off track:
3. 3. Rock review (5 minutes) — Each quarterly rock, company and individual, reported as on track or off track by its owner. Off-track rocks go to the issues list.Rock: · Owner: · On track / off track:
4. 4. Customer and employee headlines (5 minutes) — One-sentence headlines, good or bad, about customers and employees. Anything that needs discussion goes to the issues list.
5. 5. To-do list (5 minutes) — Last week's to-dos, each reported done or not done. To-dos are seven-day commitments; aim for 90 percent done. A to-do not done for two weeks becomes an issue.To-do: · Owner: · Done / not done:
6. 6. IDS: issues list (60 minutes) — List every issue, pick the three most important, then take them one at a time: identify the real issue, discuss it once, solve it. A solved issue produces a to-do. Then pick the next.Issue: · Identified (the real issue): · Solution: · To-do created (owner, due in 7 days):
7. 7. Conclude (5 minutes) — Recap the new to-dos, agree what to communicate to the rest of the company and who will do it, and each person rates the meeting from 1 to 10.To-dos recapped: · Cascading messages (what, to whom, by whom): · Ratings (each person, 1 to 10): · Average:

At the end: to-do list and issues list, as tables you can keep across meetings.

The template

Download it as a Word file, or copy the text version into your own document.

Level 10 Meeting Notes

Company: 
Team (e.g. leadership team): 
Date: 
Time started (same day and time each week): 
Time ended: 
Facilitator: 
Scribe: 
Present: 
Absent: 
Quarter (for the rocks being reviewed): 

1. Segue (5 minutes)
   [Each person shares one piece of personal good news and one piece of business good news. Note that it happened; do not minute the content.]

2. Scorecard review (5 minutes)
   [Five to fifteen weekly numbers, each with an owner and a goal. Read each as on track or off track. Off-track numbers go to the issues list. No discussion here.]
   Measurable:
   Owner:
   Goal:
   This week:
   On track / off track:

3. Rock review (5 minutes)
   [Each quarterly rock, company and individual, reported as on track or off track by its owner. Off-track rocks go to the issues list.]
   Rock:
   Owner:
   On track / off track:

4. Customer and employee headlines (5 minutes)
   [One-sentence headlines, good or bad, about customers and employees. Anything that needs discussion goes to the issues list.]

5. To-do list (5 minutes)
   [Last week's to-dos, each reported done or not done. To-dos are seven-day commitments; aim for 90 percent done. A to-do not done for two weeks becomes an issue.]
   To-do:
   Owner:
   Done / not done:

6. IDS: issues list (60 minutes)
   [List every issue, pick the three most important, then take them one at a time: identify the real issue, discuss it once, solve it. A solved issue produces a to-do. Then pick the next.]
   Issue:
   Identified (the real issue):
   Solution:
   To-do created (owner, due in 7 days):

7. Conclude (5 minutes)
   [Recap the new to-dos, agree what to communicate to the rest of the company and who will do it, and each person rates the meeting from 1 to 10.]
   To-dos recapped:
   Cascading messages (what, to whom, by whom):
   Ratings (each person, 1 to 10):
   Average:

To-do list
No. | To-do | Owner | Due (7 days) | Done

Issues list
No. | Issue | Raised by | Status (open / solved / dropped)

Example: filled-in level 10 meeting

What the template looks like once it’s been used. The organisation and people are made up.

Action items

Tips for level 10 meeting

• Keep the issues list in the same document from week to week and add to it between meetings; the meeting starts with the list already populated.
• Write to-dos as a verb and an outcome: "reissue listings at the new rate", not "hiring". The Friday check is then unambiguous.
• Note the time each section ended for the first two months. The notes will show exactly where the meeting drifts.
• Record off-track scorecard numbers with the actual figure, not just the status, so the trend is visible across weeks.
• If the same issue is solved twice in a quarter, the first solution was not the real issue. Write that down as the new issue.

Related templates

• Team meeting minutes template — The weekly meeting of one team: last week's numbers, blockers, decisions and this week's priorities.
• Staff meeting minutes template — The regular all-staff meeting of an office, clinic or branch: updates, policy changes, schedules and recognition.
• Project meeting minutes template — The weekly status record: where each workstream stands, which milestones moved, what changed on the risk log and what was decided.
• Meeting notes with action items template — Notes built around a running action register, for recurring meetings where last week's actions are this week's first agenda item.
• All meeting minutes templates

Or let the notes write themselves

A template helps when you’re the one typing. If you’d rather not be, an AI note taker can draft the summary and action items for you. Most send a bot into the call; QuietNote captures from your own computer instead, so nothing joins the meeting and you decide when capture starts. It’s in private beta. Whatever you use, read the draft before you send it, and tell attendees you’re recording where the rules require it.