Training frontliners who share one store tablet

Most franchise locations have one tablet at the front of house and a back-office laptop the manager uses. The frontliners share the tablet for clock-in, order entry, and increasingly, training. Designing training for the shared-tablet reality means accepting three constraints: login has to be fast, resumption has to be fast, and the platform has to track per-frontliner completion even when the device is shared. Most LMS systems were not built for this; many fail at the second constraint alone. ## The shared-device reality A typical QSR or coffee shop has 6 to 12 frontliners on a normal week, one tablet at the front, and one POS at the register. The tablet is used for everything: clock-in, schedule check, training assignments, customer-experience surveys, internal messaging. Average tap time per frontliner per shift might be 3 to 8 minutes spread across 4 to 6 sessions. If training requires a 5-minute login flow, the frontliner does it once and never comes back. If training resumes them at the start of the module they were halfway through, they bail. The shared-device context demands frictionless re-entry. ## What login should look like Three login patterns work on shared devices, ranked from best to worst. **PIN-based login.** Each frontliner has a 4 to 6 digit PIN. They tap their name from a roster, enter their PIN, are in. Total time: ~5 seconds. This is the model used by most POS systems for the same reason. **QR code on a name badge.** The frontliner scans their badge with the tablet camera, the platform recognizes them, they are in. Total time: ~3 seconds. Requires hardware support and badge issuance — works well for larger franchises with onboarding-grade infrastructure. **Email + password.** The default for most LMS systems and the worst on shared devices. Frontliners forget passwords, do not have email access at work, end up with the manager logging them in. Avoid. Aristotl supports PIN and SSO-based shared-device login for this reason. The frontliner picks themselves from a location roster, enters their PIN, sees their own assignments and progress. ## Resumption matters more than initial start A training session on a shared tablet looks like this: frontliner picks the tablet up between customers, has 4 minutes, opens the platform, picks up where they left off in the module they were doing yesterday, completes a knowledge check, gets called away. They put the tablet down. Next frontliner picks it up. For this to work, two things have to happen automatically: 1. **The platform has to remember exactly where the frontliner stopped.** Not the start of the module — the exact frame, exact knowledge-check, exact answer-in-progress. 2. **The platform has to log the frontliner out cleanly when they switch to another app or close the browser.** No dangling sessions where the next frontliner accidentally completes someone else's training. If the platform restarts the module from the beginning each time, the frontliner gives up. If it persists their session and the next person sees their progress, you have a tracking nightmare. ## Tracking per-frontliner completion The completion record must be tied to the frontliner who completed it, not the device. This sounds obvious, but a surprising number of homegrown training tracking systems use device sessions or even just "the manager confirms" — which fails the audit and disconnects from the rollup dashboard. The right model: every action (open module, answer knowledge check, finish course) is logged against the user account, not the device. Aristotl's data model treats device as transient context — useful for analytics (how much training happens on the front-of-house tablet vs personal phones?) but never as the unit of completion. The unit of completion is always the frontliner. ## What the manager does The store manager's role on shared devices: ensure the device is charged, ensure the platform is bookmarked or pinned, occasionally help a frontliner who has forgotten their PIN. They are not a training-delivery agent; the platform delivers itself. Managers should also have a quick-access view that shows them, at a glance, who is behind on training at their location and a one-tap message to ping them. This converts the shared device from a passive tool into an active intervention surface. ## What completion rates look like Franchises that get the shared-device model right (PIN login, instant resume, per-frontliner tracking) hit 85-90% completion on assigned training. Franchises that try to run desktop-style training on shared tablets sit in the 40-60% range. The gap is the friction at every login and resume — death by a thousand 30-second waits.

Ready to put this into practice?