TrackTik’s Site Tasks, Up Close: Turning the Work Between the Tours Into Proof
More than likely, your guards are doing more than the contract says.
A site manager flags a suspicious vehicle and asks someone to keep an eye on it. A fire extinguisher check is due and nobody else is going to do it. Snow gets dumped overnight and a guard clears a path before the morning shift arrives. None of it is on the tour schedule. All of it gets done anyway — and then it disappears. No timestamp, no record, no line item at renewal. Just a team that went above and beyond, and a firm that absorbed the cost without getting credit for it.
That gap is what Site Tasks was built to close.
Guard tour software does its job well: it confirms a patrol happened, checkpoints were hit, the route was completed. But a tour is binary — it started, it finished. There’s no room in that model for a task that runs three days, one that gets created on the fly at 2pm, or one that needs to be tied to a specific asset. Guard tour tells you what happened on the patrol. Site Tasks captures everything else.
We recently got on a live webinar and walked through how it works end to end — the demo, the principles behind it, the features we’ve shipped, and where it’s headed. This post is the deeper look, and if you’d rather see it in motion, the on-demand recording is available too. Here’s the substance.
What Site Tasks actually does
Start with the everyday reality. A task can be scheduled in advance or spun up on the fly when a client calls at 2pm. It carries a clear status the whole way through — pending, started, completed, or, when it slips, missed — so nothing sits in limbo.
The range is the point. The same system handles a higher-ed officer escorting a student to their car, a Clery Act check on the campus blue-light phones, a multi-day compliance inspection on a manufacturing site, and a healthcare round that needs status updates across a shift. You define the job types, write the descriptions, and decide which posts carry out which tasks, so an officer sees exactly what’s expected of them.
A few things that make it usable in the field rather than just on paper:
- It connects to what you already run. Tasks link to your existing tours and to chores, and they can be tied to specific assets — so you’re not rebuilding your operation, you’re layering structure on top of it. The result is a clean calendar view of planned work, set weekly, bi-weekly, or monthly.
- It’s built for the phone. A guard can assign a task to themselves and start it later, complete a required report with custom fields, drop a signature, and add comments — all from the app. If something more urgent comes up, they postpone and come back to it.
- It closes the loop in real time. The moment a task is finished, supervisors get the update. And it all rolls up into one report you can hand a client for any timeframe — every activity, on the record.
The three things every task carries
When we stepped back and asked what makes this work, it came down to three:
Accountability. Every task has an owner and a status. A supervisor can see what’s done, what’s in progress, and what’s been missed, in real time — no chasing people down.
Visibility. A single clear view of planned and unplanned activity across every site. No more relying on verbal updates that evaporate by the end of the shift.
Documentation. This is the one teams underestimate until renewal season — and then it’s the only thing that matters. Timestamped, auditable records of exactly what was done, by whom, and when. When the contract conversation comes, you walk in with proof.
What is available in TrackTik today
Four capabilities are live in production right now:
Reminders. Set reminders on scheduled tasks so fewer of them slip. The goal is simple — drive the missed-task rate down and keep the team on track.
Exception rules. Configure what happens when a task is missed, postponed, unfinished, or late. You can route a notification by SMS or email, or, if you run Command Center, fire it as a call-to-action that shows up right away.
Easy handoffs. Picture a guard buried under ten tasks while a teammate has five. The overloaded officer can hand a task or two off from the mobile app — no dispatcher in the middle — with an approve-or-decline step so the receiving guard stays in control. It’s a real safety valve for moments like a code blue on one floor when a security check is due on another.
Analytics dashboard. Aggregate Site Tasks data at the site, zone, or region level and start seeing patterns — including the uncomfortable ones, like a particular post that keeps missing tasks.
Where the revenue actually hides
Here’s the part that turns Site Tasks from an ops tool into a business case.
Every out-of-scope ask a guard handles — shovel the snow, run an extra check, the occasional “can you also…” — becomes a documented, timestamped record instead of an invisible favor. By the end of the day you’ve got a tally of value-added work that was never invisible to begin with.
Then the analytics do something more interesting. Using Data Lab, you can visualize the trend by user and by location and watch which ad hoc tasks keep recurring. That repetition is a leading indicator: a request your team keeps fielding for free is often a new service line waiting to be priced. Our implementation recommendation is to define an ad hoc task, tie it to your reporting, and track the volume because “here’s exactly how much extra we did for you” is one of the best conversations you can have with a client.
Questions from the webinar
Is this live or coming soon? Live. It’s been in production for a while and is an add-on to the guarding platform — not a roadmap promise.
Is there a cost? Yes, it’s a paid add-on. Pricing depends on your deployment, so loop in your account executive or client success manager, who can also help you quantify the impact.
Can a mobile unit use this? Site Tasks lives at the site level, built for static guarding — but it bridges to mobile. If a patroller can’t reach a site (protesters, an accident, a delay), they can convert that run-sheet job into a site task and hand it to the static guard already on site to complete on their behalf.
Can a Zone user who logs into a site see Site Tasks? Not today — it was built for static guarding. But we keep hearing the request, and repeated feedback is how things climb the list.
Any plans to refresh the interface? Already underway. Some of what you saw runs on our newer front-end framework, and we’re reimagining the experience more broadly — starting with the guard app, since it touches the most people.
What’s next
A few things we’re genuinely excited about:
Recurring tasks, and the auto-assign question. You can already schedule a task to recur weekly, bi-weekly, or monthly. What we don’t do is pre-assign it to a named person — a guard’s login identifies them, so starting a task is what assigns it to whoever’s actually on shift. Auto-assignment is on the table, and we want your use cases.
Duration windows. “Within 5 days,” “within 10 days” — flexible timing is in the backlog and a priority, especially for compliance-heavy sites like manufacturing.
Holiday-aware scheduling. Soon you’ll set Site Tasks around holidays, holiday eves, and the special days specific to your region — set it once, add a reminder to adjust, and stop tracking it by hand.
Agentic workflows, human in the loop. Nobody loves reassigning forty tasks on a Monday morning. We’re prototyping an AI assistant that can read your Site Tasks data and act on it — execute missed tasks, schedule the upcoming ones, handle the high-volume busywork — while a person stays in control of the decisions that matter.
The thing worth remembering
Guard tour covers the patrol. Site Tasks covers everything else — so the work your team actually does stops disappearing, and the next renewal starts with proof instead of opinions.
Want the full walkthrough? Watch the on-demand version of the webinar — including the live demo and the complete Q&A.
And to see Site Tasks running on your own sites, talk to your client success manager or account executive.
