Device settings · Free designer

Tracker auto check-in geofences and overdue alarms for journey plans

Drivers forget to call in. A tracker does not. Turn the call-in points and rest stops of your approved journey plan into geofences, reporting rules and overdue alarms, and hand the settings sheet to whoever configures the devices.

Runs in your browserYour own device valuesSettings, not a journey plan
Points on the route (up to 20)
PointRoad km from startTypePlanned stop (min)Own radius (m)Remove

Copy the points in order from the approved journey plan. Own radius is optional: leave it empty and the designer sizes the geofence.

hh:mm

Planned departure from the first point, 24-hour clock.

km/h

Average over the whole trip, slow sections included. It sets the expected times.

Example route. Replace it with the points of your own journey plan.

Settings sheetPer point

Hand the sheet to your configuration team

A report with every geofence, its event, the expected time and the alarm times.

Settings sheet report

Take the settings sheet to the configuration desk

  • One geofence per point, with radius and event
  • Expected time, overdue alarm and escalation
  • Positions expected inside each call-in geofence
  • Rest-stop and unplanned stop alarms
  • Every value you entered
From plan to device

Each point becomes a geofence

The device reports when it enters or leaves each circle. The control room only hears about the points that did not happen on time.

Startkm 0Call-inkm 120Restkm 250Call-inkm 380Endkm 470position every 30 s
Fig. 1 Stop points get a yard-sized circle. A pass-through call-in needs a circle wide enough to catch at least one position at speed.

Why let the device check in?

A manual call-in depends on signal, a phone and a driver who remembers. A geofence event arrives by itself, with the time and the position. People then deal only with the exceptions: a point not reached, a stop that is too long, a stop where none was planned.

How big must a call-in geofence be?

A vehicle that drives through a circle without stopping must leave at least one position inside it. Through the centre it covers 2 x r of road, so the radius must cover half the distance driven between two positions, plus the position error.

r = speed (m/s) x interval (s) / 2 + accuracy = 22.2 x 30 / 2 + 10 = 343 m -> 350 mRounded up to 50 m. Place the centre on the road, not beside it.

When is a vehicle expected at each point?

Expected time adds the driving time of each leg to the departure time, plus the planned stops before the point. The overdue alarm waits a grace period: a fixed number of minutes, or a share of the leg, whichever is larger.

expected = departure + Σ(leg km / speed x 60) + Σ planned stops overdue = expected + max(grace, leg minutes x share) escalate = overdue + further minutes
Example settings sheet: depart 05:30 at 70 km/h
PointRadiusEventExpectedOverdue alarm
Base gate200 mExit05:30No alarm
Call-in 1, km 120350 mEnter07:1307:43
Rest area, 30 min200 mEnter and exit09:0409:34
Call-in 2, km 380350 mEnter11:2611:56
Site gate, km 470200 mEnter12:4313:13

Which alarms does the sheet set?

  • Overdue: the vehicle has not entered the next geofence by the overdue time.
  • Escalation: still no event after the further minutes, so the next person is called.
  • Long rest: the vehicle stays in a rest geofence longer than the stop plus the tolerance.
  • Unplanned stop: the vehicle is stopped outside every geofence for too long.

Assumptions and limits

  • This designer does not write or approve a journey plan. It starts from points your team already approved.
  • Road km and an average speed give expected times, not a forecast of traffic or weather.
  • Interval, accuracy and radii are typical values, not Tracom specifications. The 4000 geofence slots are the published Tracom ST100 value.
  • Whether the overdue logic runs on the device or on the platform depends on your device model and platform. Ask before you rely on it.
  • The calculations run in your browser. Your inputs reach our server only if you ask for the emailed report, and are then kept for up to 45 days.

Sources

Sources and date checked: 3 November 2026. The radius rule is plain geometry. The 4000 geofences are the published Tracom ST100 value. Verify alarm times against your own HSE procedure.

Related Tracom solution

Let the device check in, so the driver can drive

Tracom tracking devices support advanced geofencing and emergency panic alerts. Ask which geofence events, slots and alarm options your device model offers before you load the sheet.

  • Advanced geofencing. Enter and exit events for each point on the route.
  • Emergency panic alerts. The driver can raise an alarm between check-ins.
  • No internet? No problem. The device keeps deciding on the vehicle without a connection.
  • Real-time SMS adjustments. Change a setting for a new route without a workshop visit.
Questions

Questions about automatic check-ins

Setting up check-ins for a remote route? Contact Tracom.

Is this a journey management plan?

No. The journey plan, with its risks and approvals, comes first. This designer turns the approved call-in points and rest stops into device settings.

Why does a call-in point need a bigger radius than a rest stop?

Because the vehicle may not stop there. At 80 km/h and one position every 30 seconds, the vehicle moves 667 m between positions, so a small circle can be crossed with no position inside it.

What happens if no position falls inside a geofence?

The check-in is missed and the overdue alarm fires even though the driver is on time. The designer flags every point where fewer than one position is expected.

How many geofences can my device hold?

Tracom publishes up to 4000 geofences for the Tracom ST100, and the page starts from that value. For another device, check its datasheet.

Does the overdue alarm run on the device or on the platform?

Not always the same. Geofence events come from the device, while timers and escalation often run on the platform. Confirm where each rule runs before you go live.

What is Tracom's role here?

Tracom makes tracking hardware. The designer helps you translate a journey plan into device settings. It does not approve journeys and does not replace your control room.

Related tools and templates

Configure the rest of the alarms

Get the report

Enter your details and we will email you the file.

Use your real name so the file arrives addressed to you. Don't worry, we won't flood you with emails or calls.

Scroll to Top