EOS Hub

English

Slovenčina

English

Slovenčina

Appearance

L10 Meetings ​

The L10 (Level 10) Meeting is the heartbeat of EOS. EOS Hub provides a structured digital environment for running these weekly meetings with your team, guiding you through all seven segments.

INFO

New to the L10 Meeting format? Read the EOS Methodology: Level 10 Meeting page first for background on why this meeting structure works.

Creating a Meeting ​

To start a new L10 Meeting:

  1. Navigate to Meetings in the sidebar.
  2. Click New Meeting.
  3. Select the meeting date (defaults to today).
  4. The meeting is created and you are taken to the meeting view.

TIP

Only users with the team role OWNER or ADMIN can create meetings -- this includes organization Owners, Admins, and Implementers, who act as team Admin in every team. MEMBER users can participate but not initiate.

Recording a Past Meeting ​

If your team held an L10 Meeting without running it in EOS Hub, you can record it afterwards:

  1. Click New Meeting.
  2. Turn on the Already happened switch.
  3. Enter the date, start time (in your time zone), and duration in minutes (1--600).
  4. Click Create meeting.

The meeting is saved as completed, so it appears in the meeting history and counts toward the dashboard charts. Members can then add their ratings (see Meeting Ratings).

The Seven Segments ​

Each L10 Meeting follows a structured flow of seven segments. EOS Hub displays each segment as a step, guiding your team through the process.

Moving Through the Agenda ​

  • The facilitator leads. When a team ADMIN or OWNER (the facilitator) opens a segment or clicks Done, the meeting moves there. This is saved: leaving the meeting -- another page of EOS Hub, a closed tab, a reload -- and coming back opens the meeting at the same segment with the same segments marked done. Other participants open the meeting at the facilitator's segment and can look at the other segments on their own.
  • Each segment has its clock. It starts when the facilitator enters the segment and shows the time left of its time box (amber in the last minute). Past the time box it shows the overtime with a minus sign in red, for example −04:23. Leaving a segment keeps its time, and coming back continues it. The agenda shows the time each segment has used.
  • Time boxes: 5 minutes for each segment, and IDS gets the rest of the team's meeting length (90 minutes → 60 minutes of IDS; see Configuring Duration).

1. Segue (5 minutes) ​

Start the meeting with good news. Each participant shares one piece of personal or professional good news. This sets a positive tone and helps the team connect.

In EOS Hub, participants can type their segue or share verbally while the facilitator advances the meeting.

2. Scorecard Review (5 minutes) ​

Review the team's weekly Scorecard. The meeting view displays all measurables with this week's values compared to goals.

  • Numbers that hit their goal are highlighted in green, missed ones in red -- the goal decides, nobody marks them by hand.
  • This week's value can be entered or corrected right in the table (Enter saves, ↑/↓ moves to the next measurable).
  • Missing entries show click to enter and the last value entered.

TIP

A missed number isn't discussed here: click Add to issues next to it. The issue (New Leads: 42 leads (goal >50)) is linked to the meeting and appears in the IDS segment.

3. Rock Review (5 minutes) ​

Every Rock of the meeting's quarter is reported for the meeting's week: On Track, Off Track or Done, with an optional note. The facilitator marks who is absent; an absent owner's Rock without a report in advance is recorded as ? (unknown). Each Rock shows its last 4 weeks, and an Off Track Rock can be added as an issue for IDS with one click.

Reporting is mandatory but doesn't block: Conclude lists the Rocks still waiting for a report, and the meeting can end anyway. See Weekly Reports.

4. Headlines (5 minutes) ​

Share customer and employee headlines -- important news that the team should be aware of. Headlines are brief, informational updates. If any headline needs discussion, drop it to the Issues list.

In EOS Hub, team members can add headlines during the meeting. Each headline can be flagged as needing IDS with a single click.

Anyone on the team can take the notes. One row adds every headline: pick its kind (customer, employee, company) and Whose news (default: your own), type it and press Enter. The kind and the person stay, and the field keeps the focus, so the next headline follows straight away. While the meeting runs, headlines are the team's shared notes: anyone on the team can fix, move to another person or delete any of them with ⋯. After the meeting, only a headline's author (while the rating window is open) and the facilitator can.

5. To-Do Review (5 minutes) ​

Review To-Dos from the previous week. Each To-Do owner reports whether their item is Done or Not Done.

The segment shows all of the team's open To-Dos plus the To-Dos completed since the previous meeting, together with the completion percentage for that period.

  • Done To-Dos are checked off and archived.
  • Not Done To-Dos can be carried forward to next week or dropped to the Issues list.
  • Add To-Do creates a new To-Do right in this segment (for example one given again with a new date); it is linked to the meeting and shows in its recap.
  • The pencil next to a To-Do changes its title, owner or due date without leaving the meeting. The To-Dos raised in the meeting can also be changed in IDS and Conclude, and when correcting a completed meeting.

