When two or three leadership team members are traveling or a holiday falls on a Monday, our team tends to cancel our Level 10 Meeting entirely or push it back, which breaks our operational rhythm. What is the rule for protecting the meeting pulse when people are absent?

Question

Tyler Smith · Accepted Answer

The weekly Meeting Pulse is the operating heartbeat of an EOS company. When you cancel or reschedule a Level 10 Meeting because someone is out of office, you communicate that operational accountability is optional. One skipped meeting turns into a two-week blind spot where Rocks stall, red Scorecard metrics go unaddressed, and customer issues fester.

The rule is non-negotiable: same day, same time, same agenda. The meeting happens every single week, regardless of who is missing. If the Visionary is on vacation, the Integrator runs the pulse. If the Integrator is traveling, another leadership team member facilitates. If half the team is out at an industry conference, the remaining leaders still sit down for 90 minutes, review the numbers, and solve whatever issues fall within their control.

When a holiday falls on your standard meeting day, you do not cancel. You hold the pulse on the first business day following the holiday at a fixed alternate time, or you hold it the Friday before. The team agrees on this backup slot at the start of the year so calendar collisions never become an excuse.

For absent members, their seats must still be represented. The leader must update their Scorecard measurables and Rock statuses in advance. If they own an open to-do, they report done or not done to the Integrator before the meeting starts. If an issue on the list requires their direct input, the team leaves it for the following week and prioritizes the next critical problem.

Consistency builds organizational trust. When employees and leaders know the pulse occurs rain or shine, they stop scheduling random interruptions and learn to resolve business issues inside the meeting rhythm.