When our weekly To-Do completion percentage falls below the 90 percent benchmark, our team tends to roll incomplete items into the next week automatically without discussion. What is the strict protocol for handling incomplete To-Dos during the Level 10 review?

Question

Tyler Smith · Accepted Answer

When To-Do completion drops below 90 percent, allowing incomplete items to silently roll over into the following week erodes team accountability. A To-Do in EOS is a seven-day commitment, not an open-ended aspiration. If an item is not done, rolling it over should be the absolute exception, not an automatic default.

During the To-Do List review in the Level 10 Meeting, the Integrator reads each item. The owner may only say done or not done. No explanations and no backstories. If an item is not done, the owner has three specific paths:

- Drop it: If circumstances changed and the action is no longer critical, kill it immediately.
- Push it down to the Issues List: If the incomplete item reveals an operational roadblock, an unrealistic scope, or a resource constraint, drop it down to the bottom of the Issues List to be solved during IDS.
- Extend it once: If the person genuinely needs forty-eight more hours to finalize a deliverable that is already ninety percent complete, the Integrator may allow a single one-week extension.

If a To-Do appears on the list for a second consecutive week, it must either be marked done or dropped to the Issues List as an execution failure. It never rolls over a third time.

Tracking this percentage openly on your Scorecard makes the trend visible. When the room recognizes that dropping below 90 percent triggers an immediate diagnostic during IDS, leaders naturally become more disciplined about what they agree to take on.