Getting 100% completion on mobile-only devices

Hitting 100% completion is a different game from hitting 90%. The first 90 points come from getting the basics right: mobile-first design, fast login, the manager paying attention. The last 10 points are the hard ones — the frontliner on extended leave, the new hire who started two days before the deadline, the location with a broken tablet. Networks that hit 100% on compliance training do four specific things differently from networks stuck at 88%. ## First, define what 100% means 100% of who, by when, on what? - 100% of active frontliners (excluding employees on parental, medical, or extended leave) — yes, achievable. - 100% of every person who shows up in HRIS as employed at any point in the quarter — no, not realistic. Mid-quarter starts and stops will always create a small gap. - 100% within the deadline window — depends on whether the window includes a buffer for new hires. It should. The right operational target is: 100% of active frontliners within their assigned deadline window, with the deadline accommodating new-hire ramp time. That target is achievable; the alternatives are not. ## Four practices that close the last 10% **1. The 14-day-before alert.** When 14 days remain on a deadline, every frontliner not yet started gets a notification, and their manager gets a list. Not the L&D team — the manager who can act locally. This catches the 30% who would otherwise wait until the last weekend and then hit a tablet glitch. **2. The 3-day intervention list.** Three days before deadline, the platform generates a list of every frontliner not yet complete, by location and manager. The district manager gets a roll-up: "Region North, 14 frontliners outstanding, here are the names." The intervention is direct: the district manager calls the store managers, the store managers find the frontliners, the frontliners finish. **3. The new-hire deadline buffer.** New hires get a 14-day window from their start date for compliance training, regardless of when the assignment was originally pushed. Without this, anyone hired 5 days before the network deadline will fail. Aristotl's assignment model supports per-learner deadlines for this reason. **4. The leave roster.** The platform has a status for "on leave — deadline paused." When the frontliner returns, their deadline reactivates from their return date. Without this, every parental leave creates a permanent overdue record that pollutes the rollup. These four practices are operational, not motivational. They close the gap between "most frontliners trained" and "every frontliner trained." ## What the manager has to do The manager's role at 90→100 is small but non-negotiable: respond to the 3-day intervention list. Five minutes per location, three days before deadline, find the four to seven frontliners outstanding and confirm they will finish. If they will not (vacation, leave, system issue), flag it; otherwise, hand them the tablet and watch them start. The practice that fails: "the L&D team will chase them." Centralized chasing does not work at scale. The manager is the chase. They are five feet from the frontliner. ## What the platform has to do Three platform requirements, beyond the basics: 1. **Per-learner deadline support.** Network-wide deadlines are too rigid for new hires and returning leave; per-learner deadlines fix this without breaking the rollup. 2. **Manager-scoped intervention lists.** The 3-day list goes to the manager's dashboard, not an L&D inbox. Aristotl's manager dashboard surfaces this list automatically when a deadline is approaching. 3. **Notification routing that the frontliner will actually see.** SMS to the frontliner's phone (if BYOD policy allows), or push notification on the store tablet they actually pick up. Email-only notifications to a frontliner who never checks email is not a notification. ## What 100% feels like in practice A QSR network running this model on annual food-safety refresher hits 100% within deadline three quarters in a row. The pattern: 14 days out, 35% are already done; 7 days out, 75%; 3 days out, 92%; deadline day, 99.5%; the last 0.5% finish in the 7-day buffer for new hires and returning leave. The dashboard shows a clean weekly run, the audit report exports without exceptions, the regional health inspector visits with no surprises. Networks that do not run this model show the same total trained — eventually. They just show it spread over six weeks of post-deadline cleanup, with auditor-visible exceptions.

Ready to put this into practice?