ONGOING INDEPENDENT COVERAGE
Questions Buyers Are Asking# Workflows for Physical Security and Campus Incident Management
This piece breaks down where a general system holds up for physical security work, where it needs outside help, and what to ask before you rely on it for anything urgent.
Last updated: 6 September 2026
If a door alarm goes off at 2am, or a fight breaks out in a parking lot, or a camera flags someone in a building after hours — something has to catch that, send the right person, and keep a clean record of what happened. Many companies and campuses try to handle this inside the same system they already use for IT help tickets.
ServiceNow is the most common example, since it already sits inside so many organizations for other reasons. The question worth asking is simple: is a system built to track a broken laptop also built to handle a live safety event?
The three shapes, side by side
Everyday facility reports | Live security events | Reports required by law | |
|---|---|---|---|
What it is | A broken lock, a spill, minor property damage | An alarm, a break-in, a fight, a lockdown | A crime or safety event that must be logged and shared on a set schedule |
What matters most | Getting it fixed eventually | Getting the right person there fast | Getting the record exactly right, on time |
How fast it needs to move | Hours to days | Seconds to minutes | Set by law, not by the company |
Biggest risk if it goes wrong | A small delay, mildly annoying | Someone gets hurt, or the response is too slow | Fines, legal trouble, loss of trust |
1. Does the alert reach the system by itself, or does someone have to type it in?
A camera or an alarm going off is not the same as someone filling out a form. For the system to help in real time, it needs to hear about the alarm the moment it happens, without a person typing it in first.
Our reading: We could find no sign that ServiceNow reads a live camera feed or an alarm system on its own. Getting a device alert into ServiceNow as an incident needs a separate connector app, built by an outside company, added on top.
Ask for a full list of every extra app or connector needed to bring in camera, alarm, or badge data — and what each one costs, separately from the main license.
2. Who tells a guard where to go, and how fast?
An IT ticket sits in a queue until someone picks it up. A live security event cannot wait in a queue — it needs a person sent, right away, to the right spot.
Our reading: ServiceNow's own security tool, called Security Incident Response, was built to manage computer security problems — things like a phishing email or a data leak — not to send a guard to a physical location. Dispatching a real person to a real place in real time is a different job than the one that tool was designed for.
Ask how an alert actually turns into a person standing at the right door — and how many steps sit between the alert and that person moving.
3. Can it prove a guard actually walked the route?
A patrol route only works if someone can later prove it happened — not just that a ticket says it did.
Our reading: Tools built specifically for campus and site security often include a way to prove a guard was physically at a checkpoint at a set time. A general ticketing system was not built with that kind of proof in mind.
Ask how the system proves a guard was physically present at a location and time — not just that a record was created and closed.
4. Does it know the difference between a routine report and one the law requires you to share?
Some safety events are just internal record-keeping. Others must be reported publicly, on a fixed schedule, because a law says so — for example, certain crimes on a school campus in the United States.
Our reading: A general system tends to treat every incident record the same way. A record that must be reported externally, on a deadline, needs its own tracking — a flag, a due date, a reminder — separate from an ordinary internal report.
Ask whether the system automatically flags which incidents must be reported outside the company or campus, and by when — without relying on someone to remember.
5. Does the record hold up if it is ever needed outside the building — in an investigation or in court?
An IT ticket rarely needs to survive outside the company. A safety incident record sometimes does.
Our take: this is where a general system shows its age fastest. A record meant to hold up later — locked once written, limited in who can touch it, clear about who saw it and when — takes deliberate design. Most general-purpose systems were not built with that use in mind from day one.
Ask what happens to a record once it is closed: who can still edit it, who can see it, and whether that access is tracked.
Where a general system like ServiceNow fits
A company already running IT, HR, and facilities requests through one system, with a small in-house safety team, mostly low-urgency reports, and no legal deadline pressure — for that company, adding safety reports to the same system it already trusts can be a reasonable, low-cost choice.
Where it does not fit
A live guard dispatch operation. Any site with a legal reporting deadline it cannot afford to miss. Any building with heavy camera or alarm use that needs alerts to arrive automatically, without a person typing them in first, and without paying for a separate connector app to make that happen.
FAQs
Is ServiceNow a bad choice for physical security? Not automatically — it depends on what the site actually needs. It fits well for record-keeping and low-urgency reports. It fits poorly for live dispatch, camera and alarm-heavy sites, and legally required reporting deadlines.
Do all physical security tools handle these the same way? No. Some tools are built mainly for a single site with light needs. Others are built for guard dispatch, patrol proof, and legal reporting deadlines from the start. The gap between the two is usually where a buyer gets surprised.
What is the one thing most buyers forget to check? Whether alerts from cameras, alarms, or badge systems arrive on their own — or whether someone has to notice the alert first and type it in by hand.
This is a piece of opinion — our reading of what buyers should ask, based on public material available as of the date noted above. It is not a statement of fact about any company. No company mentioned pays for the mention. Any company named here can write to hello@analystlayer.com; we respond within three working days and update the piece where the input is factual, with the update dated on this page.