The goal is a 90%+ completion rate each week.

6. IDS -- Identify, Discuss, Solve (60 minutes) ​

This is the core of the meeting. The team works through the Issues list using the IDS process:

  1. Identify -- Prioritize the top three issues from the list.
  2. Discuss -- Dig into the root cause (not symptoms).
  3. Solve -- Agree on a solution, which usually becomes a To-Do.

In EOS Hub, the IDS segment displays the team's whole open list of short-term issues, sorted by priority -- not only the issues raised during this meeting. Long-term issues stay on the V/TO for quarterly and annual planning and do not appear here. The team can:

  • Reorder issues by priority
  • Move an issue to "Solving" status to indicate active discussion
  • Create To-Dos directly from the issue resolution (the suggested due date is 7 days out)
  • Mark issues as "Solved" when complete

WARNING

Resist the urge to skip straight to solving. The "Discuss" phase is critical for finding root causes rather than treating symptoms.

7. Conclude (5 minutes) ​

Wrap up the meeting:

  • Recap To-Dos -- Review all new To-Dos created during the meeting.
  • Cascading Messages -- Identify any information that needs to be communicated to the rest of the company.
  • Rate the Meeting -- Each participant rates the meeting with a whole number from 1 to 10.

Meeting ratings feed the Dashboard: its Meetings pillar is the average rating of the last 4 rated meetings (target 8+), and its Meetings card shows the ratings, durations and attendance of the last 12 meetings.

Notes ​

Under the agenda, every meeting has a Notes card for decisions and context worth keeping. The facilitator (team Admin or Owner) writes them; they are saved automatically as you type. Everyone else on the team reads them. Notes can be prepared before the meeting and completed afterwards. Notes written in Markdown (bold, lists, links) are shown formatted.

Recap ​

A completed meeting starts with a Recap: the team, day, duration and average rating, the new to-dos with their owners and due dates, the issues solved during the meeting and those raised in it, headlines, cascading messages and the notes (Markdown shown formatted; Copy as text keeps the source text).

  • Copy as text copies the recap as plain text, ready for an e-mail or a chat message.
  • Print / PDF opens the meeting's record: an A4 document for anyone who wasn't there, such as top management. It starts with the key figures (average rating, attendance, To-Dos done, measurables and Rocks on track) and the time each agenda step took against its time box, then follows the agenda: segues, the scorecard of the meeting's week and the three before it, the Rocks as reported that week, headlines, the To-Do review with what wasn't done, IDS (issues solved, new To-Dos and issues), cascading messages, notes, and who attended with their ratings. Save as PDF opens the print dialog; choose Save as PDF there.

Meeting Ratings ​

EOS Hub follows the EOS rating rules:

  • Whole numbers from 1 to 10. The target is an average of 8 or higher.
  • Only actual ratings count. The average includes only the people who rated the meeting. Members marked absent and members who did not rate are left out.
  • Shown with participation. The result is displayed as the average with one decimal and the number of people who rated, for example 8.5 · 5/6 rated.
  • Below 8, say why. After the reveal, every rating below 8 is highlighted with Below 8 -- say why, so the team hears what to improve.

Hidden Until Revealed ​

During a running meeting everyone rates privately: you see your own rating, and for the others only whether they have rated (Rated / Not rated yet). The average is hidden too, so nobody adjusts their number to the others.

When everyone has rated, the facilitator (team Admin or Owner) clicks Reveal ratings. Until then the facilitator can mark people absent, but not rate on someone's behalf. The ratings refresh on their own every few seconds during the Conclude step. Then everyone sees all ratings and the average. Others see the reveal after reloading the page. Once the meeting has ended, ratings are always visible -- also those added later in the rating window. The REST API and AI assistants follow the same rule.

When Can You Rate? ​

The meeting must be started before anyone can rate it. After that:

  • Members can rate the meeting during the meeting and after it ends -- until the team's next meeting starts, but for at most 7 days. For a recorded past meeting, the 7 days start when it was entered.
  • ADMIN and OWNER can set or correct anyone's rating and mark members as absent at any time.

Implementers do not rate

An organization Implementer can facilitate the meeting and manage ratings like a team Admin, but never rates the meeting. The rating belongs to the team, so Implementers are not listed in the ratings and are not counted in the "rated" total.

Meeting Countdown Timer ​

When a meeting is in progress, a real-time countdown timer appears on the right of the top bar, on every page of the app. This helps the team stay on track with time management.

