An EOS meeting agenda template is a repeatable outline for the weekly Level 10 Meeting used in the Entrepreneurial Operating System (EOS). It usually allocates 90 minutes to team check-ins, measurable results, quarterly priorities, a to-do review, problem-solving, and clear next steps.
What an EOS Meeting Is
EOS is a business operating framework that gives a leadership team shared tools and routines for managing priorities and addressing obstacles. Its weekly leadership meeting is commonly called a Level 10 Meeting because participants rate the meeting at the end on a scale of one to ten. The purpose is not to produce a perfect score every week; the rating is a quick signal about whether the meeting was focused and useful.
The agenda is designed to create a predictable rhythm. Routine updates are kept brief, while most of the meeting is reserved for the issues that are blocking progress. The format can be used by an EOS leadership team and adapted for another recurring team meeting, but the terms and measures should be understood by everyone using it. It is not simply a general-purpose meeting checklist: the sequence is intended to connect weekly activity with longer-term priorities.
The Standard 90-Minute Agenda
A common EOS Level 10 agenda has seven timed sections. The times below add up to 90 minutes. Treat them as a disciplined starting point, not a reason to rush an important decision or let discussion run without an owner.
- Segue — 5 minutes: Each person shares a brief personal and professional good news item. This helps the team arrive mentally and build connection without turning the opening into a long round of status reports.
- Scorecard — 5 minutes: Review weekly numbers against their targets. The focus is on which measurable indicators are on track or off track, not on explaining every detail behind each number.
- Rock review — 5 minutes: Check the status of the quarter’s most important priorities, commonly called Rocks in EOS. A quick on-track or off-track review surfaces work that may need attention.
- Customer and employee headlines — 5 minutes: Share important positive or concerning feedback, events, or information from customers and employees. Headlines are short; a substantial problem can be added to the Issues List for later discussion.
- To-do list — 5 minutes: Review commitments from the prior meeting. A to-do is generally a specific action expected to be completed within a week, rather than an open-ended project.
- IDS — 60 minutes: Identify, Discuss, and Solve the highest-priority issues. The team selects issues, gets to their underlying cause, agrees on a practical solution, and assigns any resulting actions.
- Conclude — 5 minutes: Recap new to-dos, decide what information needs to be communicated to others, and have participants rate the meeting. Confirm who will share any agreed message and by when.
Timing matters because the short review sections protect time for IDS. If the team spends 20 minutes debating scorecard details, it may leave the most consequential obstacle unresolved. Capture that detail as an issue and return to it during the problem-solving portion.
How the EOS Components Fit Together
The recurring agenda works best when the team maintains a few basic tools between meetings. A scorecard contains a small set of weekly measurable indicators, each with a target and a person accountable for reporting it. A Rock is a major priority for the quarter, with a clear owner and a way to judge whether it is on track. The Issues List holds problems, opportunities, and questions that need team attention.
These tools answer different questions. The scorecard asks whether the business is seeing the expected weekly signals. The Rock review asks whether important quarterly work is progressing. To-dos record short, concrete commitments. The Issues List is a parking place for items that deserve discussion, not a second set of vague tasks. Keeping these distinctions clear prevents the meeting from becoming a round of project updates.
IDS is the mechanism for turning the Issues List into decisions. The team first identifies what is actually wrong, then discusses it openly, and finally solves it by agreeing on a decision or next action. The sequence discourages jumping to the first proposed fix before the group understands the issue. Not every topic will be fully resolved in one sitting; if further work is needed, assign an owner and a defined next step.
EOS Meeting Agenda Template
| Meeting details | |
|---|---|
| Date and time | |
| Attendees | |
| Facilitator | |
| Agenda section | Minutes | Owner or lead | Notes, status, or outcome |
|---|---|---|---|
| Segue | 5 | ||
| Scorecard | 5 | ||
| Rock review | 5 | ||
| Customer and employee headlines | 5 | ||
| To-do review | 5 | ||
| IDS: Identify, Discuss, Solve | 60 | ||
| Conclude: recap, messages, meeting rating | 5 |
| Issues to prioritize for IDS | |||
|---|---|---|---|
| Issue | Priority | Owner | Decision or next step |
| New to-dos | |||
|---|---|---|---|
| Action | Owner | Due by | Complete next week? |
| Meeting rating, 1–10 | Message to cascade | Who will share it? |
|---|---|---|
Fictional Sample: How to Fill It In
The following example is fictional and shows the level of detail that makes the template practical. Suppose a small team has a quarterly Rock to prepare a new customer onboarding process. During the scorecard review, the team sees that the number of new customers starting on schedule is below its target. The Rock owner reports that the process draft is progressing, but a required handoff between two roles remains unclear.
The team records the metric as off track without using the five-minute scorecard slot to investigate every cause. It adds the handoff problem to the Issues List. During IDS, the team agrees that the root issue is the absence of a named owner for the handoff, assigns fictional team member Maya to propose a clear handoff step by Friday, and records that commitment as a to-do. At the next meeting, the group checks whether Maya completed it and whether the scorecard signal has changed. The value of the record is that a concern becomes an owned action rather than an item everyone assumes someone else will handle.
Preparing and Running the Meeting
Preparation prevents the agenda from being consumed by information gathering. Before the meeting, the facilitator can ask participants to update their numbers, Rock status, and to-dos. Team members should add issues as they arise during the week instead of relying on memory at the meeting. An issue can be phrased simply, such as “handoff ownership is unclear” or “delivery dates are slipping,” rather than as a lengthy proposed solution.
At the start, confirm that the essential participants are present and that the team has the current scorecard, priorities, and issue list available. During reviews, keep reports concise and avoid solving issues prematurely. When a point needs more time, capture it on the Issues List. In IDS, choose the issues with the greatest importance to the team, not necessarily the ones raised most recently or by the most senior person.
A facilitator helps the group follow the sequence, manage time, and make sure decisions are recorded. The facilitator does not have to be the person with the most authority, and the role can rotate if that works for the group. Before moving on from an issue, state the decision plainly, identify the owner of any action, and set a realistic due date. Close by reading the to-dos back so each person can correct a misunderstanding before the meeting ends.
Adapting the Template Without Losing Its Purpose
Teams may need to adjust wording, note-taking fields, or the people invited, especially when using the agenda outside an EOS leadership team. Keep the weekly time blocks and core review sequence recognizable if the aim is to follow a Level 10 format. If the meeting regularly needs more than 90 minutes, first check whether updates are too detailed, the Issues List is poorly prioritized, or participants are trying to handle topics that belong in another meeting.
Do not add every department update to the agenda simply because it happens weekly. A report that does not support a decision, measurable indicator, or priority can often be shared separately. Similarly, the template does not require every issue to be solved on the spot. A clear next step, owner, and date can be a useful outcome when the group needs information before deciding.
For a small team, one person may facilitate and also own a scorecard number; the roles do not automatically need separate people. For a larger group, it can help to ask for concise updates in advance and keep the live meeting focused on shared decisions. Whatever the arrangement, agree on who updates the document and how the team will preserve decisions and commitments from week to week.
Common Problems and How to Avoid Them
- Turning the scorecard into a debate: Review whether numbers are on or off track, then add the important explanation to the Issues List for IDS.
- Using vague Rocks or to-dos: Describe a result that can be judged as complete or incomplete. For a to-do, name one owner and a near-term due date.
- Discussing symptoms rather than causes: Ask what is creating the issue before agreeing on a fix. A visible symptom may not reveal the underlying obstacle.
- Letting one person dominate IDS: Invite relevant perspectives, keep the discussion on the issue, and distinguish evidence from assumptions.
- Leaving without a record: Write down decisions and actions during the conversation, then read them back during the conclusion.
- Changing the agenda every week: Frequent redesign makes it harder to build a consistent rhythm. Keep the standard sections stable and make changes deliberately when the format is not serving the team.
A common misconception is that a Level 10 Meeting should spend all 90 minutes discussing problems. It should not: the short opening and review sections establish context and accountability, while IDS receives the largest block because it is where the team works through its most important issues. Another misconception is that every participant must rate the meeting a ten. The rating is feedback about the meeting experience, not a test of loyalty or a judgment of a person.
How It Differs from a General Weekly Meeting
A general weekly meeting might be organized around department-by-department updates, presentations, or announcements. The EOS format instead uses a fixed sequence and reserves a substantial portion for prioritized issue-solving. It also links weekly review to quarterly priorities and measurable indicators. This can make the meeting easier to repeat, but it is not automatically the right structure for every gathering.
Use the Level 10 agenda when a leadership team needs a recurring forum for accountability, shared priorities, and decisions on obstacles. A project working session may need a different agenda centered on deliverables and technical choices. A company-wide presentation may need time for explanation and questions rather than a leadership-team IDS block. Teams can use other meeting formats alongside the weekly leadership meeting instead of forcing every conversation into one template.
Frequently Asked Questions
How long is an EOS Level 10 Meeting?
The standard weekly format is 90 minutes, with five-minute reviews, a 60-minute IDS block, and a five-minute conclusion. Teams sometimes adapt the timing, but preserving enough time for focused issue-solving is central to the format.
What does IDS mean in an EOS meeting?
IDS stands for Identify, Discuss, Solve. The team clarifies the real issue, discusses it, and agrees on a solution or a specific next action. It is intended to move beyond repeatedly reporting a problem.
What should go on an EOS Issues List?
Put important problems, opportunities, and questions that need discussion on the list. Phrase each item briefly enough to understand, and prioritize it when the team reaches IDS. Routine updates and simple tasks usually belong in their own review or to-do list instead.
Who should attend a Level 10 Meeting?
It is generally a recurring meeting for the leadership team and the people responsible for its shared priorities and results. Invitees should be able to contribute to the agenda’s decisions; bringing a large audience for updates alone can make it harder to maintain the format.
Can I use this as a free printable EOS meeting agenda?
Yes. The blank tables above can be copied into a document and printed or completed digitally. Fill in meeting details, update the review sections, and record IDS outcomes and to-dos so the team can check them at the next meeting.