How to digitise a security company: a step-by-step path from paper and Excel

The order to digitise a security company: employee records, clients and posts, payroll, billing, field operations, and how to bring supervisors and guards along.

  • StrataMax team
  • 9 min read
On this page

To digitise a security company, move your work into one system in the order the data depends on itself: first a clean employee master, then clients, posts and shift rates, then payroll, then client billing, and only then field operations such as mobile check-in, patrol visits and incident records. Each step uses the lists built in the step before. Doing it out of order, for example handing guards a check-in app before posts and shifts are set up, is the most common reason a rollout stalls.

The second half of the job is people. Supervisors and guards have to change how they work, and the office has to stop accepting the old paper and spreadsheet versions. This guide covers both: the order, what to check at each step, how to manage the change, and what to measure so you know it is working.

Why does the order matter when you digitise?

A security company runs on a chain of records. A guard is employed, assigned to a post at a client, works shifts, gets paid, and the client is billed for the post. Every record further down that chain points back to the ones above it.

Record Depends on
Employee Nothing (it is the starting point)
Client and post Nothing, but needs the contract terms
Assignment and shift Employee, post
Attendance Assignment, shift, post location
Payroll Employee, attendance, shift rates
Invoice Client, post, contract rate
Patrol visit, incident Post, client, employee

If the employee list has duplicates, every later step inherits them: two payslips for one guard, two SSF lines, a wrong head count on the client invoice. Fixing data at the top of the chain is cheap. Fixing it after it has flowed into payroll and billing means reversing payments and issuing credit notes.

That is why the old advice to “start with attendance” needs care. Attendance is the most visible change, but it sits in the middle of the chain. It only works once guards, posts and shifts already exist.

Step 1: How do you build a clean employee master?

One list, one row per person, with no duplicates. For each employee:

  • Full name as on the citizenship certificate, and phone number.
  • PAN and SSF ID where they exist. If a number is missing, leave it blank and chase it. Never fill the column with another number to make it look complete.
  • Bank name and account number.
  • Basic, dearness and other allowances, and the joining date.
  • Documents: citizenship copy, photo, training and other certificates.
  • Current client and post.

Mark leavers as inactive rather than deleting them. Their history is needed for final settlement, SSF and tax records.

This step usually takes longer than any other, and it is where most of the value is. Errors that have sat in spreadsheets for years (a basic entered as gross, a guard on two client sheets) surface here. Our article on when Excel stops working for a security company covers the field-by-field clean-up and the parallel payroll run in more detail.

Step 2: How should clients, posts and shifts be set up?

Enter every client, every post at every client, and the shifts each post runs. For each post record:

  • The site address and the area within which a guard counts as “at the post” (needed later for location-checked attendance).
  • The shifts (for example 06:00 to 18:00 and 18:00 to 06:00) and how many guards each shift needs.
  • The shift rates used for guard pay, including the overtime rate for that shift.
  • The contract rate used for billing the client.

Then assign each active guard to a post and shift. A quick test of this step: the number of guards assigned per client should match the head count on the last invoice you sent that client. If it does not, find out why before moving on. The difference is either a billing error or a staffing gap.

Step 3: When should payroll move?

Once employees and posts are clean, move payroll. Run at least one month in both the old spreadsheet and the new system and compare guard by guard: head count, total basic, employee and employer SSF, TDS and net pay. Every difference has a cause, and it is often an old spreadsheet mistake.

Payroll is the step guards notice. A guard who is underpaid by the new system loses trust in everything that follows, including the mobile app you will ask them to use next. Do not switch until the parallel run matches or every difference is explained and accepted.

Things to settle during this step:

  • Which allowances are part of basic and which are not, since SSF is calculated on basic.
  • The overtime rate for each shift, and that it meets the Labour Act (the Act’s overtime rules are covered in our overtime calculation guide).
  • Who prepares, who checks and who approves each payroll batch.

Step 4: How should billing move?

Move billing after payroll, because both use the same client and post list. Run one month of invoices from the new system alongside your current method and compare each invoice line by line.

If your company must use IRD-approved billing software, or report invoices to CBMS, check that this step is done with software that meets those rules and that invoice numbering continues correctly from your old series. Record receipts in two parts, cash received and TDS withheld by the client, so client balances do not show false outstanding amounts.

Step 5: How do you roll out field operations?

Field operations come last because they depend on everything above: the guard, the post, the shift and the post’s location.

Roll out in batches, not all at once:

  1. Pick a pilot group of five to ten posts under one reliable supervisor, ideally with a mix of day and night shifts.
  2. Install and log in each guard on the mobile app during a supervisor visit, not by phone.
  3. Run check-in alongside the paper register for a short, fixed period, for example two weeks. Compare them daily.
  4. Fix the post areas where check-ins fail because the area is drawn too tight or in the wrong place.
  5. Add patrol visits and incident records once check-in is stable, starting with the same supervisor.
  6. Stop accepting the paper register at those posts on a set date, then move to the next batch.

Patrol visits and incident records have their own guides: running patrol visits across many posts and incident reporting for security companies. Location-checked attendance is covered in GPS attendance for security guards.

How do you bring supervisors and guards along?

Software rollouts in guard companies fail more often for people reasons than for technical ones. A few rules help.

Supervisors first

Supervisors are the link between the office and the posts. Train them before the guards, give them the app first, and make them responsible for their posts’ check-in rate. A supervisor who understands the system will answer most guard questions on the spot.

