Security Services

Non-Emergent Response Services

Aquila designs and staffs accountable non-emergent field-response programs for government, transportation, institutional, and public-serving organizations under defined call, authority, dispatch, escalation, and reporting protocols.

A structured response for calls that do not require 911

Public agencies, transportation systems, institutions, and community-serving organizations receive many requests that require an accountable field presence but do not begin as a police, fire, or medical emergency. Sending the wrong resource can consume limited emergency capacity; sending an unprepared resource can create avoidable risk. Aquila Protective Services helps organizations design and staff defined non-emergent response programs between those two outcomes.

These programs are not a substitute for law enforcement, emergency medical services, crisis clinicians, or other authorities. Aquila personnel operate only within the role, training, permissions, and escalation limits established for the contract. Calls involving violence, weapons, serious medical concerns, crimes in progress, or other emergency indicators are transferred or escalated according to the approved procedure.

Programs are built around an authorized call type

Non-emergent response is not a single universal service. The contracting organization determines which requests may be assigned, what the responder is expected to accomplish, what authority is available, and which conditions make the call ineligible. Aquila converts those decisions into a dispatchable service model with clear acceptance and escalation criteria.

Low-risk public-assistance or customer-service requests requiring an in-person response.
Facility, property, access, or transportation concerns that need observation, documentation, or coordination.
Nuisance, ordinance-support, or quality-of-life assignments specifically authorized by the contracting agency.
Follow-up visits, scheduled checks, notifications, escorts, or other defined administrative field tasks.
Calls requiring connection to an agency representative, service provider, outreach resource, supervisor, or public-safety responder.
Temporary response programs supporting a pilot initiative, service interruption, seasonal demand, or gap in existing field resources.

Call-screening rules protect the public and the responder

Before launch, each proposed call type is reviewed for foreseeable hazards, required information, exclusion criteria, and the qualifications needed to respond. Dispatch questions are designed to identify facts that may change the response, including threats, weapons, injury, active violence, intoxication, uncontrolled behavior, criminal activity, environmental hazards, vulnerable persons, and whether another agency is already involved.

A call that changes while pending or after arrival can be reclassified. Responders are not expected to continue beyond their authorization simply because the assignment began as non-emergent. Procedures identify when to disengage, request additional Aquila resources, notify the client, or contact police, fire, EMS, or another designated provider.

What happens from intake to closure

An authorized request enters through the channel established by the client, such as an agency system, telephone intake, electronic referral, or direct dispatch connection. Required information is collected, the location and call type are confirmed, and the assignment is reviewed against eligibility criteria before deployment.

The dispatcher records the request, available facts, location, contact information, and client-defined priority.
An appropriately assigned responder receives the call details, safety information, and expected task.
Dispatch monitors acknowledgment, travel, arrival, status changes, requests for assistance, and completion.
The responder observes, communicates, takes authorized action, and avoids duties reserved for another profession or agency.
Exceptions and urgent developments are escalated through the approved notification path.
The call closes with a disposition and the documentation required by the client.

Personnel selected for public-facing judgment

The responder’s conduct often determines whether a routine concern remains routine. Personnel may be selected and trained for communication, de-escalation, situational awareness, respectful public interaction, documentation, radio procedure, defensive decision-making, and the specific operating environment involved. Assignment-specific training addresses the client’s policies and the boundaries of the role.

Aquila can structure single-person or multi-person responses according to the call type and risk assessment. Supervisors and dispatchers remain available to assist with uncertain conditions, coordinate additional resources, and review deviations from procedure.

Defined authority prevents role confusion

Every program should state what responders may do, what they may not do, and who retains decision authority. Instructions may address requests for identification, entry into facilities, transport or escort limitations, handling found property, interaction with vulnerable individuals, documentation of apparent violations, preservation of evidence, use-of-force restrictions, and contact with other agencies.

Aquila works with the contracting organization to establish those boundaries; the client remains responsible for granting only authority it lawfully possesses. Legal, clinical, code-enforcement, and law-enforcement determinations remain with the appropriately authorized professionals.

Dispatch is an active part of the response

Aquila’s redundant 24/7 dispatch centers in Denver and Nashville can receive assignments, apply client-specific call procedures, monitor responder status, document communications, coordinate supervisors, and initiate escalation. Redundancy supports continuity if severe weather, communications trouble, increased call volume, or another disruption affects one center.

Priority definitions and notification times are established for the individual program. Dispatchers need clear direction about which facts require immediate escalation, how long a call may remain unassigned, when a supervisor must be notified, and which contact assumes responsibility after an event moves outside Aquila’s role.

Documentation designed for program accountability

A closed call should show more than an arrival time. Depending on client requirements, the record may include intake information, assignment and acknowledgment times, travel and arrival status, responder observations, contacts made, actions taken, escalation, disposition, attached reports, and supervisory review.

ResponderShield Nexus can support electronic call records, status tracking, GPS-supported operational visibility where configured, reports, exception review, client access, and performance metrics. Documentation standards distinguish firsthand observations from statements provided by callers, clients, or third parties.

Performance measured beyond call volume

A meaningful program review considers whether eligible calls are accepted consistently, assigned within the expected time, handled within scope, documented completely, and escalated appropriately. Measures can also examine cancellations, unsuccessful contacts, repeated locations, safety exceptions, client complaints, use of additional resources, and the reasons calls could not be completed.

Trends should lead to operational decisions. Repeated exclusions may indicate that intake questions need improvement; repeated escalations may suggest a call type requires different staffing; long completion times may reflect travel, access, or unclear disposition requirements rather than responder performance alone.

Pilot programs before broader deployment

When the service model is new, a limited pilot allows the client and Aquila to test assumptions with controlled call types, geography, hours, and volume. The launch plan defines training, communications, supervision, data collection, review meetings, and the conditions that would pause or expand the program.

Early calls are reviewed closely to determine whether screening rules are identifying risk, responders understand their authority, documentation is useful, and other agencies know when and how to interact with the service. Procedures can then be refined before adding call types, locations, operating hours, or personnel.

Regional programs with local operating rules

A multi-location program can use common intake, reporting, supervision, and quality standards while maintaining jurisdiction-specific call types, escalation contacts, licensing requirements, public-safety relationships, and local resources. This balance supports consistent program management without assuming that authority or service availability is identical everywhere.

Aquila can develop and support non-emergent response programs across Colorado, Wyoming, South Dakota, Kansas, Nebraska, Oklahoma, and Tennessee, coordinated through its regional operations and dual dispatch-center infrastructure.

Defining a potential response program

The planning process begins with the problem the organization is trying to solve, the calls currently consuming resources, available call data, proposed authority, operating area, requested hours, expected volume, desired response time, safety exclusions, partner agencies, documentation needs, and measures of success.

Aquila can then help develop a service concept, staffing assumptions, dispatch workflow, eligibility matrix, escalation plan, training requirements, technology configuration, pilot structure, pricing model, and implementation schedule. The result should make clear which calls belong in the program—and which do not.