A charter school network in New York — automated attendance and continuous safety monitoring across three campuses at full occupancy.
A charter school network in New York needed accurate, automated attendance and continuous safety monitoring for every student and member of staff — across three campuses at full occupancy, and not as a register taken at the end of the day.
Attendance was taken on paper and in the SIS. Emergency procedure depended on printed lists carried to muster points. Between classes — the periods of highest movement and highest risk — the building's knowledge of where anyone was fell to zero and stayed there until the next register.
None of that is negligence. It is the standard operating model of practically every school in the world, and it is only visibly inadequate in the minutes when it matters most.
The original brief was one use case: automated daily attendance. A proof of concept was built to test exactly that — and what it actually demonstrated was the value of the infrastructure underneath it. Once the canopy existed, each further use case was a configuration, not a project:
This is the infrastructure argument proven in the hardest environment there is: one use case justified the project, and the canopy made every use case after it marginal.
The requirement was continuous sub-metre coverage of very large, densely occupied multi-floor buildings, on a per-square-metre budget a school can defend to a board. That combination rules most things out quickly.
The tag decision drove as much of the design as the locator decision did. At eight thousand units, cost, battery life, charging logistics and replacement workflow are the difference between a system that runs for years and one that quietly decays.
This is what "we design and manage the project" looks like in practice — one design, held across the partners best placed to deliver each layer of it.
No single vendor could have delivered this alone — and a single-vendor design would have forced compromises at every layer. The ecosystem is not overhead; it is how the right answer gets built.
Adoption is the quiet killer of people-tracking projects. A new device to carry, remember and charge is a device that ends up in a drawer — and at eight thousand students, even a small refusal rate breaks the system's promise.
Students and staff already wore ID cards on lanyards. So Fluidity designed a custom tag housing — manufactured with MOKOSmart — where the existing ID card slides into rails on the tag itself, and the whole thing hangs from the same lanyard they were already wearing. Zero change of process. Zero new habit to build. The tag disappeared into something that already existed.
Inside: custom firmware written for the newest version of Quuppa's location logic.
The deliverable was not a dashboard. It was a change in what the organisation is able to establish: during an evacuation, during an ordinary Tuesday, and afterwards when someone asks what actually happened.
Three problems, and all of them were scale. Coverage: continuous positioning across every floor of large, multi-storey buildings — not a pilot corridor, everywhere, because attendance that works in most rooms is attendance that does not work. Confidence: room-level had to mean genuinely room-level. A tag that drifts through a classroom wall marks a student present in the wrong lesson, and one wandering dot per class is enough to send the register back to paper. Surge: hundreds of tags pouring through the same entrance in the same few minutes at the start of day — the RF equivalent of rush hour, arriving at precisely the moment the data matters most.
The first campus is where the design was earned: locator layout and tuning tested against reality until all three problems held at once. The campuses that followed inherited that layout as a template — the difference between a rollout and three consecutive experiments. The tag ran its own gauntlet: three-plus years on a battery, waterproof, and tamper-proof enough to survive eight thousand school-aged owners.
The thinking above is the free part. A discovery call is where it gets specific to your site.