Keep the guard’s job short

A guard should need only a few steps: open the app, check in at the start of the shift, check out at the end, and request leave. Anything more at the start (long forms, many screens) leads to missed check-ins.

Plan for guards without smartphones

Some guards will not have a suitable phone, or will have one that is often out of charge. Decide in advance how their attendance is recorded, for example by the supervisor on the guard’s behalf with a reason, and review those cases weekly so the exception does not become the rule.

Explain what the data is for

Guards will ask whether the company is tracking them. Be clear and accurate: location is checked when they check in and out, to confirm they are at the post. Put this in writing, in plain language, and stick to it.

Answer pay questions fast

In the first payroll months, set aside time for salary queries. A wrong payslip that is fixed within days builds trust. One that drags on for weeks undoes the rollout.

Set an end date for the old way

Parallel running is a safety net, not a destination. Announce the date after which paper registers, spreadsheet payroll or manual invoices are no longer accepted, and keep to it. Two systems running indefinitely is more work than either one alone.

What are the common mistakes?

Mistake What happens Better approach
Starting with the mobile app Guards check in to posts and shifts that are not set up; data has to be redone Set up employees, clients, posts and shifts first
Importing spreadsheets without cleaning them Duplicates and wrong basics carry into payroll and SSF Clean the employee master before import
Switching payroll without a parallel run Guards are under- or overpaid in the first month Run one month in both and reconcile
Using several unconnected tools The same guard and post are kept in three places and drift apart Keep employees, posts, payroll, billing and field records in one system
Rolling out to every post at once Problems at many posts at the same time; supervisors overwhelmed Pilot five to ten posts, then batches
Letting the old method continue Staff keep using what they know; new data is incomplete Set and keep a cut-over date
Skipping access rules Everyone can see and change everything Give owners, accounts, supervisors and guards different access

What should you measure to know it is working?

Do not judge the project by feel. Pick a few measures, record your starting point before you begin, and check them monthly. Use your own numbers; there is no industry benchmark to compare against.

Measure How to count it Why it matters
Payroll preparation time Days from month end to approved payroll Shows whether manual work has actually reduced
Payroll corrections Number of payslips changed after approval Shows data quality
Check-in rate Shifts with a recorded check-in divided by shifts scheduled, per post Shows adoption and problem posts
Manual attendance entries Attendance entered by office or supervisor instead of the guard Should fall over time; a rising number needs a reason
Invoice issue date Days from month end to invoices sent Earlier invoices mean earlier cash
Head count mismatch Guards assigned versus guards billed, per client Catches unbilled posts and staffing gaps
Patrol visits completed Completed versus scheduled visits Shows supervision is happening
Open incidents Incidents still open or investigating after a set period Shows follow-ups are being closed

Review these in a short monthly meeting with operations and accounts. Our guide to security company reporting covers the wider set of weekly and monthly reports an owner should look at once the data is in one place.

Checklist: digitising a security company

  • Record starting figures for the measures above before you begin.
  • Build one clean employee master; no duplicates; missing IDs left blank, not filled in.
  • Mark leavers inactive instead of deleting them.
  • Set up every client, post, shift, shift rate and contract rate.
  • Check guards assigned per client against the last invoice.
  • Run one parallel payroll month and explain every difference.
  • Agree who prepares, checks and approves payroll.
  • Run one parallel billing month and check invoice numbering continues correctly.
  • Record client receipts with TDS withheld shown separately.
  • Train supervisors before guards.
  • Pilot mobile check-in at five to ten posts with the paper register alongside.
  • Decide how attendance is recorded for guards without a working smartphone.
  • Tell guards in writing what location data is used for.
  • Add patrol visits and incident records after check-in is stable.
  • Set and keep a cut-over date for each old method.
  • Review the measures monthly.

How StrataMax supports this path

StrataMax keeps the whole chain in one system: employee profiles with documents, certificates and equipment issue and return; clients and posts; payroll with SSF, TDS, overtime, Dashain allowance, approvals and payslips; IRD-approved VAT billing with receipts that record TDS withheld; and patrol visits, incidents, expenses and leave. Guards use the Android app for their assignments, check-in and check-out, and leave requests. Book a demo to plan a rollout around your own posts.

Frequently asked questions

What should a security company digitise first?

Start with one clean employee master, then clients, posts and shift rates. Payroll, billing and field operations all depend on those two lists, so digitising them first stops the same mistakes being copied into every later step.

Should attendance be digitised before payroll?

Attendance and payroll should be planned together, but the records come first: a guard's check-in is useless if the guard, the post and the shift do not already exist in the system. Most companies move payroll once records are clean, then roll out mobile check-in post by post.

How long does it take to digitise a security company?

There is no fixed time. It depends on how clean your records are and how many posts you have. Plan at least one parallel payroll month and one parallel billing month, and roll field operations out in batches of posts rather than all at once.

How do you get guards and supervisors to use a new system?

Train supervisors first and make them responsible for their posts, keep the guard's steps short, run the old and new methods side by side for a short, fixed period, and then stop accepting the old method. Answer pay questions quickly, because guards judge the system by whether their salary is right.

Next step

Let StrataMax do this every month

Payroll with SSF and TDS, IRD-approved billing and every guard and post on one record. Book a 30-minute walkthrough.