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.
:::tip If you also want operational guidance For how to judge overdue-return candidates or when to make phone calls, see Operations Guide - Safety checks and return confirmation. :::
:::tip If you want the full picture of Safety Tracking 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 Manage screen and tap Live Tracking to open the monitoring screen. On the web, you can check participant locations from the event details page, but management commands such as SOS handling and force finish are available only in the smartphone app.
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.
| Status | Color | Condition |
|---|---|---|
| Normal | Green | Within 10 minutes since the last received location |
| Caution | Orange | 10 to 30 minutes since the last received location |
| Warning | Red | More than 30 minutes since the last received location |
| Inactive | Gray | Not currently active |
Participant information
For each participant, you can confirm:
- Display name / Entry Number
- Status (SOS / Sharing / Ended. Ended also includes cancelled plays)
- Elapsed time
- Battery level
- GPS accuracy
- Time since the last location update
The participant list can be sorted by most recent start (default) or number order. Participants who are sending an SOS are highlighted in the list, and you can use the SOS filter chip to show only participants currently in SOS. Also, when an SOS is received, an alert pops up.
What to look at first
- Participants with active SOS
- Participants in Warning or Caution state
- 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, an alert popup appears on the monitoring screen.
Contents of an SOS alert
- Participant name / Entry Number
- SOS message if the participant entered one
- Location when the SOS was sent
- Time of the SOS
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.
:::note It is easier to separate screen operations from field decisions 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 participants (alerts or notices) can be sent from the Broadcast message (to all participants) or Individual message (to a specific participant) options in the event management menu. 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 are treated as "Important notices" on the participant side and automatically pop up on the screen of participants who are sharing their location. Low-urgency messages are handled the same way, so be mindful of the content and frequency you send.
:::tip Use it together with SOS handling While confirming a situation after an SOS, you can send a message directly to the participant to ask about their status or share what to expect next. 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 | 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 |
| Clear SOS | Mark the SOS as resolved (shown only for participants currently sending an SOS) |
| Force-end the 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 location transmission 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 |
:::tip Transmission interval and status judgment 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, a "Caution" indication appears more easily, so don't judge it as abnormal immediately — check it together with the last-received time. :::