Our leadership team consistently misses our 90 percent To-Do completion rate because members treat the seven-day deadline as optional and routinely roll incomplete tasks over to the next week. How do we eliminate rolling To-Dos and restore real weekly accountability?

Question

Tyler Smith · Accepted Answer

A To-Do in the EOS framework is a binary, seven-day commitment. It is either done or not done. The moment your Integrator allows someone to say roll it to next week without consequence, you have replaced personal accountability with a suggestion box.

To break this habit, enforce three non-negotiable rules during your Level 10 Meeting:

- Score the task as not done immediately. Do not keep it open. It goes against your weekly percentage, pulling the team score below 90 percent in plain view of everyone.
- Force an immediate binary choice. When a To-Do is not done, ask the owner: Can you get this done in the next seven days, or is this an operational roadblock that belongs on the Issues List? If it remains relevant and realistic, reassign it as a brand-new To-Do for the upcoming week. It does not roll; it is treated as a renewed commitment with fresh visibility.
- Trigger an automatic issue on the second miss. If the same commitment misses the deadline two weeks in a row, it automatically drops to the bottom of the Issues List. Two consecutive misses signal a broken process, poor time management, or a GWC issue on the Accountability Chart.

Your weekly meeting pulse only builds traction if commitments carry operational weight. When leaders realize that unfinished tasks result in public red metrics and root-cause examination during IDS, the team will stop accepting rollover tasks.