Field showcase · every gate event

What the guard does.
What head office gets.

Left: the actual tablet screen, gesture for gesture. Right: what the guard does, the record that lands at HQ within 30 seconds, and the clever part that makes it powerful. The guard collects; head office does everything else.

HQ · liveANALYSES · ESCALATES GateLog Vehicle Staff Visitor Bus
👮
Guard collectstap · point · glance
🔒
Captured + fingerprintedon the device
🧠
HQ analysesflags · trends · ROI
📣
Auto-escalatesto the right dept

People check-ins

The high-frequency flows. Identity by recognition, structure by tap — and every record arrives with a timestamp, gate, guard and shift the guard never typed.

· Jamaica Urban Transit Co.SYNCED
Staff in / out
Search
ste
DS
Devon Sterling
Production · in 7:02 AM
IN
AS
Andre Stewart
Maintenance
OUT
KS
Karen Stephens
Admin
OUT
Checked in
Devon Sterling · 7:02 AM

🚶 Staff in / out

Hundreds a day · peaks at shift change
2 taps~3 s0 typing
What the guard does
  1. Finds the name on the board — recents float up at shift change
  2. Taps it — card flips IN, or OUT on the way home
Ledger record → HQ ≤30 s later
typestaff · Devon Sterling
entered_at07:02:14 · Main Gate
guard / shiftK. Whyte · shift #4811
time_on_sitecounting → closed by the same tap
GUARD: 1 fieldAUTO: 6 fields
Ask "who's on the compound right now?" and get an exact, named answer — any second of the day. The paper book can't.
· Jamaica Urban Transit Co.SYNCED
Walk-in visitor
Visitor name
Marcia Campbell
Host — who are they here to see?
ster
👤Devon SterlingProduction
👤Karen StephensAdmin
Linked to staff · Production
MeetingInterviewPersonal
Log entry

👋 Visitor walk-in

Type the name · the staff directory does the rest
~6 taps25 s · 10 s repeat
What the guard does
  1. Types the visitor's name
  2. Two letters of the host → taps the staff match
  3. Purpose from a chip
Ledger record → HQ ≤30 s later
person_nameMarcia Campbell
hostDevon Sterling
host_staff_idc9c6ca61-… · real staff record
host_departmentProduction
no-exit sweepflagged at midnight if never tapped out
GUARD: 3 fieldsAUTO: 8 fields
Every visitor is tied to the staff member they came to see. An unaccounted guest always has an owner to call — and HQ can see which departments pull the most outside traffic.
· Jamaica Urban Transit Co.SYNCED
Vehicle entry
KCD 4821SCANNED ✓ HIGH
⚠ WATCH LIST · DENY
KCD-4821 — reported stolen · supervisor notified
Driver / visitor name
A. Brown
Host
Staff name or department
Acknowledge to continue

🚙 Vehicle at the gate

Point & lock — no shutter · watchlist fires instantly
point & lock~6 s📷 reads itself
What the guard does
  1. 📷 Points at the plate — it reads, buzzes, locks
  2. Enters the driver / visitor name
  3. Host + purpose
Ledger record → HQ ≤30 s later
vehicle_plateKCD-4821 · scanned
scansource: camera · confidence high
photo[0]plate · sha256 9f3ab2…
watchlist_hitDENY — reported stolen · acknowledged
GUARD: 2 fieldsCAMERA: 1 photoAUTO: 9 fields
The plate is checked against the watchlist before the guard's finger leaves the screen — and a returning vehicle arrives with its whole visit history attached.
· Jamaica Urban Transit Co.SYNCED
Contractor crew
Company
Rapid Electrical Ltd
Rapid Electrical Ltd14 visits
Foreman
O. Henry
4 people+
Host / work area
Maintenance — Workshop B
Log entry

🛠 Contractor crew

One conversation, one record, the whole crew accounted for
~8 taps30 s · 12 s repeat
What the guard does
  1. Company from recents
  2. Foreman's name + crew count
  3. Work area / host
Ledger record → HQ ≤30 s later
companyRapid Electrical Ltd · visit #15
crew4 people · foreman O. Henry
host_departmentMaintenance
durationopen → on HQ's still-on-site list
GUARD: 4 fieldsAUTO: 7 fields
Each company's visit history writes itself — who's been on site, how often, how long. A crew still "in" at 6 p.m. is a question HQ can finally ask.

Fleet check-ins — the JUTC flagship

Scan the bus, pick the driver from staff, run the checklist. The guard records what they see; head office does the maths — and the guard never sees a flag.

· Jamaica Urban Transit Co.SYNCED
Departure check
JUTC-240SCANNED ✓
Driver
L. Campbell
✓ Linked to staff
Fuel level out
Copy the needle onto the gauge
FUEL
184 203
KM/H
COPY WHAT YOU SEE ↓
Full¾½¼E
!
Fare machine
Powered on & accepting payment
✓ Working⚠ Faulty
Roll out →

🚌 Bus rollout

Scan the bus, pick the driver, run the checklist — every bus, every morning
scan + checklist~20 s📷 dashboard
What the guard does
  1. 📷 Scans the bus number — it matches the roster & identifies itself
  2. Picks the driver from the staff list (or types it)
  3. Fuel level — copies the gauge
  4. Fare machine — working?
  5. 📷 Odometer — point & scan
