Safety Monitoring
This page explains how to operate and monitor a Safety Tracking Event on the event day. For how to create this kind of event, see Create an event and set the basics.
What this page covers
- Where to open the monitoring screen
- What you can confirm on the screen
- Where to use management commands such as SOS handling and force finish
What this page does not cover in detail
- The overall concept of the Safety Tracking feature
- Recommended settings by activity type
- How to handle overdue return cases or field decisions
Those are organized in Safety Tracking and Operations Guide - Safety checks and return confirmation.
For how to judge overdue-return candidates or when to make phone calls, see Operations Guide - Safety checks and return confirmation.
If you want organizer setup, participant guidance, and activity-type-specific settings as well, see Safety Tracking.
Open the monitoring screen
Select the target event from the event management screen and tap Live Tracking to open the monitoring screen. On the web, open the Live Console from the event overview page (Live Console Overview & Screen Layout) to monitor safety and get coordinates in real time on a large PC screen (force end, resolving SOS, and remote punch can also be done from the Live Console).
Things to confirm before starting
- The target event is published
- Participants have already started sharing their location
- Participants can be identified by display name or Entry Number
- Someone on staff has the smartphone app available
If SOS handling or force finish may be needed, it is safer to have at least one staff member at HQ who can operate the smartphone app.
How to read the monitoring screen
Map view
Participant locations appear on the map as markers. Marker size changes according to participant status, and more urgent statuses are shown with larger markers.
Participant status
Participant communication status is judged automatically based on how much time has passed since the last received location, and the screen shows it as a color (the status names are not displayed).
| Color | Meaning | Condition |
|---|---|---|
| Green | Location is arriving | Within 10 minutes since the last received location |
| Orange | Location is late | 10 to 30 minutes since the last received location |
| Red | No location for a long time | More than 30 minutes since the last received location (also red when nothing has been received) |
| Gray | Not playing | Participants who have stopped sharing (including cancelled ones) |
Participant information
For each participant, you can confirm:
- Display name / Entry Number
- Status (SOS / Sharing / Ended. Ended also includes cancelled plays)
- Area violation status ("Out" / "Restricted" badge and duration when outside the play area or inside a restricted area. A red ring appears around the marker on the map)
- Elapsed time
- Battery level
- GPS accuracy (horizontal accuracy)
- Time since the last location update
The participant list can be sorted by Latest Start (default) or Number. With either sort order, participants sending an SOS, and then participants in violation of play/restricted areas, are moved to the top of the list and highlighted, and you can filter using the SOS or Outside area / Restricted filter chips. SOS and area violations also reach the phones of all owners, managers, and operators as push notifications.
What to look at first
- Participants with active SOS
- Participants outside the play area or inside a restricted area
- Participants shown in red or orange (delayed or disrupted location updates)
- Participants whose updates have stopped for a long time
- Participants who have not ended sharing
For detailed priority and first-response thinking, see Safety Tracking - Monitoring, SOS handling, and ending location sharing.
SOS handling
When a participant sends an SOS, all owners, managers, and operators receive a push notification on their phones, and an alert popup appears if the monitoring screen is open.
An SOS that was already active before you opened the monitoring screen does not pop up. Check the top of the list and the SOS filter.
Contents of an SOS alert
- The title 🆘 Emergency Rescue and the sentence "#entry number name is requesting emergency assistance" (only the name when there is no number)
- SOS message if the participant entered one
- OK - Selects that participant
- The time and location of the SOS are not in the alert. Check them in SOS Information (SOS Sent At / SOS Location) in the selected participant's details
Resolving an SOS
After confirming the situation and finishing the response, you can mark the SOS as resolved. An SOS can be cleared either from the participant side or from the organizer side.
This page explains where to confirm SOS and where to mark it resolved. For the timing of phone calls or decisions about on-site checking, see Operations Guide - Safety checks and return confirmation.
Sending messages from the organizer to participants
Messages to all participants (alerts or notices) can be sent from Broadcast in the event management menu. Operators can send the first direct message to a specific participant only from the Player List on iPhone, on the row of a participant who has checked in with the Check-in QR (turn on Enable direct contact with event organizer). Use Direct Messages in the event management menu to reply to direct messages from participants. Use them while switching back and forth with the monitoring screen. They are useful when you want to reach out before or after an SOS, or to alert all participants — for example sudden weather changes or announcing the end time.
Messages sent by an operator pop up as New message only when the participant has the location sharing screen open, and only within 60 seconds of sending. Low-urgency messages are handled the same way, so be mindful of the content and frequency you send. Messages sent from Broadcast are not sent as push notifications, so participants who do not have the screen open will not notice them until they open the message screen themselves. For urgent contact, also use the phone or other means.
While confirming a situation after an SOS, if the participant has checked in with the Check-in QR, you can send a direct message from the Player List on iPhone to ask about their status or share what to expect next (if the participant has already written, you can reply from Direct Messages). For the timing of phone calls or decisions about on-site checking, see Operations Guide - Safety checks and return confirmation.
Management commands
| Command | Description |
|---|---|
| Set alias name | Change the participant's display name on the monitoring screen |
| Update Entry Number | Correct a mistyped Entry Number |
| Edit note | Record a note about the participant |
| Resolve SOS | Mark the SOS as resolved (shown only for participants currently sending an SOS) |
| Force End Play | Force-end the participant's play (location sharing). Any active SOS is resolved at the same time. |
When to use Force finish
- The participant forgot to stop sharing
- The participant cannot stop from their device because of trouble
- Return confirmation is complete and you only need to clean up the sharing state
When you force-end, a message saying the organizer ended the play is shown on the participant's screen, and sharing stops.
Force finish is useful, but it does not replace actual return confirmation. Make the decision together with field confirmation and communication results.
Location transmission interval
When creating an event, you can set the Tracking Interval (1 / 3 / 5 minutes). The interval is only a guide and may vary depending on the usage environment, such as network conditions and device settings.
| Interval | Recommended use |
|---|---|
| 1 minute | Short races or cases where fine-grained monitoring is required |
| 3 minutes | General safety management, default |
| 5 minutes | Long events where you want to reduce battery use |
The status thresholds (10 and 30 minutes) are fixed regardless of the transmission interval setting. On courses with many no-network areas or when using a 5-minute interval, an orange indication appears more easily, so don't judge it as abnormal immediately — check it together with the last-received time.