No installed application
The core workflow operates through a web-based QR process.
The LivePOB operational visibility model.
LivePOB combines recorded operational activity with deliberate status reporting. Daily operations establish the best available personnel picture; incidents convert that picture into confirmed SAFE, HELP and unaccounted-for populations.
The LivePOB Operational Visibility Model
Access-control events
Visitor assignments
Hard-zone transitions
Soft-zone updates
Mobile-zone records
SAFE / HELP reports
LIVEPOB
Device Irrelevant.
Resolves identity, site, zone context, status and time into one current operational view.
Person Identified.Device Irrelevant.
Current POB view
SAFE / HELP / unresolved
Map and location snapshots
Multi-site dashboards
Movement Path & evidence
Incident reporting
Daily Operations
Accountability starts before the alarm.
1
Employees, contractors and visitors are registered or imported into the platform.
2
Access events, assignments, zone changes and available integrations update the current operational picture.
3
Authorized users review personnel-on-board, site, zone and visitor information from centralized dashboards.
4
Recorded events remain available for historical review, reporting and investigation.
LivePOB does not create this visibility by continuously tracking every phone. The platform uses the events, assignments and reports available to the organization.
Employees, contractors and visitors
Access events, assignments and zone changes
Centralized dashboards
Historical review, reporting and investigation
1The organization activates the incident or muster workflow.
2Personnel report SAFE or request HELP.
3SAFE, HELP and unaccounted-for populations are updated.
4–5Follow-up, review and documentation.
During an Incident or Drill
5
The organization activates the incident or muster workflow.
6
Personnel report SAFE or request HELP from the safest available location using any suitable connected device.
7
LivePOB updates confirmed SAFE, HELP and unaccounted-for populations as reports are received.
8
HSE, Security and Operations focus follow-up on HELP requests and people who have not responded.
9
Recorded actions and timestamps remain available for post-event review and documentation.
QR identity
Any suitable internet-connected device
SAFE
HELP
SelfMuster: Identity Independent of the Device
The reporting identity belongs to the person, not to the handset. A person can use their own phone, a colleague's phone, a supervisor's device, an HSE or Security device, or another suitable internet-connected device to scan the assigned QR identity and submit a status report.
No registered handset
The status report is associated with the person's identity, not with one specific phone.
No proprietary emergency hardware
The core workflow does not depend on dedicated muster readers or terminals.
Any suitable connected device
A practical communication path is enough to submit SAFE or HELP.
No Report Means No Assumption
LivePOB does not assume that a person is safe because a badge crossed a gate, a phone was previously detected or a last-known position appeared outside an affected area. Until a confirmed status is received, the person remains visibly unaccounted for.
ALARM / DRILL
Accountability is required.
SAFE
Person deliberately confirms SAFE.
HELP
Person deliberately requests assistance.
NO RESPONSE
Person remains visibly unaccounted for until contacted or physically verified.
Point-in-Time Location Context
When device permissions and capability allow, a transaction may include GPS coordinates as point-in-time context. The coordinate is attached to that recorded event; LivePOB does not create a continuous GPS stream. Location helps provide context, but the person's deliberate SAFE or HELP report remains the operational status.
Existing Systems Can Contribute Data
LivePOB can use information from existing turnstiles, access-control systems, gates, RFID readers, visitor platforms and operational databases when suitable interfaces or approved data access are available.
Turnstiles
Access-control systems
Gates
RFID readers
Visitor platforms
Operational databases
Designed to integrate with existing systems through available APIs, databases, interfaces, or approved data-exchange methods.
See the Workflow in Your Environment
A focused demonstration can be configured around your sites, personnel groups, zones and existing infrastructure.