# Rohan's Services Dashboard — Chapter 12 Worked Example

> Synthetic regional-services-company Q3 scenario used to build Rohan's executive dashboard in Chapter 12 of *The Defensible Decision*. A single quarter, three months, four service lines, four regions — sized to what an executive Monday-morning dashboard actually shows.

**Wholly synthetic.** Any resemblance to a real services firm's data is coincidental.

## Files

- [`rohan-services-dashboard.csv`](rohan-services-dashboard.csv) — flat aggregate rollups
- [`rohan-services-dashboard.json`](rohan-services-dashboard.json) — canonical scenario contract with source hash

## What it represents

A regional services company’s fiscal Q3 2026 (July–September) revenue rollup, broken out three ways:

- **By month** — three monthly totals with actual and plan, showing a July–August miss that recovered to pace in September.
- **By service line** — four service lines (Implementation, Managed Services, Advisory, Training).
- **By region** — four US regions (Northeast, Southeast, Central, West).

Plus a single prior-quarter (Q2) comparison total.

## Invariants (locked)

The scenario carries executable invariants that Chapter 12’s release contract enforces:

- Q3 actual revenue: `$18.75M`.
- Q3 plan: `$19.20M`.
- Overall variance rounds to `-2.3%` (a small miss the executive needs to see and explain).
- Monthly totals reconcile to `$18.75M` within one cent; monthly plan reconciles to `$19.20M`.
- Service-line revenue reconciles to `$18.75M`; regional revenue reconciles to `$18.75M`.
- July and August both landed below plan; September recovered to at least plan (the trajectory that makes the miss defensible).
- Q2 baseline (`$16.90M`) is below Q3 — business is growing quarter over quarter.
- Implementation is the largest service line.
- BEFORE dashboard has 9 visuals; AFTER dashboard has 5.

## Why the numbers matter

The dataset backs Chapter 12’s teaching arc: what happens when Copilot produces a nine-visual page with no primary KPI, and how the four Refine checks (5-Visual Rule, hierarchy, composition, mobile) reduce it to a five-visual instrument panel the executive can read in thirty seconds. The `-2.3%` variance has to be *visible enough to be worth explaining* but *small enough that the recovery story matters*. Larger and the tone shifts to crisis; smaller and there is nothing to explain. The September-recovers-to-plan clause is the pedagogical asset — it lets the corrected dashboard tell a trajectory story (opened behind, ended on pace) rather than just report a miss.

If you tighten the numbers, keep the invariants above intact or the chapter will contradict its own figure.

## What it does NOT represent

- Individual account, opportunity, or deal grain (this is executive-summary rollup).
- Cost, margin, or profitability data (revenue only for this scenario).
- Weekly or daily grain.
- Pipeline or forecast.

## Reproducibility

The dataset ships from the book source at `AlexBooks/applied-ai/ai-directed-viz/data/rohan-services-dashboard.json` and is re-emitted here by `AlexBooks/applied-ai/ai-directed-viz/scripts/generate-rohan-dashboard.mjs --site-root <site-root>`. The generator writes the source SHA-256 into `rohan-services-dashboard.json` so drift between the book and this site is detectable.

## License

Released for teaching use alongside *The Defensible Decision*. Use freely.