How It Works ​

  • Countdown display -- A large, bold countdown showing the remaining time.
  • Elapsed time -- A smaller clock showing how long the meeting has been running.
  • Progress bar -- A full-width bar at the bottom of the top bar that shrinks as time passes.
  • Link to the meeting -- Click the countdown to go back to the running meeting from anywhere in the app, for example after looking something up in the Scorecard.

On phones the countdown shows only the remaining time; on wider screens the team's name and the elapsed time are shown as well. See Navigating.

Color Indicators ​

  • Green -- Normal meeting time remaining.
  • Amber -- The meeting has reached the configured warning minute (by default, minute 80 of a 90-minute meeting).
  • Pulsing red (full bar) -- Meeting has exceeded its allocated time. The timer switches to show overtime (+MM:SS).

The meeting continues running until the facilitator ends it. A meeting nobody ended is ended automatically 2 hours after its planned end (start + the team's meeting length) -- or 2 hours after the facilitator's last move in the agenda, if that was later. It ends at the planned end or at that last move. Its Meeting details say it was ended automatically until someone checks the start and duration there (Edit time). Meetings never start on their own.

Configuring Duration & Warning ​

Meeting duration and warning threshold are configurable per team by organization Owners and Admins:

  1. Go to Organization settings > Teams.
  2. Find the team's card and adjust Meeting (min) (default: 90 minutes) and Warn at minute (default: 80).

The countdown turns amber from the Warn at minute of the meeting onward. The value must be smaller than the meeting duration.

TIP

The countdown timer survives page refreshes -- it uses the meeting's start time from the database, not browser state.

Meeting Duration Tracking ​

When a meeting is completed, the actual duration is calculated and stored. This duration is:

  • Displayed in the meeting history list (with a clock icon).
  • Shown on the Dashboard in the Duration view of the Meetings card, against the planned length; meetings more than 10 % over are amber.

Meeting Details and Correcting the Time ​

A completed meeting shows a Meeting details panel with its start time, duration and the ratings in one line (the average, how many rated, each member's number). Ratings are changed in the Conclude step. If the recorded time is wrong -- for example, a meeting shows 0 minutes or was left running long after it actually ended -- an ADMIN or OWNER can click Edit time to correct the start and duration.

Deleting a Meeting ​

A meeting created by mistake or twice can be deleted by a team ADMIN or OWNER: ⋯ → Delete meeting in its row of the meetings list or in the meeting's header. After a confirmation it goes together with its segues, headlines, cascading messages, ratings and attendance, guests and notes. To-dos and issues raised in it stay (without the link to the meeting), and Rock reports and Scorecard values stay with their week.

Correcting a Completed Meeting ​

A wrong click or a typo during the meeting can be fixed afterwards:

  • Edit record (team ADMIN or OWNER) opens the completed meeting for corrections: the segments work as during the meeting -- add, edit or delete segues, headlines and cascading messages, change the Rock reports and attendance, the Scorecard values of the meeting's week, to-dos and issues. The meeting stays completed (times and duration don't change). Finish editing ends it.
  • Your own entries -- segues, headlines (text and kind) and cascading messages -- have a ⋯ menu with Edit and Delete: during the meeting and afterwards while the rating window is open (until the team's next meeting starts, at most 7 days). Admins and Owners can change any entry at any time.
  • A meeting changed after it was run shows Edited with the date and the person, in the header and in the recap. Ratings and attendance don't count as changes, and a meeting recorded afterwards (Already happened, an import) is not marked while it is being filled in.

Meeting History ​

All past meetings are listed on the Meetings page. You can:

  • View the full record of any past meeting, including all segments.
  • See who participated and how they rated the meeting.
  • Review To-Dos and Issues that were created during the meeting.
  • See the actual meeting duration alongside the average rating.

Filter the list with Status (Scheduled, In Progress, Completed) and Period (This month, Last 3 months, This year); the meetings list has no search box. The filters are kept in the address -- see Filtering Lists.

Meeting Participants ​

All team members can view the meeting. Participation is tracked -- the meeting records who was present and who rated the meeting. ADMIN and OWNER can mark members as absent; absent members are not counted in the rating average.

Best Practices ​

  • Start on time, end on time. The L10 Meeting is designed to last exactly 90 minutes (configurable per team). Use the countdown timer to stay on track.
  • Follow the segments in order. Do not skip or rearrange.
  • Keep Segue, Scorecard, Rock Review, Headlines, and To-Do Review brief. The bulk of the time (60 minutes) should be spent on IDS.
  • Rate honestly. The meeting rating is a tool for improvement, not a formality.
  • Create To-Dos, not discussions. When the team solves an issue, capture a specific, actionable To-Do.

AI-Enhanced Inputs ​

During meetings, many text inputs include an "Enhance with AI" button. This helps participants write clearer issue titles, more actionable to-dos, and better cascading messages. See AI Integration for details.

© 2026 EOS Hub. All rights reserved.