From the gate to the door

Security and the gate

A visitor log that names the guard, not just the guest.

The barrier is the front of the society

The barrier is the front of the society. GateBee treats it that way: geofenced attendance so a punch from the next street is flagged, visitor passes tied to a unit, and daily-help visits that are not modelled as society staff — they still hit the same log.

When the night shift leaves, the admissions they made stay on their staff profile. Payroll and a dispute at 9am use the same record. The committee does not reconstruct the night from a paper register and a WhatsApp screenshot.

Geofence

A punch is only on duty inside the radius

Named

Every admission stores the guard who opened

Unit

Passes are checked against the flat, not a nickname

Shift

The log outlives the person who handed over

The punch

Attendance starts with a roster. A punch without a shift is a timestamp looking for a story. The staff app asks the person at the barrier to punch inside the society's geofence. The radius lives on the society; enforcement is a switch the owner admin turns on — it cannot be armed until a point exists.

A punch from the next street is flagged. That is the whole point of the fence: the boom is a place, not a suggestion. If map tiles cannot load on a private network, the picker still takes coordinates as numbers so the society is not stuck waiting for a satellite photo.

The pass

Cabs, deliveries and guests share one log. The staff app shows the pass against the unit. The guard who admitted them is stored on the row — so “who opened the barrier?” is a query, not an argument in the office at 9am.

The resident approved from the phone, or pre-approved before the car arrived. The desk can read the same admission later. Nobody has to reconstruct it from a CCTV clip and a first name.

Daily help is not society staff

The cook, the nanny, the driver who arrives every morning — they are regular at the boom, and they are not on the society's payroll. GateBee does not pretend they are guards with a different badge.

Their visits still hit the same gate log the committee reads in the morning. The unit they serve is on the row. Mixing them into the staff directory is how societies lose both a clean roster and a clean visitor history.

After the shift

Handover is not a verbal summary. The next guard punches in; the previous admissions stay on the staff profile that made them. The desk can filter a night, a person, or a unit.

That is what “24/7” means here: the log outlives a shift change. It is not a claim that a person sits in a control room we have not sold you.

What the barrier records

Geofenced attendance

A punch from the next street is flagged. The radius lives on the society, and enforcement is a switch the owner admin turns on.

Visitor accountability

Every admission is tied to a staff profile, so a later dispute has a person, not a shift.

Daily help, separately

Regular workers are not modelled as society staff. Their visits still hit the same gate log the committee can read in the morning.

Gate, staff, daily help

The boom is the front of the society
The boom is the front of the society
Admissions stay on the staff profile
Admissions stay on the staff profile
Regular workers still hit the same log
Regular workers still hit the same log

At the barrier

Walk the desk on your own society

Bring the registration number and a rough unit count. We will show the property tree, a shift, and the gate flow — not a generic slide deck.

Book a walkthrough