Full-site design previewPreview forms do not send messages
1Degree Surveillance

Dispatch coordination

Give every escalation a destination and a next owner.

1Degree coordinates authorized escalations for security, alarm and guarding partners serving US and Canadian client sites. Operators communicate observed event information to the contact identified in the account plan and document the handoff. Physical response and agency decisions remain with the receiving party.

Illustration of an Asian monitoring operator using camera footage and a map during a handoff

Choose how we watch
your cameras.

Get a quote
Illustration of a fictional monitoring specialist watching several live camera feeds
Day24/7Night

Watch all day

A real person watches your live cameras, 24/7. If we see a problem, we follow your response plan.

Shared team$25per camera / month

Your cameras and other sites.

Dedicated team$35per camera / month

Only your agreed cameras.

Continuous monitoring
Illustration of an alarm at a warehouse entrance after dark
AlarmVideo check

Check alarms

When your system sends an alarm, we check the video and follow your response plan.

$10per camera / month

60 minutes of staff time per camera each month, shared across your site. Extra time: $0.30/minute.

Alarm verification
Illustration of camera checkpoints at a site gate, yard and loading bays
Scheduled camera round1 Gate 2 Yard 3 Loading bays

Check at set times

We check your cameras at the times you choose and send you a report of what we find.

$0.75per scheduled check

Up to 16 camera views and 5 minutes per check. Minimum: $22.50 per site each month.

Virtual guard tours

Choose the route for the type of event

A technical fault, expected activity and an event requiring response should not enter an indistinguishable queue. The account plan needs a route for each, with the information the receiving person requires.

Your monitoring center, patrol team, site contact or appropriate public response agency may have a role. An administrative contact ladder is not automatically the right route for an urgent incident. Build event-specific instructions with the responsible parties before the account goes live.

The contact handoff

An attempt and a handoff are different states.

  1. Locate

    Identify the exact area

  2. Contact

    Use the agreed call list

  3. Hand over

    Record who takes over

The account sets the contact sequence. External attendance is a separate event.

View the working details
  1. Attempted

    Contact role, method and attempt are recorded.

  2. Reached

    Communication is established with the contact.

  3. Acknowledged

    The recipient’s acceptance or update is recorded.

  4. Handed over

    The next owner and any open action are identified.

Useful handoff information

  • Site and exact zone
  • Observed activity
  • Action already taken
  • Current limitation

Make the contact ladder usable

A list of names is not enough. Use this planning table to identify the action, destination and fallback for each account. It is a design aid, not a universal emergency procedure.

Escalation route planning
DecisionInformation the account needs
When to escalateObservable event criteria, relevant location and any required verification step.
Who receives itThe authorized destination, contact method, availability and role.
What to communicateSite address, entrance or area, camera, event time, observed activity and actions already taken.
If contact failsThe authorized fallback and how the attempted contact is recorded.
When responsibility transfersHow acceptance is established and which team continues observation or follow-up.
How the event closesRequired outcome information, unresolved work and the recipient of the final record.

Keep attempts, acceptance and attendance separate

A call placed is a contact attempt. An acknowledged handoff shows that another party has received information. Confirmed attendance is a later event that should only be recorded when it is known. These distinctions help your team explain the response accurately to its client.

For an illustrative industrial-yard event, the operator might identify activity near a named gate, document an authorized audio action and pass the current observations to the nominated patrol contact. The report should preserve any uncertainty about location or continued activity, rather than filling the gap with an assumed outcome.

Test the information before it is needed

Check site addresses, entrance descriptions, contact availability and fallback instructions with the people responsible for them. A tabletop review can reveal a missing night contact or an instruction that sends two teams toward different actions.

Any test involving an external responder must be arranged through that party's approved process. Do not use a real emergency request to test a routine workflow. After a test, update the account record and identify which instruction is now active.

Plan the follow-up your client expects

Decide who tells the client what happened, who handles a technical repair and who follows up with a responding team. A monitoring event may be closed while a maintenance or customer-service task remains open.

Bring an example event and your current contact instructions to the review. The blank incident-report resource helps you identify the information your team needs from the handoff and what it must obtain afterward.

Illustration of an operator checking the camera evidence for an event

Common questions

Before you bring an account on board.

Can our own patrol company receive the escalation?

Your nominated patrol team can be included in the account plan. Its contact availability, required information and handoff procedure need to be usable during the coverage window.

Does video verification guarantee attendance or priority?

No. A receiving agency or response service controls its decisions and availability. The monitoring plan can define communication tasks; it cannot establish an outside party's guaranteed response.

Can dispatch use our existing software?

Share the software and intended workflow for technical review. A system category or product name alone does not establish supported access, event transfer or reporting functions.

What happens when a contact changes?

Update the account through the established change route with an effective time, replacement details and authorization. Obtain confirmation that the revised instruction is active, particularly for temporary or out-of-hours changes.

What would you like
to hand over?

Share your company, client-site mix and coverage needs. Let’s work through the next step.

Illustration of a fictional monitoring specialist reviewing camera views
Your camera setupYour coverage hoursYour response plan