OpenFence
For field-service teams

Geofencing for field-service teams — the job clock runs itself

When a technician crosses the customer's geofence, time-on-site starts; when they leave, it closes — as a signed, timestamped event that flows straight into your field-service platform and billing. No "did you remember to clock in."

Start free trial Try the live demo

Stop chasing timesheets — the geofence is the timesheet.

Field service runs on time-on-site you can't pin down

Billable hours, SLA windows, and payroll all hinge on when a technician arrived and left. Manual clock-ins miss it; the real times live in nobody's system.

Clock-in friction

"Did you remember to clock in?" Manual timesheets come in late, rounded to the quarter-hour, and easy to game.

On-site time, on the record

Billable time-on-site shouldn't rest on memory. A signed record backs what your tech already reported — to the minute.

No proof of service

SLA windows and "we were on site at 9" deserve a timestamped record, not a dispatcher's callback.

How a service call becomes evidence

The same real path every job runs — geofences, devices, events, signed webhooks, evidence.

  1. 1

    Geofence each customer site

    A geofence around every job address — service, maintenance, install.

  2. 2

    Devices on the techs / vans

    Registered devices report location as the route runs.

  3. 3

    enter / exit / dwell

    Arrival on site, time-on-site (dwell), and departure — clocked automatically.

  4. 4

    Signed webhooks

    Each event pushes into your FSM & billing — HMAC-verified, retried, dead-lettered on failure.

  5. 5

    Proof of service

    Every event is backed by an explainable trace — defensible evidence, not a guess.

See the evidence a service call leaves behind

Every technician arrival, time-on-site, and departure lands as a timestamped, signed event — and each one pushes a delivered webhook into your platform. Here's what that evidence trail looks like in the dashboard, for an example HVAC company:

openfence.ai/dashboard/events
OpenFence dashboard event feed: an HVAC company's technicians arriving at and departing customer sites through the day, each row a timestamped geofence enter or exit with a delivered webhook.
openfence.ai/dashboard/events
OpenFence event detail: a technician's geofence.enter arrival at a customer site, showing the signed payload and a webhook delivered with HTTP 200 in 124 ms.

Illustrative — example tenant (Acme HVAC Co) with sample data. The dashboard UI is the real product.

A real company runs OpenFence — the WDA case study → Try it on your own phone →

The same platform you'd build on

Nothing here is field-service-only plumbing. OpenFence is domain-agnostic by design — the same PostGIS geofences, enter/exit/dwell events, signed-webhook contract, rules engine, and explainable traces serve any fleet. This page just speaks field service's language; the engine speaks any vertical's.

Other use cases Explore events See the rules

Put every service call on the record

Start free — $0 today, 14-day trial. Geofence a customer site and watch the time-on-site clock itself.

Start free trial See the quickstart