Building an HQ rollup dashboard for franchise training

The HQ rollup dashboard is the operations director's morning view. They open it, see completion across every location, see which sites are behind, and either delegate the chase to the district manager or step in directly. The dashboard's job is to compress hundreds of locations into one screen without losing the ability to drill in. Most LMS dashboards are not built for this — they are built for one organization, not a network, and they crumble when you ask them to slice by franchisee. ## The morning-view test A usable rollup dashboard passes one test: the ops director can answer three questions in under sixty seconds without scrolling. 1. What is overall network completion this week? 2. Which locations are bottom three? 3. What are the overdue counts on this quarter's compliance training? If any of those takes a click or a filter, the dashboard has failed. The morning view is glanceable. The drill-in is for follow-up after coffee. ## Five metrics, ranked The rollup carries exactly five metrics. Resist the temptation to add more. **Network completion rate.** The headline KPI, displayed as a single percentage with a sparkline showing the last eight weeks. This is the number the CEO asks about. **Locations by completion (sortable table).** A row per location, sorted descending by default. Each row shows the location name, the completion percentage, the count of overdue frontliners, and a status dot (green / amber / red). Click the row, drill into the location. **Overdue count, by course.** A second table showing each active assignment, the network-wide overdue count, and the deadline. The auditor's view. **New-hire ramp time.** Average days from hire date to onboarding-complete. Shown as a 30-day moving average. If this number drifts up, onboarding is breaking somewhere. **Refresher coverage.** For recurring compliance training (food safety, harassment prevention, alcohol service), the percentage of the workforce currently within their valid window. Below 95% is a yellow flag; below 90% is a red flag. That is it. Engagement, time-on-platform, login counts — all noise at this layer. The ops director does not need them. If a learning team wants them, give them a separate view. ## The drill-in path From the rollup, three clicks should reach a specific frontliner. Click 1: location row. Now you are inside one site, seeing every assignment, completion rate, overdue count. Click 2: the course in question. Now you see the roster — every frontliner assigned, their status, their deadline. Click 3: the frontliner. Now you see their record — when they started, where they are in the module, their last activity timestamp. Three clicks. No exports. No spreadsheet. The whole point of the rollup is to remove the spreadsheet step entirely; if drilling in puts you back into Excel, the system has failed. ## The franchise-manager scope split The HQ rollup is one view. Franchise managers get their own — same shape, scoped to their location only. They see their 92% completion rate next to whatever benchmark you choose to expose (network average is the safest). They see their overdue count. They cannot see the network rollup, they cannot see other franchisees, they cannot edit HQ-owned content. This is permission work, not screen design. Aristotl's tenant model handles it with the standard Owner / Admin / Educator / Learner roles scoped to region or location. The same dashboard component renders both views; the data layer filters by scope. ## What the rollup should not show Quality scores. Engagement scores. Vanity averages. Anything that requires a definition before it can be read. The rollup is for operational decisions: who is behind, where to intervene, what is overdue. The L&D team can have a separate view for content quality and learner feedback. Do not mix them. ## Build vs buy Most franchise HQ teams will not build this dashboard. Reporting layers on top of generic LMS data are a six-month project that goes stale the moment the LMS schema changes. The fastest path is a platform that ships with the rollup as a default view — Aristotl's HQ dashboard renders this on day one with no consultant engagement, no BI tool, no schema mapping. The metrics above are the defaults; configuration adjusts thresholds, not structure.

Ready to put this into practice?