What is SOP automation?
SOP automation means running a standard operating procedure as a digital workflow instead of a document. The steps are the same. What changes is that the system routes each step, checks it is done and records it.
A PDF procedure on a shared drive tells people what to do. It cannot tell you whether they did it. An automated SOP can, because each stage has an owner, a form and a time stamp.
Tools such as Worxit's SOP workflow automation software build each procedure as a template, then run it the same way every time. For the general case for automating business processes, see workflow automation for South African companies. This guide covers how to choose and map the SOPs themselves.
Which SOPs should you automate first?
Start with procedures that are frequent, involve several people and must leave evidence. Score each candidate against these six tests.
| Test | Why it matters | Example |
|---|---|---|
| It runs often | Frequent procedures repay the set-up effort quickly | Officer onboarding at a growing company |
| More than one person or team is involved | Hand-offs are where work stalls and nobody knows who has it | Purchase requests passing operations and finance |
| It needs a sign-off | Approvals given verbally or by message are hard to prove later | Closing an incident investigation |
| It must leave evidence | Clients, insurers and inspectors ask for records | Monthly site safety inspections |
| Skipped steps cause real harm | A workflow will not move on until the step is done | Checking registration before deploying an officer |
| The procedure is stable | A template that changes weekly confuses everyone | Not a process still being redesigned |
In security and facilities, four SOPs usually pass most of these tests: officer and contractor onboarding, incident investigation, routine inspections and purchase approvals. Pick one, prove it works, then move to the next.
Which SOPs should not be automated?
Do not automate the first response to an emergency. An officer at a fire or a medical emergency must act from training and posted instructions, not open an app.
- Emergency response. Automate the follow-up instead: the report, the investigation and the corrective actions.
- Rare one-off tasks. A procedure used once a year rarely repays the set-up.
- Procedures still being rewritten. Settle the process on paper first, then build it.
- Single-person tasks with no sign-off. A checklist form is often enough.
How do you map an SOP into workflow stages?
Map the procedure as it really runs, then turn each hand-off into a stage. These eight steps work for most SOPs.
- Walk the SOP with the people who do it. The written version and the real one often differ. Record what actually happens, then decide what should.
- List every step and mark each hand-off. A hand-off is any point where the work moves to another person or team.
- Group steps into stages. A stage ends when the work changes hands or needs a decision. Most SOPs have four to seven stages.
- Assign each stage to a role, not a name. "HR administrator" still works when a person leaves. "Thandi" does not.
- Define what each stage must capture. Form fields, checklist items, photos, documents or a signature. Capture only what someone will use.
- Place the approvals. Decide who approves, on what evidence, and which stage the work returns to if it is rejected.
- Add branches and parallel stages. Use a branch when a condition changes the path, such as a high value. Run independent stages side by side.
- Pilot on one site, then review. Look at where runs wait longest and which fields nobody fills in. Change the template before rolling it out.
Approvals deserve the most thought, because that is where workflows stall. Our guide to approval workflow design covers approval levels, parallel approvals and rejection in detail.
What does an automated officer onboarding SOP look like?
Onboarding is a good first SOP: it runs often, crosses several teams and must leave records. The stages below are an illustrative example for a guarding company.
| Stage | Role | What the stage captures |
|---|---|---|
| 1. Request | Operations manager | Site, post, grade required and start date |
| 2. Document check | HR administrator | ID, PSIRA registration and grade, training certificates, uploaded as documents |
| 3. Approval gate | HR manager | Approve with a signature, or return to stage 2 with a reason |
| 4a. Uniform and equipment (parallel) | Stores | Items issued, with the officer's signature |
| 4b. Payroll set-up (parallel) | Payroll administrator | Checklist confirming the officer is loaded |
| 5. Site induction | Site supervisor | Checklist of site instructions covered, signed by the officer and supervisor |
| 6. Close | Operations manager | Confirms the officer is ready for deployment |
Stage 2 is there for a reason, set by the PSIRA Code of Conduct (regulation 11(2)). Before employing an officer, a security service provider must take reasonable steps to verify their registration status, training and qualifications.
Stage 5 supports another duty. Officers must be properly informed about the nature and scope of their duties and their legal powers (regulation 11(5)(a)). A signed induction stage shows this was done for each site. This is a summary, not legal advice.
Stages 4a and 4b run in parallel, because stores and payroll do not depend on each other. The workflow waits for both before the site induction starts.
If the registration grade does not match the post, the HR manager returns the run to stage 2 with a reason. The operations manager can see why the start date is at risk, instead of finding out on the officer's first day.
How do incident, inspection and purchasing SOPs map?
The same method works for other procedures. Each one has a clear end point and one place where a decision is needed.
| SOP | Stages | Decision point |
|---|---|---|
| Incident investigation | Incident logged, investigation with statements and photos, root cause and corrective action, client notified, closed | Operations manager signs off the findings before the client is told |
| Routine site inspection | Inspection checklist with photos, faults logged, repair assigned, repair confirmed with a photo | Facilities manager confirms the repair before the fault closes |
| Purchase request | Request with quotes, budget holder approval, order placed, goods received with a photo | A branch sends requests above a set value to a second approver |
An incident investigation often starts from an occurrence book entry. Keep the entry as the record of what happened, and use the workflow for what the company did about it.
Decide at the start what closes each workflow. An investigation closes when the corrective action is confirmed, not when the report is written. An inspection fault closes when the repair photo is accepted.
How do you roll out automated SOPs without losing your team?
Most rollouts fail on people, not software. Keep it small and visible.
- Involve the people who run the procedure in the mapping, so the template matches real work.
- Keep forms short. Every field should have someone who reads it.
- Pilot one SOP on one site before adding others.
- Name an owner for each template who approves changes and keeps a version history.
- Set a date to retire the paper form, so two systems do not run side by side for months.
- Review where runs wait longest each month, and fix the stage, not the person.
What records should an automated SOP keep?
Each run should show who did each stage, when, what they captured and every approval or rejection with its reason. That record is what clients, auditors and insurers will ask for.
Onboarding and investigation workflows hold personal information. Under POPIA, collect only what is adequate, relevant and not excessive (section 10). Keep it no longer than needed unless an exception applies, such as a legal or contractual requirement (section 14). Protect it with reasonable technical and organisational measures (section 19).
Where a law requires information to be retained, the Electronic Communications and Transactions Act allows it to be kept electronically. The record must stay accessible, keep its original format or an accurate one, and show its origin, destination, date and time (section 16). This is a summary, not legal advice.
How does Worxit handle SOP automation?
In Worxit's Workflows module, each SOP becomes a reusable template with sequential stages. Each stage can have its own forms, checklists and approval requirements.
- Stages are routed automatically to the assigned role or user.
- Approval gates hold the workflow until it is signed off. An approver can reject a stage and return it to an earlier one.
- Approvals and sign-offs can be captured as digital signatures.
- Conditional branching handles different paths, and stages can run in parallel when the logic allows.
- Photos and documents can be attached at any stage, and every step is time-stamped.
- Analytics show active runs, completion times and where runs are held up.
The dashboard licence is R600 per month, including one admin user. Additional dashboard users are R75 per user per month. Each phone, tablet or radio running the app needs a R350 monthly device licence. All prices exclude VAT.
Frequently asked questions
What is SOP automation?
SOP automation turns a written standard operating procedure into a digital workflow. Each step becomes a stage with an owner, a form or checklist and, where needed, an approval. The system routes the work to the next person and records who did what, and when, instead of relying on memory.
Which SOPs should be automated first?
Start with procedures that run often, involve more than one person, need a sign-off and must leave evidence. In security and facilities, that usually means officer onboarding, incident investigation, routine inspections and purchase approvals. Leave procedures that change every month until they settle down.
Does automating an SOP replace training?
No. Officers and staff still need to understand why each step exists and how to handle exceptions. Automation makes sure the steps happen in order and are recorded. Training makes sure people do them properly. Use the workflow to prove training happened, for example with a signed site induction stage.
Should emergency procedures be automated?
Not the first response. An officer facing a fire or a medical emergency must act from training, not fill in a form. The follow-up can be a workflow: the incident report, the investigation, corrective actions and closure. Keep emergency steps on posted instructions and in drills.
How long does it take to automate an SOP?
It depends on how many stages, people and forms the procedure has. Most of the effort goes into mapping it with the people who run it; building the template is quicker once stages, roles and forms are clear. Then pilot it on one site before rolling it out, so you can fix steps that fail in practice.
Sources
- Code of Conduct for Security Service Providers, 2003. PSIRA. Regulation 11(2) and 11(5)(a): duties of employers of security officers.
- Protection of Personal Information Act 4 of 2013. gov.za. Sections 10, 14 and 19.
- Electronic Communications and Transactions Act 25 of 2002. gov.za. Section 16: retention of information as a data message.