Tracking training completion across 50 locations

At 50 locations, the spreadsheet model breaks. One ops director cannot chase 50 store managers every Monday for completion screenshots. By the time the data is consolidated, it is already a week stale and the auditor wants this quarter, not last quarter. The fix is not a bigger spreadsheet. It is a single tenant where every location reports up automatically and HQ sees the rollup the moment a frontliner finishes a course. ## What 50 locations actually looks like Fifty locations means roughly 750 to 1,500 frontliners, depending on store format. It means three to five district managers each owning ten to fifteen sites. It means at any given week, you have new hires onboarding, seasonal campaigns rolling out, and a food-safety refresher coming due for half the network. The volume itself is not the problem. The problem is that every one of those moving parts has its own deadline, and the only people who know the on-the-ground status are the store managers — who do not have time to fill in your tracker. If the system you are using requires a manager to manually confirm completion, you have built tracking on top of human chase. That model collapses past about fifteen sites. Every additional location adds another point of failure, another inbox to ping, another spreadsheet tab to merge. ## The shift HQ needs to make The move is from pull-based tracking (HQ asks, locations answer) to push-based reporting (locations train, the system reports automatically). Every interaction a frontliner has with the platform — opening a module, answering a knowledge check, finishing a course — is a data point. HQ does not ask for it. It is already there. This is what Aristotl's HQ rollup dashboard does by default. A frontliner finishes the food-safety refresher on a tablet at site 37 on a Tuesday afternoon; that completion appears on the ops director's dashboard before the manager has clocked out. No screenshot, no spreadsheet, no chase. ## What to track at 50 locations The trap at scale is tracking everything. Five metrics carry the weight: 1. **Completion rate by location.** The headline number, sliced by site. Sort descending; the bottom three are this week's intervention list. 2. **Days-to-completion.** Average elapsed time from assignment to finish. If this drifts past seven days for a 20-minute course, the assignment is competing with shift work and losing. 3. **Overdue count.** Frontliners past their assigned deadline. This is the auditor number. 4. **New-hire ramp.** Time from hire date to onboarding-complete, by location. Surfaces the sites where onboarding is informal or skipped. 5. **Refresher coverage.** For recurring compliance training, the percentage of the workforce currently within their valid window. Everything else is derivative. If district managers want more, give them filters; do not add KPIs to the rollup. ## Drilling in without losing the rollup The HQ dashboard's job is to compress 50 locations into one screen. The drill-in's job is to let the ops director go from rollup to a specific frontliner in three clicks. Click the bottom-three location, see its course list, see who is overdue, message the manager. That is the loop. If the drill-in requires exporting to Excel, the system has failed. The whole point is removing the spreadsheet step. ## What changes at the franchisee level Franchisees and store managers get their own scope — their own location, their own staff, their own completion view. They do not see HQ's content library, they do not edit assignments, they cannot adjust deadlines on HQ-owned compliance courses. They see what is theirs and they own it. The permissions model (Owner / Admin / Educator / Learner, scoped to region or location) makes this work without a consultant engagement to set up. When a franchise manager logs in on a Monday morning and sees their 92% completion rate next to the network's 87%, you have built the right incentive. They want to be on the leaderboard, not at the bottom of the chase list.

Ready to put this into practice?