A handover verdict is computed fresh from the register on every scan. Nothing held on the device - a cached name, an old tag reading - can turn an unauthorized collection into a confirmed one.
An adult who isn’t on a competitor’s authorized list is refused, logged as a denial, and named to staff if they’re a known adult at all. Nothing is released on a guess.
The one place discretion is allowed is also the one place it’s hardest to abuse alone: a member of staff records why, then a different staff member confirms it with their own login before it’s released. Both names go on the record.
Every handover - confirmed, denied, overridden - is append-only. Not even an admin can rewrite what happened after the fact.
Event Guardian runs many clubs on shared infrastructure, but one club’s children, adults and records are never reachable from another’s - enforced at the database, not just hidden in the interface.
Competitor and adult photos are held in private storage and served through links that expire - there is no public URL for any image in the system.
Record each approved adult’s checks and when they expire. An expired check warns staff at the handover screen - enough to use their own judgement on the day, without a false-positive lockout on a busy one.
Whether a competitor may be photographed is recorded against them - set by staff at registration, or by a linked parent from their own account - and surfaced right alongside their name at handover.
Set an expected end time once, and anyone still checked in past the grace period is flagged and escalated automatically - the same alert a manual session close raises, without staff needing to remember to close it.
Export a register, the handover log, or the alert history as CSV - or a single formatted PDF covering an entire event, ready to hand to a committee.
If a child is missing
Flag a competitor missing, and any scan of their band - by staff at a handover, at roll call, or by a member of the public with no app and no sign-in at all - raises a full-screen alert naming who's looking for them and how to reach that person. A member of the public sees only a plain thank-you page: never the child's name, photo, or anything that identifies them. Staff who've opted in are notified on their phone the instant it happens, even with the app closed and the screen locked.
Where it runs
UK region only
Event Guardian's database runs in the UK. Each club's data is separated at the database layer, not just kept apart in the app you see - a query for one club's children and authorized adults simply cannot return another club's data, by construction rather than by convention.
Club A
Club B