Tom's IT Sandbox

Gap Analysis

Surface periods where an item has no forecast entry and force a business interpretation.

← Back to Reports
Executive framing

Executive Summary — Answer First

Decision rule: review this page first, then move to deeper drill-down only when the result is economically meaningful.
  • Blank does not always mean zero. This report makes that ambiguity visible.
  • Use it to distinguish intentional intermittent demand from missing forecast coverage.
  • Gaps matter most when production, purchasing, or customers expect continuity.
SCQA / Context

Situation: some item-period combinations have no forecast row. Complication: the business may interpret blanks inconsistently. Question: are these intentional gaps, true zeros, or missing data? Answer: review all uncovered periods and assign a business meaning.

Issue Tree / Diagnosis
  • Coverage gaps across the batch calendar
  • Interpretation of blanks versus zeros
  • Operational risk from missing expectations
Analysis & Insights
  • Gaps are not inherently bad, but unmanaged gaps create confusion.
  • This report is particularly important for replenishment, supplier commits, and production continuity.
  • Repeated unexplained gaps often indicate process weakness rather than business intent.
Recommendations
  • Define a policy for blank versus zero and enforce it consistently.
  • Review uncovered periods for high-priority items first.
  • Treat unexplained gaps as data-quality exceptions.
KPIs
  • Gap count by item
  • Gap count by period
  • Share of high-priority items with gaps
  • Time to resolve uncovered periods
Implementation Roadmap
Phase Key action Owner Success metric
1. Review Run the report and isolate the highest-value exceptions. Planning / Operations Material issues identified within one review cycle.
2. Validate Confirm whether the result reflects real business change, timing shift, or data-quality issue. Forecast owner Exceptions explained and documented.
3. Act Translate validated findings into supply, capacity, purchasing, or governance actions. Cross-functional team Action owners assigned with due dates.
Risks, Gaps, and Next Steps
  • Do not treat a statistical exception as a business conclusion without validating the commercial or operational driver.
  • Where economics are missing, pair this page with item margin, lead time, or inventory exposure before escalating.
  • Use the summary line above the grid to confirm row volume; unexpected row counts often indicate filter or data issues.
Analysis output

Data Table

Use the table below to validate the hypothesis, size the issue, and identify the items or periods that need action.