For guarding, cleaning and facilities contractors

The site instruction changed on Friday. Here is every officer who confirmed it before the shift.

A named record of who acknowledged the procedure, by client site, on the officer's own phone with no company email. When the client audits the site, the record is produced on the spot.

Everything on this page ships today. Roadmap items are marked and not sold.

Kayden Connect feed for a fictional Gauteng guarding company. A pinned announcement, Use of force and incident reporting procedure revision 3, shows 552 of 610 acknowledged with an Acknowledge button.
The same pinned procedure on an officer's phone, with a full-width Acknowledge button and the count 552 of 610.
552 of 610 acknowledgedRemind 58 pending

608,977security officers were active in South Africa's private security industry at 31 March 2024, across 16,453 active registered businesses. Every one of them works on a client's site, under that client's instructions.Source: PSIRA, Annual Report 2023/24, section 7.2. Industry figure, not a Kayden Connect result.

The situation

The procedure changed. The guardhouse copy cannot say who read it.

A guarding contractor with 42 client sites revises its use-of-force and incident reporting procedure. The change goes out at the 06:00 parade on the sites that hold one, and a printed copy goes to each guardhouse. Three weeks later a client's auditor asks which officers on their site were informed, and when. The contracts manager has a parade register from nine sites and a photo of a guardhouse notice three revisions old. The company employs 610 officers, most without a company email.

Today
  • A parade on some sites, a printed copy in each guardhouse.
  • A register from nine of 42 sites.
  • The client's auditor gets a photo.
With the record
  • One announcement, pinned at every site.
  • 552 confirmed by name and site; 58 pending, reminded.
  • The client's auditor gets the evidence pack for their site.
How it works

Four screens, all shipped.

1Publish

One procedure, pinned at every client site, on every phone.

The contracts manager publishes once. On HQ the approval rule holds it until the operations director has signed it off. Officers see it pinned on their own phone at the guardhouse and confirm with one tap before the shift.

Every plan · approval before publishing on HQPSIRA Code of Conduct for Security Service Providers
The pinned announcement card: Use of force and incident reporting procedure, revision 3, in force from Monday 7 September, with an Acknowledge button and 552 of 610 acknowledged, 90%.
One tap to confirm
2Reach

Officers without company email join with a code and their phone.

A site supervisor issues one single-use code per named officer. The officer enters it with their phone number, gets a one-time text, and is in. SMS carries the sign-in code only; notices never go by SMS. 96 joined this month.

Every plan · role-gated, capped per workspace per monthPSIRA Code of Conduct for Security Service Providers
Frontline access codes: 41 active codes, 96 joined this month, 610 of 650 seats used, 118 of 700 SMS this month, and an officer table with phone binding and status by site.
The Join screen on a phone: access code SGD-5W8N, a masked phone number, a Send my code button and the three steps that follow.
3Record

By client site, by name, with the time.

Riverside Office Park 36 of 38. Sandton retail cluster 88 of 97. One reminder to the 58 still pending, at most once every four hours, so the officers who did their part are left alone. The site that is behind is visible before the client asks.

Coverage by department and site on Command and HQPSIRA Code of Conduct for Security Service Providers
4Require

Turn the site instruction into required reading with a due date.

Incident reporting and occurrence book procedure 2026: 563 complete, 38 not started, 9 never asked because they have no site set. Late is marked late. When the client audits, the evidence pack for their site is one click on HQ.

Who has read it: 563 of 610 complete, 38 overdue, Remind all, Export as CSV and Evidence pack buttons, and a named roster by site with Waiting and Acknowledged late labels.
Required reading on a phone: Use of force and incident reporting revision 3 due Sep 7, three documents marked Done.
What you must evidence

The people who can ask for the record, in their own words.

South Africa · PSIRA Code of Conduct for Security Service Providers
“has been properly informed about the nature and scope of his or her functions and duties as well as his or her legal powers in this regard”
Regulation 11(5)(a), what a security business must ensure for every security officer

What the record gives you"Properly informed" gets a named record per officer and per site: the procedure, the site instruction, the date confirmed.

South Africa · PSIRA Code of Conduct for Security Service Providers
“provide training or cause such training to be provided, to all the security officers in his or her employ”
Regulation 11(7), on the legal provisions and the principles of the Code

What the record gives youRequired reading with due dates shows who has and has not confirmed the Code briefing, by site. The training itself is yours; this is the record of who received it.

United States · New York General Business Law, security guard training
“an eight hour annual in-service training course”
Section 89-n(1)(d); eight-hour pre-assignment course under 89-n(1)(a)

What the record gives youThe certificate proves the course. The record shows which officers received the site instructions and the procedure changes between courses, by client site and date.

Cited as what a contractor must be able to show. Kayden Connect does not certify compliance with any of them.

Read this before the demo

What it does not do.

It is not a guard-tour or workforce system.No patrol check-ins, no posting sheets, no rostering. It carries the communication and the record of it.
It is not training.An acknowledgement confirms receipt. The PSIRA grade course and the parade are the training.
It does not certify compliance.It produces the record you evidence with.
Plans

Where this use case lands.

Spark$4per user per monthfrom 5 seats · monthly or annual
  • Acknowledgement on any post
  • Frontline access codes
  • Required reading with due dates
  • Analytics for the last 7 days

A handful of sites and an owner who needs the record and nothing else.

Command$8per user per monthfrom 10 seats · monthly or annualEverything in Spark, plus
  • Pinned announcements
  • Coverage by client site
  • Anonymous pulse surveys
  • Analytics for the last 90 days

Ten or more sites, and a contracts manager who needs to see which one is behind.

HQ$15per user per monthfrom 25 seats · annualEverything in Command, plus
  • Approval before publishing
  • Evidence pack per site and audit log export
  • Executive dashboard, 365-day analytics

Client audits, a regulator, an approval chain and an audit trail. The organisation on this page. Talk to us.

USD per user per month. Annual billing saves 20% on Spark and Command. Every limit is on the pricing page.

The organisation on this page

Sentinel Guarding

Gauteng, South Africa · 42 client sites, 610 security officers · HQ plan

A fictional organisation. Every name, number and screen on this page is invented to show how the product behaves.

Security and facilities sales kit: two-page PDFTwo pages, USD prices, the evidence lines with links.

Bring the site instruction nobody can prove was read.

Early access is by invitation. Tell us about your organisation and we will be in touch.

Same record, other situations