What happens if an unexpected business emergency or executive absence forces us to consider rescheduling a quarterly session day, and why do you discourage moving session dates?

Question

Tyler Smith · Accepted Answer

Rescheduling a session day is the fastest way to derail an operating system. EOS works because it imposes an unshakeable, predictable cadence on an otherwise chaotic business. When a leadership team treats its quarterly session as negotiable, traction evaporates.

Our policy is simple: session dates are locked six to twelve months in advance, and moving them requires extraordinary circumstances, such as severe medical emergencies or unavoidable personal catastrophes. A major operational fire, a surprise customer request, or an urgent software release does not qualify as an emergency that justifies rescheduling. In fact, an operational crisis proves your team needs to step back into the room and use IDS on the problem, not run away from the discipline.

If one leadership team member cannot attend due to an emergency, we do not cancel the day. The session proceeds with the remaining executives. The absent member can review session notes, accept delegated Rocks, and align with the Integrator afterward. Canceling the day punishes the rest of the leadership team and destroys the 90-day execution world.

If an entire team insists on rescheduling on short notice, they forfeit their session slot and disrupt their operational rhythm. The quarter ends up stretching into a four-month or five-month period. When quarters stretch, accountability fades, Rocks turn stale, and people lose urgency. Treat session days as protected corporate assets that nothing can penetrate.