Case study
Suspension dashboard with live cross-unit integration
Problem
Suspension data originated in a different directorate and arrived as three separate sheets with no shared key. It was readable only by the operator who maintained it, and executives needed a summary rather than a raw table.
What I built
- Mapped the columns the three sheets had in common into one working sheet.
- Set up a live import-range so the dashboard follows the source, with a backup that preserves the last known state.
- Built the executive summary first, detail on demand.
Outcome. Still in daily use. Users open it for the list: how many SPPG units are suspended, how many have reopened, and which have passed three months — the point where suspension can become permanent.
Suspension dashboard
1 photoSPPG units under suspension: how many are suspended, how many have reopened, and which have passed three months — the point where suspension can become permanent. Built in a separate directorate, so the dashboard follows the source through a live import-range with a backup that keeps the last known state.
