Why Guard Management Software Can Ruin Your Business

The Trackforce Team

Trackforce

December 23, 2015 · 12 min read

Guard management software risks that can hurt a security business

Here’s the thing: 9 times out of 10 implementing guard management software is really beneficial for a business. But there was one time when guard management software wasn’t the best solution for one of our clients.

Key takeaways

  • The software does not create the problem, it reveals one.
    If tours are not being completed, visibility makes that visible. That is the tool working correctly, not failing.
  • Transparency has a sequence, and most firms get it backwards.
    Run it internally first, fix what it exposes, then give the client access. Opening the door on day one is what turns a good decision into a lost contract.
  • Software cannot substitute for supervision.
    Officers who know there are no consequences behave the same whether or not their position is being recorded.
  • A client threatening to terminate already knows.
    “They never knew what we weren’t doing” is rarely true. They usually knew, which is why they were calling.
  • For firms doing the work, this is pure upside.
    Being able to show the record is how single-property contracts turn into whole portfolios.

You think you need guard management software when … the client is ready to terminate

A client called and said, “We need guard management software because the customer is questioning whether we are doing the job.”

So we visited the customer and did a demo. We showed how GPS was integrated in the guard management software and we could use a QR code at each checkpoint. We set up task assignments and memos with complete instructions for the guard. As long as the officer was doing what he was supposed to do, everything would show up fine. And the customer, who had been ready to terminate, said he would stay on because he liked the software as a management tool.

Guard management software won’t help when … you don’t care whether guards do their jobs

Unfortunately, what showed up when we implemented the software was that the guards weren’t doing their jobs. We got really hands on at that point supervising the guards. But the guards knew there was no accountability within their company, and they just didn’t care.

So then our customer came back to us complaining: “Before I had Silvertrac, the client never knew what we were or weren’t doing.”

“But the client was going to terminate,” we said. “They knew.”

And ironically, they lost the contract to another one of our clients who uses the software. So ultimately, it wasn’t guard management software that ruined the business.

Here’s the thing. If you need to keep customers in the dark to retain clients, then you’re a firm that shouldn’t use guard management software. In your case, it will ruin your business, because it will show that the guards aren’t doing their jobs.

Guard management software works when … your company is ready to show off great work

Guard management software provides some transparency. Companies that do a great job get recognized for it. I love hearing that a company that started with one property has won the whole portfolio, or that a local company is going after a multimillion-dollar HOA contract because they are able to use reports to show what a good job they do.

If your guards aren’t doing their jobs, you still need guard management software. Just don’t take it to your clients. Use it yourself to supervise better right from your own computer. Get your own business better first, then you can let your clients see it.

Even a good company can tune up its services with guard management software in response to specific customer concerns. For example, if you learn that the customer is concerned about afterhours pool use, you might gather data about who is using pools after hours and what hours they’re there. That lets you manage afterhours use without having to lock 40 pools at 40 sites at the same hour, which you can’t do within your staff count. That is the same instinct behind answering client complaints with evidence rather than reassurance.

Guard management software gives more visibility into your operations, and the tools you need to improve those operations, which contributes to growth.

Work out where you actually are first

The story above has a single lesson buried in it: the software did exactly what it was supposed to do, and the firm was not ready for the answer. So before you buy anything, be honest with yourself about which row of this table you are in, because it changes what you should do on day one:

Where you actually are

What the data will show in week one

What to do about it

Officers are doing the work, you just cannot prove it

Completed tours and checkpoint scans that back up everything you have been claiming

Open client access almost immediately, because the record is your best salesperson

Officers are mostly doing the work, with gaps at one or two sites

A clear pattern by site, shift or supervisor rather than a vague sense that something is off

Fix the named sites first, then open access. You are weeks away, not months

You genuinely do not know what is happening in the field

Missed checkpoints, late clock-ins and reports filed from the wrong place

Run it internally only. Supervise from the data for a full quarter before any client sees it

Officers are not doing the work and supervisors know

A record that documents the problem in detail, including who knew

Internal only, and treat it as a management issue rather than a software rollout

A client is already threatening to terminate

Whatever is true, which may not help you

Be honest about the timeline. Software buys credibility only if the underlying work improves too

You would rather the client did not find out

Exactly what you are hoping to avoid showing them

Do not buy it yet. The tool is not the problem you need to solve first

Only the last row is a reason not to buy. Every other row is a reason to buy and sequence the rollout properly.

Signs you are not ready to give clients access yet