Ledger record → HQ ≤30 s later
bus / routeJUTC-240 · HWT–Papine
driverL. Campbell · staff-linked
fuel_out / odo_out25% · 184,203 km · photo
fare_machine_okfalse → escalated to fleet office NOW
statusON ROUTE — live on HQ's board
GUARD: checklistCAMERA: 2 readsAUTO: 9 fields
Scanning the bus ties the whole trip to a number and a named, staff-linked driver — so fuel, mileage and the fare check sit against an accountable person. A dead fare box is flagged as lost revenue from minute one, not discovered at month-end.
· Jamaica Urban Transit Co.SYNCED
Return check · JUTC-240
Fuel level in
Copy the needle — guard just records it
FUEL IN8%
Passenger area
Clear
Seal / tamper
Intact
Odometer in
184,361 km · point & scan
Return recorded
No flags, no figures — just the readings

🌙 Bus return — the maths runs at HQ

The guard records readings · HQ derives every flag, invisibly
scan + checklist~15 s📷 dashboard
What the guard does
  1. 📷 Scans the bus number — finds its open trip
  2. Fuel level — copies the gauge
  3. Passenger sweep — clear?
  4. Seal / tamper — intact?
  5. 📷 Odometer — point & scan
HQ computes & escalates · guard never sees this
fuel_in8% · photo sha256 b07d11…
fuel_variance−17% → POSSIBLE SIPHON
trip_km158 km — derived, never typed
rollback checkodo_in ≥ odo_out ✓
escalationsiphon → fleet office · tamper → security
GUARD: checklistCAMERA: 1 readHQ: 10 derived
The whole anti-theft engine runs after the guard walks away. Matching this reading to the morning's catches fuel siphoning and odometer rollback — automatically, invisibly, and routed straight to the fleet office.

Every issue escalates itself

The guard never decides who to call. The moment they flag something, GateLog routes it to the right department — and to everyone who needs to know, all at once.

Automatic · by department · to multiple people

Flag it once. The right team hears about it in seconds.

Incidents, a dead fare machine, a tamper issue, a fuel-loss flag — each is matched to a department and pushed to their channel (Slack, Teams, email) the instant it's recorded. No phone tree, no waiting, no "who do I tell?"

🚨
Urgent incident
guard flags
Security team
manager + supervisors
🎫
Fare machine down
rollout check
Fleet / revenue
depot + revenue ops
🔒
Seal / tamper
return check
Security team
on-call officer
Fuel-loss flag
computed at HQ
Fleet office
fleet + investigations
Fully configurable Add a department, point it at a channel, choose which issues it hears — in Mission Control, in seconds.

Built into the tablet

The features under every flow above — each one already live on the production tablet, not a roadmap item.

Point-and-lock scanning

Plates and odometers read themselves — the guard points, it locks across frames and keeps the photo as evidence. On-device, offline, no shutter.

ML Kit OCR · crop-to-frame · confidence stamped

Watchlist, instant & offline

Flagged plates and names live on the device. A hit interrupts the flow with a full-screen alert and a buzz — acknowledged before anything proceeds.

checked at the scan · works with no signal

Offline-first, always

Every record writes to the tablet's own database first, then syncs when the network allows. A dead cell tower changes nothing at the gate.

SQLite → idempotent push · zero duplicates

Automatic escalation

Incidents and fleet faults route themselves to the right department and the right people — multiple recipients, configurable per org, the instant they're flagged.

incident → security · fare fault → fleet

White-label engine

Display name, brand accent, terminology ("Bus" → "Truck") and whole modules flip per client from Mission Control. Tablets restyle on next sync.

one binary · features ship dark, light up per org

Over-the-air updates

New features reach every tablet in the field on their next launch — no app store, no site visits. Today's scan flow shipped to the gate this way.

two tablets per gate · per-tablet lane profiles

Guard accountability

Guards start a shift with a 6-digit PIN — offline. Every record carries who logged it, on which shift, at which gate. Supervision becomes a query.

every row: guard · shift · gate · device

Honest data, swept nightly

Visits never tapped out are flagged "no recorded exit" at midnight — never silently closed. The flag rate per gate becomes a discipline metric.

runs 12:15 AM Jamaica · buses excluded

Books → data importer

Three months of paper guard books digitise into back-dated, searchable records before go-live — so the system opens with history, never empty.

validated bulk import · rollback by batch

The guard collects. Head office does everything else.

The guard

Records what's in front of them

A tap, a point, a glance down a checklist. No judgement calls, no analytics on screen, no deciding who to notify. Every gesture mirrors something physical they already do. 90-minute certification.

The tablet

Captures, fingerprints, never blocks

The camera locks the value and keeps the photo as court-grade evidence. Works fully offline. A failed read just falls back to a tap — the gate never stops.

Head office

Analyses & escalates, automatically

Fuel variance, siphon detection, trip distance, trends and ROI are computed at HQ — and every issue routes itself to the right department and the right people within seconds.

GateLog · the gate, finally talking to head office · gateloghq.com