Skip to content
Pilot & Evaluation Guide guide illustrative entrance and technology scene

Field guide · Rivell

How to pilot and evaluate a weapons detection system

A demonstration shows what a system can do in ideal conditions. A pilot shows what it will do at your entrance, with your visitors, your bags and your staff. This guide lays out a practical evaluation plan you can use with any vendor, including us.

Rivell Concealed Weapons Detection team

6 min read

Last reviewed: November 2026

Illustrative image

Our disclosure

Rivell is an implementation partner for Motorola Solutions Concealed Weapons Detection, powered by Evolv. Use this plan with any vendor.

Key takeaways

Agree the objective and acceptance criteria in writing before the pilot starts. Measure your current process first. Record alarms, their causes, effective throughput and staffing at real peaks. Decide with data, not impressions.

Step 1: Define what you are screening for

DHS advises weighing the threat-level deterrence objective against the size of items a system can detect, its discrimination ability (what it will ignore) and its maximum recommended throughput. [S4] Write down which threat classes the program is meant to address and which it is not. That single page keeps the pilot, the vendor conversation and your community messaging consistent.

Agree the scope with security, facilities, operations and leadership before a vendor arrives. Identify who owns the decision at the end of the pilot and what information they will need.

  • Threat classes in scope, and out of scope.
  • Entrances in scope, and how unscreened doors will be controlled.
  • Who resolves alerts, and what happens if someone declines screening.
  • Who makes the final go/no-go decision.

Step 2: Measure your current entrance first

You cannot judge an improvement without a baseline. Before the pilot, record how people arrive today: arrival peaks by time of day, what they carry, how long the current process takes, and where queues form. If you have no screening today, record the arrival curve and the belongings mix anyway.

DHS notes that connected platforms can report visitor arrival curves and alarm rates by entrance, time and date, which helps staffing decisions during and after a pilot. [S4] Capture your own baseline as well so the comparison does not depend only on vendor data.

Step 3: Choose the pilot entrance and design the lane

Pick an entrance that represents your real problem: a typical peak, typical belongings and typical constraints such as power, network, flooring, weather and nearby metal structures or moving doors. A quiet side door makes any system look good and teaches you little.

Design the full lane, not just the portal. DHS notes a screening lane may need three or more staff: one to guide people, one to operate and one for follow-on screening. [S11] Mark a secondary screening area outside the main flow, plan signage, and provide an alternate screening option for people with implanted medical devices or accessibility needs. [S4]

Step 4: Agree acceptance criteria in writing

Acceptance criteria are the heart of a fair pilot. Detection evidence should identify the threat class, the throughput, the sensitivity setting and the confidence interval behind it. [S4] Ask the vendor to state which standard or independent evaluation supports each claim; for active walk-through metal detection, DHS points to ASTM F3566-22. [S4][S5]

Any on-site detection testing should follow a written protocol agreed with the vendor and, where appropriate, your security leadership or local law enforcement. Define in advance what counts as a pass, how nuisance alarms will be categorized and which sensitivity setting will be used for each phase.

  • Sensitivity setting(s) to be evaluated, and why.
  • Detection test protocol and who supervises it.
  • Target range for nuisance alarms at the chosen setting, and how they will be categorized.
  • Effective throughput target at your measured peak, with the staffing assumption.
  • Accessibility, privacy and data-handling requirements that must be met.

Step 5: Run the pilot and record the right data

Run long enough to see your real peaks and a representative mix of visitors and events. Keep a simple log so results are comparable from day to day.

Remember the trade-off DHS describes: raising sensitivity may improve detection of smaller items but increases alarms on non-threats, which lowers effective throughput. [S11] If you test more than one setting, record results separately for each.

  • Visitors screened, by hour and entrance.
  • Alerts, and what caused each one (category of item, threat, unresolved).
  • Time to resolve an alert at secondary screening.
  • Effective throughput at peak versus the manufacturer’s stated maximum.
  • Staff on post and any gaps.
  • Visitor questions, complaints and refusals.
  • Technical issues: network, power, interference, updates.

Step 6: Review privacy, cybersecurity and procurement

During the pilot, confirm what data the system captures, where it is stored and for how long. For the platform Rivell installs, DHS reports that alert images are stored in the cloud only with customer administrator consent, with a seven-day default retention. [S4] Document who can view alert images and how long your organization keeps them.

Bring IT in early. DHS recommends following the FBI CJIS Security Policy and CISA cloud security best practices for connected screening systems. [S4] If grant funds are involved, confirm program rules and Section 889 restrictions before ordering. [S4]

Step 7: Decide, and plan the full rollout

Compare the pilot data with the acceptance criteria you wrote in Step 4. A good outcome is not only a pass or fail; it is a clear picture of how many lanes you need for your peak, how many staff, what layout changes help, and what the total cost of ownership looks like.

Sometimes the answer is that screening is not the right fix for a particular entrance, and policy, access control or cameras will do more. Write that down too. The full rollout then follows a known sequence: design, install and integrate, acceptance testing and procedures, training, go-live and tuning, and ongoing support.

Frequently asked questions

How long should a weapons detection pilot run?

Long enough to capture your real arrival peaks and a representative mix of visitors and events. The right length depends on your schedule; agree it with the vendor in writing before you start.

What should acceptance criteria include?

The threat classes and sensitivity setting being evaluated, the detection test protocol, how nuisance alarms will be categorized, the effective throughput target at your peak with staffing assumptions, and privacy and accessibility requirements. [S4]

Can we pilot at a temporary entrance or event?

Often, yes. DHS notes some walk-through systems are transportable for temporary deployments while others are set up at fixed entrances. [S11] Choose the pilot location that best matches how you will use the system long term.

Does Rivell help run pilots?

Yes. We start with a site survey, then plan the lane, acceptance criteria, training and data collection with your team.

Rivell front office in Sewell, New Jersey

Request a site survey

Start with your entrances, your people and a practical plan.

Request a site survey