Client-facing visibility is the goal, not the starting point. Hold it back a little longer if any of these are true:

  • Tour completion is below where you would want a client to see it. Work out your baseline privately first. You cannot improve a number you have never measured.
  • Checkpoints are in the wrong places. Early rollouts often put checkpoints where they are convenient rather than where the client actually cares. Fix the map before anyone looks at it.
  • Officers have not been told what is being recorded. Surprising your team with monitoring damages trust faster than it improves compliance, and the compliance gain is temporary anyway.
  • Supervisors are not yet using the data. If nobody internally looks at the dashboard, handing it to a client means they will be the first person to notice a problem.
  • Reports are still inconsistent between officers. Guided templates in the guard app fix this quickly, but give it a few weeks to settle before it becomes client-facing.
  • You have no plan for what to say when something is missed. Decide in advance who tells the client and how, because the first exception is the moment that sets the tone for the whole relationship.

How to get ready in 60 days

  1. Days 1 to 14: internal only, and say so. Tell your supervisors and officers that the first phase is about establishing a baseline, not catching people out. Resist the urge to discipline off week-one data, which is always messy.
  2. Days 15 to 30: fix the sites, not the software. Move checkpoints to where the client walks, correct post orders, and deal with the one or two posts generating most of the exceptions. Most of what looks like a data problem is a site setup problem.
  3. Days 31 to 45: get supervisors using it daily. A five-minute morning look at yesterday’s exceptions builds the habit. If supervision does not change, nothing else will either.
  4. Days 46 to 60: open one client, deliberately. Pick your best-performing site and your most reasonable client. Walk them through it in person rather than emailing a login, and ask what they would actually want to see.
  5. Then roll outward, worst client last. The account you are most anxious about is the one to open when your operation is strongest, not while you are still finding your feet.

The version of this that ends well

The firm in this story lost the contract to another firm using the same software. That is the part worth sitting with. The tool was never the variable; the willingness to know what was happening in the field was. TrackTik will show you completed tours, position data, incidents and response times whether or not you are ready to look at them, and for security firms already doing the work, that record is the most persuasive thing you own.

If you want the straightforward version of the argument, it is worth reading why letting clients see for themselves builds trust faster than any report you write about yourself, and what not using guard management software actually costs. When you are ready, book a TrackTik demo and we will walk it through against one of your own sites rather than a sample account.

Frequently Asked Questions

Not by itself, but it can accelerate an outcome that was already coming. If tours are not being completed, the software documents that, and if you hand a client access on day one they will see it before you have fixed it. The damage comes from the sequencing, not the tool. Run it internally first, correct what it surfaces, then open client-facing reporting once the record supports you.

Eventually, yes, and it is one of the strongest retention moves available. But not on the first day. Establish your baseline privately, fix the sites generating most of the exceptions, get supervisors using the data daily, then open one well-performing site with a reasonable client and expand from there. The account you are most nervous about should be last, not first.

Then it has done its job, and you have information you did not have last week. Resist disciplining people off week-one data, which is always noisy while checkpoints and post orders get corrected. Look for patterns by site, shift and supervisor rather than by individual, because clustered problems are usually structural. Guard management gives you the pattern; the management response is still yours.

Sometimes, and it is a reasonable thing to try, but be careful about what you are promising. A client at that point is usually asking to be shown the service is real, and a demo of live tours and reporting can genuinely reset the conversation. What it will not do is compensate if the underlying work does not improve alongside it. Buy yourself credibility and then earn it.

Tell them first, and lead with the safety case rather than the compliance one. Officers accept position tracking far more readily when it arrives with lone worker protection and a panic alarm attached, because the same feature that shows a supervisor where they are is the one that gets help to them. Be specific about what is recorded and when, confirm it is limited to shift hours, and brief supervisors not to use it for petty management.

Yes, provided you are ready to be transparent with yourself. The internal value stands on its own: knowing which posts are covered, which reports are complete and where response times sit. Plenty of firms run it internally for a quarter before a client ever logs in. The only situation where buying makes no sense is if you specifically need clients not to find out what is happening, because then the tool is solving the wrong problem.

Usually 30 to 60 days. The first two weeks are messy while checkpoint placement, post orders and report templates settle. By week four you generally have a clean picture, and by week eight you have enough history to show a trend rather than a snapshot, which is far more persuasive. You can book a TrackTik demo to see what a client-facing view looks like before you commit to the timeline.

Related resources

More on proving the work to clients