why school staff need a different kind of time clock
Most time clock software is built for an office. It assumes an email address, a personal device, an onboarding message somebody will read, and fifteen quiet minutes to click through a setup wizard. Almost none of that is true of a bus driver, a cafeteria worker, or a night custodian.
So the software gets bought, the office staff use it, and everybody else stays on paper. That is the actual outcome in a lot of districts, and it is precisely the outcome Tocko is shaped to avoid. If the largest hourly departments cannot use it, it has not solved anything.
The punch screen is a keypad and nothing else. Type your PIN and you are done. There is no clock in button and no clock out button to press by mistake, because Tocko works out which one you meant from your last punch: if you were out, you are now in. The screen then tells you in words what just happened, so nobody has to guess whether it registered.
Nobody needs an email address. An employee ID and a PIN is a complete account. Where typing a PIN is itself the barrier, a printed QR badge scanned by the device camera, or a staff card tapped on a reader, does the same job. That alternative is not a nicety: WCAG 2.2 asks for a route that does not depend on memorizing and retyping a number, and this is it. Both options are off until a super admin turns them on.
A forgotten PIN is handled at the kiosk for anybody who has an email address on file: press the forgot link, identify yourself, and follow the emailed reset. For staff with no email, which in a school is a real share of them, an admin resets it instead. That is the honest cost of not requiring an email address to have an account.