A Level 10 meeting agenda template needs more than time slots. It needs a way to follow a concern from its source into the discussion and then into a separately recorded action. A flagged measure is not a root cause, and an action proposal is not evidence that the issue was resolved.
This guide uses an original fictional preparation packet for a team already maintaining EOS-style operating records. Keep your own Scorecard, Rock records, Issues List, and To-Do List as the working sources. Actual measurements, discussion, decisions, and meeting ratings belong to the team; leave them unfilled when preparing the example.
Use the reference structure with clear attribution
Level 10 Meeting™ is an EOS Worldwide trademark. The official leadership-meeting reference uses seven sections over 90 minutes. It routes concerns into an Issues List for IDS—Identify, Discuss, Solve—and closes with follow-up review. Consult the official materials for the method; the fictional records here are an original preparation aid. EOS Worldwide: Level 10 Meeting
| Reference section | Minutes |
|---|---|
| Segue | 5 |
| Scorecard | 5 |
| Rock Review | 5 |
| Customer and Employee Headlines | 5 |
| To-Do List | 5 |
| IDS | 60 |
| Conclude | 5 |
The six five-minute sections total 30 minutes; adding 60 gives 90. That verifies the time budget, not the quality of a meeting or a participant's performance. Do not prefill a rating of ten because the agenda uses the Level 10 name.
Before the meeting, connect these sections to the maintained records that participants will actually use. A packet with attractive headings but no source period, current goals, or prior commitments leaves the team reconstructing the evidence while its discussion time runs down.
Confirm what the weekly number means
Use the following fictional record:
| M01 field | Prepared value |
|---|---|
| Measure | Document reviews |
| Target | 10 |
| Observed number | 8 |
| Source reference | E01, fictional evidence reference |
| Measurement period | TO CONFIRM |
| Counting definition and matching units | TO CONFIRM |
If the target and observation refer to the same period and definition, the shortfall is two reviews. With the period unconfirmed, treat the comparison as provisional. The arithmetic 10 − 8 = 2 cannot establish that the two numbers cover the same week or count the same kind of completed review.
An evidence reference is useful only when the actual source can be inspected. E01 is a placeholder in this example, not a document we have verified. In the real packet, retain the source location, period, and counting definition so someone can reproduce the observation.
Even a confirmed shortfall does not tell you why it happened. “The team lacked capacity” is a hypothesis until evidence supports it. Other explanations might require investigation; do not manufacture one to make the issue record feel complete.
Create I01 with the question: “Which reviews were blocked, and what evidence explains it?” Link it to M01 and E01. Record the observed values, missing period, and evidence question. Leave the actual discussion blank until it happens.
Keep the Rock and prior To-Do independent
The same packet includes R01, a quarterly documentation goal, and T01, a prior To-Do. Neither can inherit a status from M01's eight reviews.
| Record | Known in this fictional packet | What remains unresolved |
|---|---|---|
| R01 | Quarterly documentation goal | Owner's current confidence and supporting evidence |
| T01 | Prior follow-up item exists | Completion receipt or other actual completion evidence |
| I01 | M01 comparison raises an evidence question | Cause, discussion, and agreed resolution |
Keep R01's confidence unknown until the responsible owner supplies it. The weekly count does not establish progress against the complete quarterly goal. Keep T01's completion unverified until its result is supported; a proposal to do something now cannot prove a prior commitment was completed.
“Unverified” describes a preparation gap. It is not a third invented official EOS status or proof that the task failed. Bring the question to the actual review, record the team's supported state, and retain the evidence used. If an R01 or T01 concern becomes a separate issue, give it its own identifier and source link rather than forcing it into I01 merely because all three involve documentation.
Separate issue resolution from the proposed action
An original IDS preparation record can hold these fields without writing the meeting's answer in advance:
| I01 field | Preparation entry |
|---|---|
| Source | M01; fictional reference E01 |
| Observed fact | Target 10; observed 8; period and definition unconfirmed |
| Question | Which reviews were blocked, and what evidence explains it? |
| Cause hypothesis | Not established |
| Actual discussion | Blank |
| Proposed follow-up | A01: locate the review records |
| A01 owner and due date | TO CONFIRM |
| Actual agreement and decision evidence | Blank |
| Issue solution state | Unresolved |
A01 has an action identifier because it may become a commitment with an owner and date. I01 keeps its issue identifier because the concern may remain open while that evidence is gathered. Preserve both links: A01 → I01 → M01.
Creating A01 does not make it agreed, completed, or sufficient to solve I01. If the team agrees to the follow-up, record the actual owner, due date, and agreement. If the records later become available, record the evidence and the actual conclusion separately. Finding records may enable a discussion without itself resolving the underlying problem.
At the close, inspect each proposed follow-up for missing ownership or timing. A line reading “someone will investigate” is still missing a commitment. Preserve that gap visibly instead of choosing a person's name or tomorrow's date on their behalf. Leave any actual communication decision and meeting rating blank until supplied.
Copy this prompt to prepare the packet
Prepare an original fictional weekly operating-review packet for a team already maintaining EOS-style records. Attribute Level 10 Meeting to EOS Worldwide and link https://www.eosworldwide.com/level-10-meeting. Do not copy its downloadable packet or imply endorsement, certification, or an installed EOS system.
Include the reference leadership agenda: Segue 5 minutes, Scorecard 5, Rock Review 5, Customer and Employee Headlines 5, To-Do List 5, IDS 60, Conclude 5. Check the sum is 90. Keep private headlines, actual discussion, decisions, communication instructions, and meeting ratings blank. Do not invent an effectiveness or employee-performance score.
Build original tables for source measures, issue preparation, and separate proposed actions. Use M01: document reviews, target 10, observed 8, fictional source reference E01. Period, counting definition, and matching units are TO CONFIRM. A shortfall of 2 is conditional on a confirmed common period and definition. E01 is a fictional placeholder, not inspected evidence. Do not infer a capacity problem or other root cause.
Link M01 to I01: “Which reviews were blocked, and what evidence explains it?” Include observed values, sourceMetricID M01, evidence reference E01, missing evidence, cause hypothesis not established, actual discussion blank, actual agreement blank, and solution state unresolved.
Include R01, a quarterly documentation goal with owner confidence and supporting evidence unknown. Do not mark it on-track based on 8/10. Include prior To-Do T01 with completion evidence absent and preparation status unverified; do not label it done from a proposal. Explain that unknown preparation evidence is not a new official EOS status or proof of failure. Separate any additional issue by its own ID and source.
Propose A01: locate the review records. Link it to I01 and M01. Owner and due date remain TO CONFIRM; actual agreement, completion, and resolution evidence remain blank. A proposed action is neither an accepted commitment nor a solved issue. Preserve that distinction if evidence is later supplied.
Keep the team's native agenda, Scorecard, Rock, Issues List, and To-Do records authoritative. An optional sanitized HTML reading companion may show the M01-to-I01-to-A01 trace and missing evidence, without automatic updates, notifications, saved decisions, or a claim that a meeting occurred. End with checks for the 90-minute sum, conditional comparison, distinct IDs, unresolved owner/date/confidence/completion, and absence of invented outcomes.
Present the evidence chain beside the working records
Maintain the packet and its decisions in the team's established tools. When someone asks why A01 exists, the record should lead back to I01's question and M01's evidence gap. When someone asks whether I01 is solved, it should show the actual conclusion and supporting evidence—or clearly retain the unresolved state.
NOS can save and render HTML. A sanitized HTML companion can make that chain readable: the conditional 10-versus-8 comparison, the unresolved issue, and the proposed follow-up with missing owner and date. Keep private headlines and source records out of the reading view unless appropriate to include. Rendering the packet does not update a Scorecard, assign a task, notify participants, or establish a meeting outcome.
Explore NOS with the evidence chain you have prepared. A useful meeting packet lets the next reader distinguish what was observed, what still needs an answer, and what the team actually agreed to do.