In Version 9.25, geofences become full checkpoints in COREDINATE. When a team member enters a zone, time tracking starts. When they leave, it stops. Each crossing appears in the logbook, separated into entry and exit.
NFC tags and GPS points cover most security documentation. What they don't capture are areas. A warehouse is not a point. A facility is not a radius. A loading bay has an edge, beyond which a delivery begins. With the 9.25 update, the geofence follows the geometry of the site.
In COREDINATE, you draw geofences as polygons, not circles. Point by point in the map editor: an L-shaped warehouse, a facility with three annexes, a marked loading bay. Left click sets a corner, Double-click or Enter completes the polygon, Right-click removes the last point, Esc cancels.
For each geofence, you configure three independent triggers. For each one, you set separately whether it responds on entry, on exit, or manually.
The employee's shift starts as soon as they enter the zone. When they leave, it stops. Forgotten clock-ins no longer occur for geofences where the shift begins anyway: gatehouse, admin building, staff car park.
Records the duration of stay in exactly this zone, parallel to the ongoing shift. How long was an employee in the hazardous materials storage today? The answer is in the details drawer, with timestamp for entry and exit.
On entry, a freely configurable warning appears in the app, for example "Please wear protective equipment". The display follows the language of the logged-in employee, not the language of the site. For multilingual teams, each person reads the warning in their own language.
In the checkpoints overview, you can see which triggers are active per zone.
Tasks that are attached to a zone work differently than at an NFC point. On entry, they are unlocked, but do not need to be completed immediately. The employee can move around in the zone, complete other tasks, leave the zone and re-enter. The task remains open until it is checked off. If the employee leaves the zone without completion, the app gives a proactive warning.
Not every crossing needs to be physical. App users can trigger geofences directly from the map; a tap produces the same action as crossing the boundary. This is practical for shifts where tracking begins with login.
Entries and exits appear as separate entries in the logbook, in the dashboard and in reports. You filter by zone, trigger type or employee. Clicking on an entry opens the details drawer with map, GPS accuracy and timestamp.
Geofences are not a separate data stream. They sit in the same audit trail as NFC scans and GPS points. Filter, history and PDF export work identically.
In the same release, we open the Community portal. Previously, feature requests came through support tickets. Now you see what's submitted, what's being discussed and when something goes live. Each suggestion goes through a six-step status process, including New, Public, In Development, Released and Closed. The submitter gets a notification with each status change. Suggestions with the most likes appear at the top of the list.
Posts are anonymous or under real names; anonymous requests do not publicly show the submitter. Discussions run with live updates without page reloads, with comments and replies. Replies from COREDINATE staff appear with a COREDINATE badge. The portal is available in German, English, French, Italian, Polish and Arabic.
Both updates are active in all COREDINATE packages as of Version 9.25. You create geofences under Area → Map view → New geofence. The Community portal is accessible from the left navigation, marked as "New".
The full changelog 9.25 with all bug fixes and minor improvements can be found at coredinate.de/help/changelog-produkt-updates. We now accept requests and improvement suggestions via the Community portal.
Not yet a COREDINATE customer? Talk to our sales team or order the 14-day test set with real equipment.