If a metric misses its weekly target by just one percent or a fraction of a unit, does it automatically turn red and go to the Issues List, or should our Scorecard allow a tolerance band around weekly goals?

Question

Tyler Smith · Accepted Answer

Do not use tolerance bands or gray areas on an EOS Scorecard. If your weekly goal is 50 outbound sales conversations and the team hit 49, the number is red. If the target delivery time is 4.0 days and your actual was 4.1 days, it is red.

Allowing tolerance bands softens accountability. The moment you declare that hitting 95 percent of a target counts as green, your leadership team will begin treating 95 percent as the actual target. Human nature will then slide the tolerance down to 90 percent. Soon, your entire Scorecard appears green while your business is performing below standard across every seat.

A red number is not a personal failure, a punitive reprimand, or a signal that someone must be fired. Red simply means an objective standard was missed. It is neutral data.

When a number turns red:
- The owner announces the off-track status during the Scorecard review without apologizing or making excuses.
- The Integrator asks if it needs to go to the Issues List.
- If the miss is an isolated, understood anomaly that requires no cross-functional action, the owner says working it and monitors it next week.
- If the miss reveals an operational roadblock, process breakdown, or trend, it drops straight to the Issues List for IDS in the Level 10 Meeting.

Absolute objectivity creates clarity. Keep your targets firm, keep the colors binary, and let red numbers do their job by highlighting where the business needs attention.