# Security Pilot Program Guide: Run a 30-Day Site Trial

By VDS Editorial · Published November 2026

Source: https://visiondetectionsystems.com/blog/security-pilot-program-guide

> A 30-day pilot at one site tells you whether mobile surveillance works for your operation before you commit. This guide covers goals, metrics and what to track.

To run a 30-day pilot of mobile surveillance, pick one site with a known recurring problem, write your goals and success criteria before the unit arrives, track events and reliability throughout, and review results with the vendor at the end. A pilot is a controlled test, so the value comes from the measures you set in advance and the records you keep.

## Pick the right site

Choose a site where the problem is real and recurring, such as after-hours theft, trespassing, vandalism or vehicle break-ins. The site should produce enough activity during 30 days to test the system. A site that is almost never disturbed will pass any pilot and teach you nothing.

Choose a site that resembles the rest of your portfolio, so the results apply elsewhere. Confirm the practical basics: a place to position the unit with a clear view, sun exposure for solar power, and cellular coverage. The [deployment guide](/blog/how-to-deploy-a-surveillance-trailer) covers placement and setup.

## Write goals and success criteria first

Write down what you want to learn before the pilot begins. Keep the list short and specific. Good pilot goals are things you can observe, such as whether the unit covers the entry points you care about, whether alerts are accurate enough to be useful, and whether response is fast and well documented.

State what success looks like in plain terms. For example, you might decide in advance that coverage must include every entrance, that the operations team must find alerts credible, and that every escalation must come with a clip and a written note. Avoid numeric targets you cannot justify. Compare against your own baseline instead.

Capture the baseline now: how many incidents occurred in the months before, what they cost you in time, and what you did about them. Without a baseline you cannot say whether anything improved.

## Set up roles and communication

Assign a pilot owner on your side and ask the vendor to name one on theirs. Agree on who gets alerts, who can act on them, and how you will communicate during the trial. Schedule a short weekly check-in so problems surface early, not on day 30.

Tell the people on site what is happening. Staff and neighbors should know the unit is there and who to contact with questions. Agree on how to handle a real event during the pilot, including who calls police and who talks to the monitoring team.

## What to track during the pilot

Keep a simple log. A spreadsheet works. Record every alert, whether it was verified, what was done, and how long each step took. Add notes on anything unexpected.

| Measure | What to record | Why it matters |
|---|---|---|
| Coverage | Areas seen and areas missed | Confirms placement fits the site |
| Alerts | Count, type and whether each was useful | Shows alert quality and noise |
| Verification | Time from detection to human review | Shows how quickly events are assessed |
| Response | Actions taken, such as talk-down or police dispatch | Shows what happens when it matters |
| Records | Clip and written note for each event | Shows documentation quality |
| Reliability | Outages, causes and how you were told | Shows whether the unit is dependable |
| Support | Questions raised and how fast they were answered | Shows service after setup |
| Incidents | Events that occurred, compared with the baseline | Shows the effect on the problem |

If alert noise is high, work with the vendor to adjust the rules rather than accept it. The guide on [reducing false alarms in video analytics](/blog/how-to-reduce-false-alarms-in-video-analytics) explains what can be tuned.

## Watch reliability, not only incidents

A quiet month does not prove the system works, and a busy month does not prove it fails. Track whether the unit stayed online and whether you were told about problems before you noticed them. Solar and cellular systems depend on sun and signal, so note the weather and any connectivity dips.

The article on [surveillance trailer uptime](/blog/surveillance-trailer-uptime) lists what affects availability and what to ask. A vendor that reports its own outages promptly is easier to trust than one you have to chase.

## Hold a mid-point and a final review

At about the halfway mark, review the log with the vendor. Look for patterns such as repeated alerts from the same cause, blind spots or gaps in response. Adjust camera aim, alert rules or notification steps, and note what was changed and when. Changes are expected in a pilot, but record them so you can judge results fairly.

At the end, review the full log against the criteria you wrote at the start. Score each goal as met, partly met or not met, with notes. Collect feedback from staff who dealt with alerts, and from anyone who lives or works near the site.

## Decide what happens next

Make the decision based on the evidence. Options include expanding to more sites, extending the pilot to test another condition, adjusting the setup, or ending the trial. If you are comparing several vendors, use a common scorecard. The article on vendor reference questions and scorecards provides one.

Ask the vendor how a pilot converts into a longer arrangement, and what changes if you continue. Review options such as short rentals and longer terms in the [rental guide](/blog/mobile-surveillance-trailer-rental), and confirm exit terms in writing.

## Common pilot mistakes

Pilots go wrong in predictable ways. The first is starting without written criteria, which turns the final review into an argument about impressions. The second is picking a site that is too quiet or too unusual to be useful. A third is changing too many settings at once, so nobody knows which change helped.

Other mistakes involve people. Staff who were not told about the pilot may disable power, move the unit or ignore alerts. Nobody owns the weekly check-in, so problems wait until the end. Results are judged only on incident counts, which ignores support, documentation and reliability.

Avoid these by writing the plan on one page: site, dates, goals, measures, owners and the date of the final review. Share it with everyone involved, including the vendor. Keep a change log, review it each week and hold the vendor to the same standard you set for yourself.

## How VDS fits

VDS builds solar-powered mobile surveillance units. Each has a 5MP PTZ with 25x optical zoom and three 8MP wide-angle cameras on a 22 ft telescopic mast (30 ft available), powered by a 900W bifacial solar array and an 11.8 kWh LiFePO4 battery bank with reserve for 3-5 consecutive cloudy days. Dual-SIM 4G/5G cellular means no site power, internet or trenching is needed.

Most deployments go from signed quote to live monitoring in about a week, and on-site setup takes one person under 20 minutes. A 24/7 US-based security operations center verifies events, responds with live talk-down, and dispatches police with video. Rental, month-to-month and term subscriptions are available. See the [mobile surveillance unit](/products/mobile-surveillance-unit) or [talk to our team](/get-started).

## Frequently asked questions

### Why run a 30-day pilot?

A pilot tests coverage, alert quality, response and reliability on your own site, with real conditions and real staff. It reduces the risk of a larger commitment and gives you data to compare vendors.

### Which site should I use for a pilot?

Choose a site with a known, recurring problem and enough activity to produce events during the trial. A site that is too quiet will not tell you much, and one that is too unusual may not represent the rest.

### What should I measure during a pilot?

Track coverage of the areas that matter, the number and quality of alerts, how fast events are verified and escalated, uptime, and how many incidents occurred compared to before the trial.

### How do I decide if the pilot succeeded?

Compare results to the success criteria you wrote before the trial began. Include operational fit and support quality, not only incident counts.

### Can I get a mobile surveillance unit for a short trial?

Rental, month-to-month and term subscriptions are available from VDS, so a short trial is possible. Contact the team to discuss your site and timeline.