• Dispatcher
  • Responder
  • Videos
  • FAQ
  • Status
  • ES
  • Ukrainian
  • Dispatcher
  • Responder
  • Videos
  • FAQ
  • Status
  • ES
  • Ukrainian

User Resources

home/Documentation/User Resources
  • Dispatcher Resources
    • Getting Started
      • Dashboard Navigation
      • Profile Menu
      • Responders Panel
      • Active Incidents Panel
      • Settings (ᵐ)
    • Key Functions
      • Add and Edit Responders (ᵐ)
      • Select Responder Type (ᵐ)
      • Add and Edit Web Users (ᵐ)
      • Map Layers
      • Transport Options
        • Add Transport Destinations
        • Arrival Notifications
      • Map Editing
      • Chats Feature
      • Push-To-Talk
      • Create Incident Panel
        • Creating Incidents
        • Pending Incidents Feauture
        • Dispatch Mode (previously called Incident Priority)
        • Alert Types (previously called Dispatch Types)
        • Responder Tags
        • Assigning Responders
        • Custom Incident Labels (ᵐ)
      • Dispatch Automation
        • Broadcast Alerts
        • Preferred ETA
        • Confirmation Windows
      • Monitoring Incidents
      • Dispatch Controller
      • Add Incident Disposition Codes
      • Add Dispatcher Incident Comments
    • SMS Functionality
      • SMS Chat Messaging
      • Add SMS Dispatcher (ᵐ)
      • Create Incidents by SMS
    • Reporting
      • Reports Automatically Generated by Beacon
        • Incident Reports
        • Summary Reports (ᵐ)
      • Documentation Manually Added by Responders
        • View Incident Notes (ᵐ)
        • Case Reports
    • More Dispatcher Resources
      • Practice Exercises
      • External Factors
  • Responder Resources
    • Mobile App interface
      • Beacon Mobile App Tour
      • Getting Started
        • Initial Sign In
        • Home Screen
        • SOS Feature
        • Map Features
        • Sidebar
        • Manage Responders
      • Response Workflows
        • Responder Types and Workflows
        • Incident Card Navigation
        • Incident Alert
        • En Route
        • Arrival On Scene
        • Additional Resources
        • Destination Transport
        • Arrival at Destination
        • Complete Incident
        • Response Times Summary
      • Documentation
        • Submit Incident Notes (Mobile App)
        • Case Reports
      • Other Features
        • Mobile App Chat
        • Push-To-Talk
        • Create New Incidents
        • Incident Dispatch Mode
        • Update the Incident After Creation
        • Interactive Notifications
        • Alerts Vibration for Beacon
        • Duty Scheduler
        • Special Permissions for Mobile App Users
        • Mobile App Settings
    • SMS Interface
      • Full Manual for SMS Users
      • SMS Code Index
      • Submit Incident Notes (SMS)
      • Requesting Additional Resources (SMS)
      • SMS Chat
    • Practice Exercises
  • Case Reports
    • Introduction to the Case Reports Feature
    • Setting Up Case Reports
    • Mobile App Case Reports Feature
    • Web App Case Reports Feature
  • GPS Settings & Tracking Services
  • Downloads
    • Web Dispatcher Cheat Sheet
    • Mobile App Responder: Patient Transport
    • Mobile App Responder: Response-only
    • Dispatcher Practice Exercises
    • SMS Responder: Response-only
    • Responder Practice Exercise
    • Alerts and Sound Settings
    • Dispatcher Guide Downloadable
    • Responder Guide Downloadable
    • Beacon Reporting Features Guide
    • Manager Assessment
  • Videos
  • Status

Preferred ETA

Editing these Settings is only available for Managers

GPS is a great way to figure out how close Responders are to an emergency. Unfortunately, not everyone has GPS-capable phones, so Beacon uses the Preferred ETA setting to figure out who’s closest. (There are other reasons why Beacon doesn’t use GPS to find the closest Responder, too. Read more here.)

When Dispatchers send out Broadcast Alerts, Responders are asked to self-report their estimated time of arrival (ETA) to the Incident Location. Beacon compares each Responder’s self-reported ETA to the Preferred ETA setting to determine what happens next.


Here are three examples to show you how it works. (Please note: The Preferred ETA setting works the same way whether you’re responding through the Beacon Mobile App or via SMS.)


Scenario 1:

Responder’s ETA is less than or equal to the Preferred ETA

Result:

Responder is Assigned Immediately ✅

If the Responder’s ETA is less than/equal to the Preferred ETA, and Beacon is still looking for more responders, the Responder is immediately assigned to the incident and asked to Confirm En Route.


Scenario 2:

Responder’s ETA is greater than the Preferred ETA

Result:

Responder is told to “Please Standby” ✋

If the Responder reports an ETA greater than the Preferred ETA, the Responder is told to Please Standby (for 1 minute*). Beacon is now waiting to see if there are other Responders who are closer. If Beacon can’t find another Responder with a shorter ETA, Beacon will then send the Confirm En Route message, as shown here.

*Read this page on “Confirmation Windows” to learn about how Beacon decides how long you have to wait.


Scenario 3:

Responder’s ETA is greater than the Preferred ETA

Result:

Responder is Rejected 🚫

Just as in the example above, in this scenario the Responder reports an ETA greater than the Preferred ETA and is then told to Please Standby (for 3 minutes*). After 3 minutes, Beacon then tells the Responder, “You are not needed for this incident.”

Why? Because Beacon found another Responder who reported a shorter ETA than this Responder.

*Read this page on “Confirmation Windows” to learn about how Beacon decides how long you have to wait.

The Preferred ETA setting is how Beacon determines who the closest Responders are. Is it perfect? No. In fact, you’ve probably already figured out that Responders can game Beacon by always replying with an ETA of 1 minute.

This is true.

But why would they want to do that when lying about their ETA could be the difference between them saving a life and delaying care to a critical patient? As far as we’re concerned, that’s a personnel problem — not a technology problem. Tell your Responders to be honest about how long they need to arrive on scene.

One day everyone will have GPS-enabled phones and Beacon will be able to pick the closest responders that way (in theory, at least). Until then, the Preferred ETA setting will do just as well.

Tags:Dispatcher Guide
Related Articles
  • Initial Sign In
  • Responder Types and Workflows
  • Pending Incidents Feauture
  • Duty Scheduler
  • Manager Assessment
Previous
Broadcast Alerts
Next
Confirmation Windows

Dispatcher Resources

Responder Resources

Downloads

Status

Contact Us:

 [email protected]

 ENG +1.218.4 BEACON

(+1.218.423.2266)

 ESP +1.787.336.0123

*These are not emergency phone numbers.
In case of emergencies, please call your local emergency service.
  • Privacy Policy
  • Terms of Use
  • ©2025 TREK MEDICS INTL ALL RIGHTS RESERVED