Skip to main content

Operational Workflows & Use Cases

Workflows built around how guarding companies actually run.

Explore how Plethora replaces disconnected spreadsheets and manual handovers across multi-site deployment, shift rostering, attendance confirmation, and payroll preparation.

01

Multi-site guard & post coordination

For operators managing 50 to 250+ guards across diverse client locations

Internal operating base

The Operational Challenge

When client site requirements, post counts, and assigned guards are tracked in separate spreadsheets, controllers cannot easily see which locations are under-assigned or how contract changes affect staffing.

Connected Outcome

Operations managers and controllers work from a single site registry that feeds directly into shift rostering, attendance sheets, and client billing.

Step-by-Step Operational Flow
  1. Register each protected location once with its service type (Guarding, Access Control, or Patrols), risk rating, and client contacts.
  2. Break each site into day and night posts with explicit required guard counts.
  3. Assign active guards directly to sites or posts and view live assigned-versus-required status badges.
Governed by per-module role permissions and audit loggingRequest a walkthrough of this workflow →
02

The connected roster-to-payroll chain

Eliminating manual re-keying between scheduling, timesheets, and pay runs

Internal operating base

The Operational Challenge

Re-typing shift schedules into attendance spreadsheets and then re-entering hours into payroll software wastes administrative hours and introduces calculation errors at month-end.

Connected Outcome

The roster you publish becomes the timesheet you confirm, and the approved timesheet becomes the audit evidence for the payroll you run.

Step-by-Step Operational Flow
  1. Generate pay-period-aligned rosters using standard patterns (3 on 3 off, 4 on 4 off, weekdays, or custom rotations).
  2. Review day and night shifts separately on the site timesheet, capturing Duty ON and Duty OFF Occurrence Book (OB) numbers and reliever replacements.
  3. Run the five-stage payroll workflow (Attendance → Create run → Calculate → Approve → Mark paid) where approved timesheets drive hourly guard pay and statutory calculations.
Governed by per-module role permissions and audit loggingRequest a walkthrough of this workflow →
03

NBCPSS leave & relief coverage coordination

Managing annual, sick, family responsibility, parental, and study leave

Internal operating base

The Operational Challenge

Approving leave without checking cycle balances or coordinating relief cover leads to uncovered posts or timesheet conflicts during payroll calculation.

Connected Outcome

HR and control room teams maintain clear leave balances while active development continues on deeper in-context leave-and-attendance conflict resolution.

Step-by-Step Operational Flow
  1. Preview leave requests against the employee's leave rules and current cycle balance before submission—accounting for public holidays inside annual leave periods.
  2. Route requests through a structured approval queue with full audit history.
  3. Assign available relief officers on the site roster and timesheet so replacement hours are captured for payroll.
Governed by per-module role permissions and audit loggingRequest a walkthrough of this workflow →
04

Role-based access control & onboarding migration

Bringing existing security company records online safely

Internal operating base

The Operational Challenge

Migrating off legacy spreadsheets is risky if bad data is written blindly or if every administrative user has unrestricted access to payroll and billing.

Connected Outcome

Security companies onboard clean operational records while preserving strict separation of duties across control room, HR, and finance staff.

Step-by-Step Operational Flow
  1. Configure company parameters once—PSIRA registration, tax number, UIF reference, pay period, and employee ID prefix.
  2. Download structured employee and site CSV templates and run pre-write validation so every formatting error is listed before records are saved.
  3. Assign per-user, per-module capabilities (View, Create, Edit, Delete, Approve, Export) with strict company data isolation.
Governed by per-module role permissions and audit loggingRequest a walkthrough of this workflow →
Structured Onboarding & Pilot Scoping

Evaluate Plethora through a controlled operational pilot.

We work directly with South African private security operators to discover your current rostering, attendance, and payroll workflow, import existing employee and site CSV records with pre-write validation, and define clear success criteria for a controlled pilot.