Our weekly delivery volume fluctuates wildly week to week due to client scheduling, making our Scorecard swing between deep red and bright green. Should we track a rolling 4-week average or stick to raw weekly counts on our Scorecard?

Question

Tyler Smith · Accepted Answer

Stick to raw weekly numbers. The primary purpose of an EOS Scorecard is to give you an early warning pulse of reality, not a smoothed-out narrative. When you rely on a rolling four-week average, you introduce mathematical lag. A serious operational breakdown that happened this week gets masked by three weeks of strong historical performance.

Smoothing the data delays your leadership team from stepping into IDS until the damage has already compounded. If your delivery volume swung from twenty units down to two, you need to see the red box immediately on Tuesday morning. That drop may indicate an emerging client bottleneck, broken onboarding, or an upstream sales hiccup that occurred three weeks prior.

If volatility is a natural operational reality of your business model, adjust how you evaluate the number rather than changing the metric to an average:
- Set a weekly minimum operating floor that accounts for standard delivery variances.
- If the red box represents a scheduled or expected fluctuation, the seat owner simply states that context during reporting and chooses not to drop it down to the Issues List.
- If the dip represents an unplanned failure, drop it straight down to IDS.

Keep the raw weekly number visible. You want the raw friction of current operations in front of leadership so you solve small issues before they become chronic margin leaks.