SUPPORTING DOCUMENT CASE FILE // APPENDIX

BRD Summary

Short business requirements summary reconstructed from the beverage commercial performance case study.

Purpose

This summary captures the business requirements behind the reporting layer built for pricing, channel, and promotion performance.

Business Problem

Commercial teams were working from inconsistent definitions, manual reconciliations, and delayed reporting. That made it hard to review performance quickly and act while campaigns were still live.

Objectives

  • Standardise key commercial definitions
  • Reduce manual report preparation time
  • Give teams earlier visibility into promotion and channel performance
  • Support one shared view across sales, finance, and field teams

Stakeholders

  • Commercial managers
  • Sales teams
  • Finance teams
  • Field teams

Scope

In Scope

  • Metric alignment
  • Shared hierarchies
  • Semantic reporting layer
  • Dashboard views for commercial review

Out of Scope

  • Trade execution systems
  • Pricing approval workflows
  • Broader account planning outside the reporting model

Current-State Issues

  • Conflicting product hierarchies
  • Manual spreadsheet reconciliation
  • Slow turnaround for weekly reporting
  • Promotion review happening after the fact

Future-State Outcome

Commercial teams should have one reporting layer with consistent definitions, faster turnaround, and easier visibility into pricing, promotion, and channel performance.

Success Measures

  • Shorter report preparation time
  • Consistent KPI definitions
  • Better promotion review during live periods
  • Less manual reconciliation between teams
SYSTEM ONLINE // KM.III.IV 00:00:00 SAST CASE FILE // ACTIVE