01 / 03 Shift board
The shift board fills in, team by team, as colleagues arrive. Each row is a role, a token, a door and a time.
On shift, on time.
For government departments and any workplace that runs on shifts: cover shows up in tomorrow's report. The shift board fills in, team by team, as colleagues arrive.
For government departments, hospitals, schools, hotels, plants and any workplace that runs on shifts: each shift's cover as colleagues arrive, not in tomorrow's report. A Pulses Vision device above the staff door verifies staff who enrolled with consent, so colleagues just walk in, with no badge to find and no tap at the door. The shift board in Pulses Ops fills in team by team, by role and time, with every building on one page, and a sign-in that doesn't verify goes to the supervisor to confirm on WhatsApp, Teams, SMS or email. Names stay on your own servers, on the on-site Pulses Compliance Guard, and retention is set by your policy. Where your policy requires it, only enrolled staff are analysed. All processing happens on the device; only anonymous metadata leaves.
From the door to the supervisor.
- 01
Pulses Vision above the staff door
A Pulses Vision device above the staff door verifies staff who enrolled with consent. Contractor shifts too, where the contractor's employer consents. Colleagues just walk in: no badge to find, no tap at the door.
- 02
Enrolled staff, verified on the device
Names stay on your own servers; the board shows roles and times. Where your policy requires it, only enrolled staff are analysed.
- 03
Supervisors see each shift's cover, by role
The shift board fills in, team by team, as they arrive, with every building on one page. A sign-in that doesn't verify goes to the supervisor to confirm, on WhatsApp, Teams, SMS or email.
By design All processing happens on the device; only anonymous metadata leaves.Anonymous Unique FaceID is made on the device and can't be turned back into a picture; staff who enrolled with consent link it to their staff record.Names stay on your own servers, on the on-site Pulses Compliance Guard.Retention is set by your policy.
Shift, policy, confirm.
01 / 03 
02 / 03 Workplace policy
Where your policy requires it, only enrolled staff are analysed. Consent on file, names on your own servers, retention set by you.
03 / 03 To confirm
A sign-in that doesn't verify goes to the supervisor to confirm: confirmed on shift, or not on this shift.
The staff door, the shift.
Transcript
At the staff door, the morning shift arrives. Yet whether the front desk is covered shows up later, in a report. Pulses. AI for the physical world. A Pulses Vision device above the staff door verifies staff who enrolled with consent. Colleagues just walk in: no badge to find, no tap at the door. The shift board fills in, team by team, as they arrive. Names stay on your own servers; the board shows roles and times. Where your policy requires it, only enrolled staff are analysed. A sign-in that doesn't verify goes to the supervisor to confirm. Over one hundred and fifty million journeys counted across Pulses deployments. Designed and made in the UAE. See the full showcase.
Take it to your team.
-
Deck · PDFThe staff door and the shift, in slides
The story for HR, facilities and your data protection officer.
-
Leave-behind · PDFThe two-page summary
Print-ready. Hand it on after the walkthrough.
Questions from HR and facilities teams
How do I stop buddy punching on badge readers?
There is no badge to pass to a colleague. A Pulses Vision device above the staff door verifies staff who enrolled with consent as they walk in, and the shift board fills in by role and time. A sign-in that doesn't verify goes to the supervisor to confirm: on shift, or not on this shift.
Can we analyse staff only, without analysing customers, when privacy rules require it?
Yes. Where your policy requires it, only enrolled staff are analysed. Consent is on file, names stay on your own servers on the on-site Pulses Compliance Guard, and retention is set by you. The shift board shows roles, tokens, doors and times, not names.
Where is the data stored? Do you keep face images or video?
Processing happens on the Pulses Vision device, and only anonymous metadata leaves it. Names stay on your own servers, on the on-site Pulses Compliance Guard, and retention is set by your policy. Anonymous Unique FaceID is made on the device and can't be turned back into a picture; staff who enrolled with consent link it to their staff record.
Can a government department run it entirely on its own servers?
Yes. Pulses can run fully on your own servers, with no cloud dependency, for teams whose data has to stay on site. Either way, processing happens on the Pulses Vision device, only anonymous metadata leaves it, and names stay on the on-site Pulses Compliance Guard.
Does it work across many buildings, and outside government?
Yes. Every building and every shift sit on one page, so HR sees cover across sites without asking each one to report. The same staff-door set-up fits a government department, a hospital, a school, a hotel or a plant: anywhere colleagues work shifts and come in through a staff door.
Walk your staff doors with us.
We go through your buildings, doors, shifts and workplace policy with you.
More in Government
-
Branch experience Unique visitors, not tickets. -
Culture events Hold every event to one standard. -
Culture sites Know where your visitors go next. -
Inspection network A vehicle's attempts, side by side. -
Perimeter and contractors Unique visits, day and night. -
Service centres One customer, one journey. -
Vehicle inspection Each required check: done, or skipped. -
Pulses for Government 8 use cases in Government -
Every use case All 27 use cases
