For family venues
A kids area is a capacity, a queue, and a handover you have to be able to prove.
Checking a child in is the one operation in a venue where getting it wrong is not a billing problem. It is modelled here as capacity, a waiting list, a guardian link and a controlled release — and it stores about as little about the child as the operation can work with.
01
Capacity is a constraint, not a note on the door
A kids area seats a set number of children at once. Every other kind of resource ships with a capacity of one, which is the exclusive behaviour a console or a billiards table needs; the kids area is the case that made capacity a real number, and check-in is checked against it.
- Occupancy is answerable at any moment: how many places there are, how many are active, how many are paused, how many are free, and how many people are waiting or have been called.
- A check-in into a full area is refused, with the option of taking a place in the queue instead of failing.
- A child already checked in cannot be checked in twice; the refusal names the session they are already in.
- A shared area does not go to paused because one child’s session paused — the area is not the session.
02
The queue, for when it is full
A waiting ticket walks from waiting to called to seated, or is cancelled, and it carries a position in line, the guardian it belongs to, the wristband code, the party size and a note. Tickets expire after twelve hours, so yesterday’s queue is not this morning’s.
- The queue is deliberately not a booking. Parking waiting tickets on the reservations table would have leaked invented bookings into the reservations screen, the no-show sweep and the covers forecast, so it is kept as its own append-only record of what happened.
- Position is computed from the ledger rather than stored, so a cancellation in the middle does not leave a gap that someone has to renumber.
- Calling a family and seating them are two different events, which is what lets you measure how long a called family took to arrive.
03
Who is responsible, and who may take them home
A child is not a separate kind of person in the system: they are a participant in the party, with a link to the adult responsible for them. That link is what the release rules are built on, and the rules are the reason this page exists.
- Releasing a child to anybody other than the guardian on file requires a manager’s PIN and a written reason, and the PIN is only accepted from someone who actually holds the approval permission.
- A guardian cannot simply leave the party while their ward is still checked in. They must name another adult in the party, and the handover is written to the audit trail with the reason it happened.
- The system refuses obviously wrong guardians — a child cannot be their own guardian, and another kids-area guest cannot be named as one.
- The remaining-time warning and the end-of-session notice go to the guardian, because the person who needs to know is the one holding the bill.
04
What is stored about a child, and what is not
There is no child profile in this system, and that is a decision rather than an omission. A child is a display name, an optional wristband or QR tag code, and a link to whoever is responsible for them. There is no age, no photograph, no medical note and no parent-and-child entity.
- The check-in request has no field for a name, an age, a photo or a note about the child, so there is nowhere for that data to arrive even by accident.
- The wristband code is an operational identifier for finding a child in a room, not an identity record.
- Anything more would be sensitive data about a minor that a venue has no operational reason to hold, and holding it is a liability rather than a feature.
05
The bill a family actually gets
One party can hold an indoor table, a console in the gaming room and a child checked into the kids area, and close on a single check — or split, by person, by item, into equal shares or by percentage.
- Each participant carries a spending policy: unlimited, a fixed limit, approval for everything, approval above a threshold, or no purchases at all.
- A purchase that trips a policy raises an approval the host resolves, rather than being silently refused at the counter.
- A charge for a child routes to whoever is paying for them, so a kids-area hour is not a separate errand at the end of the evening.
- A party cannot close over unsettled money or a running timer, so nobody walks out mid-session by accident.
06
Asking for something, and saying how the evening went
A parent with a child in one room and a coffee going cold in another should not have to catch a waiter’s eye. From the code at the table a guest raises a real request — a waiter, water, the bill — and it is routed to whoever covers that area rather than shouted across the floor. The same phone carries the venue’s offers, and at the end it carries the question of how the evening actually went.
- A service request walks from raised to accepted to done, so a wait is a number rather than an impression, and one nobody has picked up escalates instead of ageing quietly at the bottom of a screen.
- Offers and coupons are visible to the guest on their own phone, in their own language, so a family sees what is running without a member of staff having to remember it.
- Feedback is a rating out of five with food, service and speed scored separately, which is what turns a bad night into a cause rather than a mood.
- A poor rating opens a service-recovery case while the family is still in the building, rather than surfacing in a report a fortnight later.
Questions about the kids area
What do you store about a child?
A display name, an optional wristband code, and a link to the adult responsible. That is the whole record. There is no age, no date of birth, no photograph, no medical or allergy note and no parent-and-child entity, and the check-in request has no field for any of them, so there is nowhere for that information to be entered even by mistake. The refusal is built into the system rather than left to a policy someone remembers: anything more is sensitive data about a minor that a venue has no operational reason to hold.
Can anyone collect a child from the kids area?
No. Releasing a child to the guardian on file is an ordinary check-out; releasing them to anyone else needs a manager’s PIN and a written reason, and the PIN is only accepted from a member of staff who genuinely holds the approval permission — a supervisor cannot lend a code they do not have. The override, the person who authorised it and the reason they gave are written to the audit trail, which is read-only by design.
What happens when the kids area is full?
The check-in is refused and the family can take a place in the queue instead. A waiting ticket holds their position in line, the guardian it belongs to, the wristband code, the party size and a note; calling them and seating them are separate events, so the wait and the walk-up are two different numbers; and a ticket expires after twelve hours so a forgotten queue does not carry over to the next day.
Bring the handover you are most nervous about.
The uncle who arrives to collect, the guardian who wants to leave early, the Friday when the area is full at seven. Those are the cases worth walking through.
A time, a screen share, and your own floor plan on the screen.
[email protected]