Tarabeeza
العربية

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, how many children it covers 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 a record the venue keeps between visits, and the adults who may collect them hang off it — usually two, and brothers and sisters share both. That link is what the release rules are built on, and the rules are the reason this page exists.

  • Any adult on the child’s record may collect them, and that is an ordinary check-out. Releasing the child to anyone else takes a manager’s PIN and a written reason, and the PIN is only accepted from someone who actually holds the approval permission.
  • The handover is settled before anything is stopped or billed, so a collection that is refused leaves the child checked in rather than half-released with a timer still running and nobody paying for it.
  • An id that is not a guardian record at all is refused before the override is even reached, and no PIN buys past that — which is what makes signing a child out to another child impossible rather than merely discouraged.
  • Who actually collected the child is written down by name against the session they were in, and “a guardian collected them” is not accepted as the answer where more than one adult is on file.
  • A warning goes out at ten minutes left and again at five, addressed to the guardian rather than to the child, and once however many times the sweep runs. Where the venue already knows that adult as a customer it reaches their phone; otherwise the attendant walks over, which is what a kids desk does anyway.

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 and, where the venue issues one, a wristband code. There is no age, no date of birth, no photograph and no medical note, and the check-in has no field for any of them. What is held beside it is a way to reach an adult — a name, the number the desk calls and a second number to try — because a child who cannot be handed back to anybody is the situation the whole record exists to prevent.

  • The check-in takes a name for the child and nothing else about them — no age, no photo, no free-text note — 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, and it is reused between visits — which is what makes a returning child a lookup at the desk rather than a re-registration every Saturday.
  • 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.
  • The records expire on their own. Every visit moves a deletion date forward, and an hourly sweep removes a child nobody has brought back inside the retention window, along with any guardian left with nobody on file.
  • Reading that list at all is its own permission, held by the kids desk and by nobody on the floor — a waiter can see that the area is busy and cannot see who is in it.

05

The bill a family actually gets

An indoor table, a console in the gaming room and a child checked into the kids area close on a single check, and nobody has to describe the family to the software first. There is no group to build and no host to nominate. The kids-area session is run as part of the table the family is sitting at, and that is the whole of what decides where the hour is billed.

  • A visit has exactly one master check, and it belongs to the visit rather than to the table, so the family who sits down next never inherits the last one’s running total.
  • Check the child in against the table and the hour lands on that table’s open bill by itself. Where there is no table — the parent who drops the child off and leaves — the desk names the bill instead, and a session with neither is refused rather than billed to a guess.
  • The bill settles whole, or splits: the items picked out one by one, into equal shares, or by percentage. One check takes more than one tender, walking from open to partly paid to paid as each lands, and it refuses a payment larger than what is outstanding.
  • A check that still owes money refuses to close and names what is outstanding, and a time charge cannot reach a bill that has already closed — the till refuses it by name rather than quietly dropping an hour of play.

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, and a wristband code where the venue issues one. That is the whole of the child’s own record: no age, no date of birth, no photograph and no medical or allergy note, and the check-in has no field for any of them, so there is nowhere for that information to be entered even by mistake. What is held beside it is a way to reach an adult — a name, the number the desk calls and a second number to try — because a child who cannot be handed back to anybody is the situation the record exists to prevent. It does not stay, either: every visit moves a deletion date forward, and an hourly sweep removes a child nobody has brought back inside the retention window along with any guardian left with nobody on file. Reading that list at all is its own permission, held by the kids desk and by no one on the floor.

Can anyone collect a child from the kids area?

No. Releasing a child to any adult on their own record 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. Who collected the child is written down by name, and the override, the person who authorised it and the reason they gave go to the audit trail, which is read-only by design. An id that is not a guardian record at all is refused before the override is reached at all, so a child can never be signed out to another child.

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, how many children it covers 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.

Write to us
Book a demo

A time, a screen share, and your own floor plan on the screen.

[email protected]