Biometric Readers or Phones: How a School Should Actually Decide

How the two approaches work is well covered, including in our own explainer on biometric attendance without hardware. This piece assumes you already understand both and are now trying to write a recommendation someone has to approve. That is a procurement problem, and it turns on four questions the technology comparison rarely answers.

1. What is the five-year number, not the quoted one?

Hardware quotes are per-device and one-off, which makes them look decisive next to a recurring subscription. The comparison only becomes honest once you extend both to the life of the decision.

For a reader-based estimate, count the units you need — entrances, not buildings, and remember the gate everyone actually uses. Then add installation and cabling, the enrolment exercise for every member of staff, the annual maintenance or support contract, replacement for failure and vandalism, and the integration work to get data out of the reader and into whatever runs payroll. Schools consistently under-count the last item, because it is quoted as a project rather than a line on the hardware invoice.

For a phone-based estimate, count the subscription and the setup time, and be honest about the staff who will need help in week one. Then compare the totals over five years rather than the numbers on the two quotes.

2. What happens when you add a campus?

This is the question that most often changes the answer. A hardware estimate scales linearly — a second site means a second set of devices, a second installation, a second enrolment, and usually a second integration. A software estimate scales with headcount, which for a school group is a much flatter curve.

If a second site is anywhere in the three-year plan, model it now rather than treating it as a future problem. The decision that looks cheapest for one campus is frequently the most expensive for three. Multi-campus operation is where the two curves visibly separate.

3. What do you do with the readers you already own?

Most schools are not choosing from nothing. There are devices at the gate, possibly working, possibly bypassed. Writing them off feels wasteful, and that feeling drives more procurement decisions than anyone admits.

The useful test is whether the existing estate is producing a record you would put in front of a reviewer today. If the data is exported by hand each month, or one entrance has been broken since spring, or half the staff are marked manually because the reader does not recognise them reliably, the sunk cost is already sunk — you are paying for it in administrative time rather than capital. If it works and the data flows, keeping it and integrating is entirely reasonable, and a serious vendor should support that rather than insist on replacement.

4. What happens on the worst morning?

Compare failure modes, not features. A reader that fails takes out one entrance completely, and the fallback is a paper list that someone has to key in later — on the day everyone is already stretched. A phone-based system fails differently: a flat battery or a forgotten handset affects one person, and a supervisor records them without the whole gate stopping.

Neither is failure-proof. But a failure that affects one person is a different operational problem from one that affects three hundred, and that asymmetry belongs in the recommendation.

Where hardware still wins

There are settings where readers remain the better answer, and a recommendation that pretends otherwise will not survive scrutiny. Where personal phones are genuinely not permitted on site. Where an existing access-control system already governs doors and attendance is a by-product of it. Where a single controlled entrance handles the entire workforce and always will. And where a shared-device kiosk suits the workforce better than personal handsets — catering and facilities teams, for instance.

The common thread is a fixed, controlled, single point of entry. The further a school moves from that — multiple gates, multiple buildings, staff who move between sites — the worse the fixed-point assumption fits.

Writing the recommendation

A recommendation that survives a finance review states the five-year total for both options, models the second campus explicitly, says plainly what happens to the existing estate, and names the failure mode of each. If it does those four things, the decision usually makes itself.

See how CampusTrack handles biometric attendance, or pricing for the subscription side of the comparison.