What does a guarding platform actually hold?
A guarding platform built through add-ons holds three kinds of operating record: what officers observed and did, how the work was staffed, and how quality was checked. Each acquired company arrives with its own archive, usually in a different scheduling or reporting app, which is why integration is the moment to look.
| System | Records | Why AI labs and data users value them |
|---|---|---|
| Workforce management and scheduling | Shift schedules, call-offs, fill decisions, overtime approvals, license and training checks | Staffing under hard constraints is a planning problem agents are being trained to handle |
| Guard tour and patrol tracking | Checkpoint scans, patrol routes, missed-tour exceptions and supervisor follow-up | Timestamped sequences show routine work and where it breaks down |
| Incident and daily activity reporting | Narratives, incident types, escalation steps, follow-up actions | Observation, classification, escalation and outcome in one record |
| Post orders and site procedures | Duties per post, escalation trees, emergency steps | Written rules that can be compared with what officers actually did (client-confidential, see below) |
| Quality and account management | Supervisor site inspections, client complaints, corrective actions, quarterly business reviews | Findings paired with fixes give clear outcome labels |
| Remote video monitoring and dispatch | Alarm events, operator dispositions, dispatch decisions | High-volume judgment calls with recorded results |
| Sales and bids | RFP responses, staffing models, win and loss notes | Proposal reasoning tied to results |
| Email, Teams and shared drives | Branch manager threads, training decks, SOPs | Context that links the other systems together |
The value is in the links between these systems: an incident that led to a post-order change, a complaint that led to a staffing change, a missed tour that led to retraining.
Which guarding companies fit?
SourceX's baseline is a business in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) that reached 50+ full-time employees at peak (contractors excluded), has operated for several years with documented records, holds the rights to what it would license, and has an owner or executive able to sponsor the deal. Guarding needs one extra check: payroll counts are inflated by part-time and on-call officers, so look at full-time officers, supervisors, dispatchers and branch staff at the busiest point. Subcontracted guards and off-duty police officers arranged through a coordinator are not full-time employees.
Sub-segments that tend to keep the deepest records:
- Contract manned guarding for commercial real estate, industrial sites, distribution centers and corporate campuses
- Mobile patrol and alarm response, where every call has a timestamped disposition
- Remote video monitoring, where operators log each alarm decision
- Event security for repeat venues, with years of staffing plans and incident logs
Executive protection and government-cleared guarding usually produce thin or restricted records. An add-on that has already been folded into the platform, or a branch that was wound down, can still qualify if its records exist. The who qualifies page has the full baseline.
How to screen add-ons during integration
Integration is when old apps get switched off, so screen each add-on before its systems retire. Use the branch archive screen:
- ☐Is the platform, or the add-on screened on its own, at 50+ full-time employees at peak (contractors excluded)?
- ☐Are incident and activity reports from before the acquisition still retrievable outside the seller's old app?
- ☐Which scheduling, tour and reporting tools did the add-on use, and when will each be shut off?
- ☐What do the add-on's client agreements say about who owns reports and how site information may be used?
- ☐Who at the platform (CEO, CFO or another authorized representative) can own the conversation?
| Integration step | Record risk | What to ask |
|---|---|---|
| First 30 days: systems inventory | Nobody lists the old reporting app | Which tools held reports, schedules and tours, and since when? |
| Scheduling cutover | Only active schedules migrate | Can the full shift history be exported first? |
| Reporting app sunset | Contract ends and history disappears | Is there a complete export with attachments before cancellation? |
| Branch consolidation | Shared drives and inboxes are deleted | Who decides what is archived and where? |
The incident and on-call records checklist covers the same ground for any company with dispatch-style records.
Rights and confidentiality pitfalls in guarding
Guarding records mix the company's own work with client secrets and personal details, so the rights review matters more here than in most service businesses.
- Post orders and site security plans describe a client's layouts, access procedures and weak points. Treat them as client-confidential and out of scope unless the client agrees, and even then strip site identifiers.
- Incident narratives name members of the public, suspects, witnesses and employees, and may reference police reports, medical events or camera footage. They need de-identification or exclusion, and video or body-worn camera footage is generally out.
- Officer personnel files, including background checks, license records and drug tests, stay out.
- Hospital and clinic accounts can put patient details into incident reports; those records stay out unless properly de-identified.
- Client contracts sometimes state that reports belong to the client, which would take them out of scope.
For platforms with California operations, the CCPA gives California residents rights to know, delete and opt out of the sale or sharing of their personal information where a business meets the law's thresholds, which is one more reason personal details are removed rather than licensed. This is general information, not legal, tax or financial advice. The company's counsel decides what can be included, and de-identification rules are agreed before any work begins.
Why sponsors are looking inside guarding platforms now
Longer holds raise the bar for value creation. Bain's Global Private Equity Report 2026 puts buyout holding periods at exit at around seven years, up from five to six years over 2010-2021, and notes that almost 40% of portfolio companies have been held more than five years. A guarding platform several years into its hold has accumulated add-ons, archives and a story to tell at exit.
A data license is not a margin lever in the usual sense. It is usually paid once, for a license that gives the buyer exclusive AI-training use of agreed records on agreed terms, priced as one net payout from SourceX, and the company keeps ownership of its records. Plan for it as a one-off, not as recurring revenue.
Who can make the introduction?
The person closest to the CEO usually makes it: the operating partner, the deal partner on the board, or an integration lead who has seen the archives. The operating partner playbook covers the role in more detail, and the guide to assessing portfolio company data opportunities explains how to run the review across a whole fund.
From there the sequence is short:
- The introducer registers and submits the platform through the referral form, or sends the CEO a referral link to apply directly.
- SourceX reviews size, history, record breadth and rights with the CEO or CFO.
- The platform's operations team builds a data inventory listing systems, years covered and exclusions such as post orders and personnel files.
- Price and terms are fixed with the platform before any SourceX reviews the opportunity.
- If the platform signs, records are de-identified as agreed, delivered and paid for. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.
Nobody on the sponsor side exports or forwards reports at any stage.
A conversation starter for the platform CEO
Across the add-ons we hold years of incident, patrol and scheduling history, and some of it sits in apps we are about to switch off. Guarding companies can license records like these to teams building AI, in return for one payment, with personal details removed and client site information excluded. Before we cancel the old systems, would you take a short fit call with SourceX to see if we qualify?
Next step
Pick the add-on whose reporting app is closest to being switched off and run it through the company fit checker. A passing result is your cue to register as a partner and introduce the platform, or have the CEO apply at sourcex.si/apply with your referral link. For a sector with similar integration timing but stricter technical-data limits, see aerospace MRO platforms.