Leadership team members frequently join our Level 10 Meeting five to ten minutes late or sneak out early for client emergencies, fracturing the pulse. What is the strict operational protocol to stop tardiness and partial attendance?

Question

Tyler Smith · Accepted Answer

Tardiness and mid-meeting departures are not minor scheduling inconveniences. They are cultural leaks that signal your leadership team values external operational chaos over foundational team accountability.

In EOS®, the weekly Level 10 Meeting™ must be treated as sacred: same day, same time, same agenda, starting and ending on time. When leaders drift in late or leave early to deal with fires, they compromise the integrity of the meeting pulse and force the rest of the team to work around their schedule.

The Integrator must execute three non-negotiable rules to stop this behavior:
- Start the meeting precisely on the minute, even if seats are empty. Never delay the start of the Segue to wait for a latecomer. Starting late rewards unpunctual behavior and punishes leaders who arrived prepared. If a seat is empty, move directly into the agenda.
- Forbid laptops and phones for non-meeting purposes. If an executive claims they must keep their phone active for an urgent client crisis, they are admitting their department lacks operational autonomy. If an emergency is truly catastrophic, the leader should step out entirely, handle the crisis, and take an unexcused absence rather than dividing their attention.
- Grade attendance in the Conclude section. Any late arrival, early departure, or disruptive device use automatically drops the meeting rating to an eight or lower for the entire room. Make punctuality a collective standard.

When a leader routinely fails to protect the 90-minute block, it is not a time management problem. It is a GWC™ failure regarding their seat on the Accountability Chart. Treat punctuality as a baseline requirement of leadership.