Verify Every Field Service Call.
Eliminate Ghost Dispatches & Travel Disputes.
Commercial service contractors lose margin to unverified travel hours and disputed work orders. Hirebase connects technician dispatch directly to configurable site boundary geofencing and photographic proof-of-work—producing verified, audit-ready records to defend client billing.
“The ticket says it's closed. Can we prove the tech was actually there?”
Dispatching the right technician to the right job is only half the problem. The other half is what happens after: a closed ticket with no photo, no location, and no timestamped record is a claim, not proof, and it's the first thing a client disputes.
A status field a technician sets from a truck can say anything. It has no bearing on whether the truck was ever at the address, or whether the work behind the status change actually happened. Dispatch and proof-of-completion have to live in the same system, or the dispute takes longer to resolve than the job itself did.
Dispatch through the Master Project View, not a phone tree.
A dispatcher builds the day in a drag-and-drop Master Project View: drag a technician onto a job, and it's assigned. There's no separate call to confirm it and no group text to track who picked it up. Every job on the board carries one of eight statuses, the same vocabulary a dispatcher, a technician and a client all read the same way, from Unscheduled through Punch In, Punch Out, or an exception like No Show or Conflict. Full mechanism detail lives on Scheduling & Field Execution.
A missed job requires a note, not just a tap.
Marking a job No Show is not a single click. A dispatcher has to type why, so the record explains itself later without anyone having to remember the context, whether that's a locked entrance, a canceled visit, or a technician stuck on the previous job.
The same mandatory-note pattern applies to Missed Punch and Conflict, so exceptions on a service route stay explained, not just flagged.
A route doesn't reach a truck until it's published.
A day's schedule stays in Draft while a dispatcher is still building it, moving jobs between technicians, reordering stops, or waiting on a last-minute add. Technicians only see the route once a dispatcher takes the explicit publish step, so nobody drives to a job that was still being reassigned an hour earlier.
Publishing is a distinct action from saving, by design: the draft route and the live route are never the same view.
What actually counts as proof a technician was there.
“Completed” as a status is a claim. Hirebase backs it with two kinds of evidence attached directly to the job record, not stored in a separate system a dispatcher has to go dig up when a client disputes an invoice. The full report catalog behind that evidence is covered on Reports & Analytics.
Up to five photos, on the job record.
An incident or job record can carry up to five photos, attached directly to the record itself rather than emailed in afterward or left on a technician's phone. Before- and-after shots, a damaged part, a completed repair: whatever the visit needs to show, it's attached to the same record a supervisor or a client will review later.
Up to five photos per record, attached directly, not routed through a separate inbox.
Every visit reconciled against the job's actual address.
Using real routing data, the Enhanced Punch report computes Distance From Job, Travel Time and Traffic Time for every punch, checked against the job's actual address rather than a self-reported location. Each punch also carries an in and out selfie photo alongside a map pin, so the reconciled distance and travel-time figures sit next to visual and location confirmation for the same event.
Distance, travel time and traffic time are computed per punch against the job's address; in/out selfies and map pins sit on that same punch record.
When a client asks “how do we know the tech was actually on-site,” the answer is the punch record itself: address-reconciled distance and travel time, a timestamped in/out selfie, and a map pin, all on one record instead of three separate systems.
A technician visiting several equipment sites in one shift doesn't need a separate punch session for each: a single session can nest multiple job-site check-ins, with distance and travel time computed per leg on a route map. That is route tracking, reviewed after the fact, not route planning or optimization in advance.
Field maintenance & service dispatch decision criteria.
Compare Hirebase against point field service software and standalone time-tracking apps across on-site proof, multi-stop route telemetry, visual dispatch, and licensing.
| Operational Requirement | Hirebase Platform | Point FSM Software (ServiceTitan, Jobber) | Point Time Tracking Apps (Deputy, When I Work) |
|---|---|---|---|
| Proof of Physical On-Site Attendance | 10m site geofence validation, 1.5s live facial anti-spoofing, and in/out selfies with numeric confidence score. | ~Technician simply taps 'Job Completed' from their truck in a driveway with zero biometric identity verification. | Basic smartphone app with easily spoofed GPS coordinates, no facial anti-spoofing, and zero post-specific hazard sign-offs. |
| Multi-Stop Route Telemetry & Leg Reconciliations | Single punch session nesting multiple job-site check-ins (up to 5 stops per shift) with per-leg GNSS distance and travel duration (raw distance & time, no mileage reimbursement). | ~Disconnected job appointments that do not calculate actual transit or traffic time between service calls. | Standalone shift punch with no multi-stop job-site check-ins or leg-by-leg transit duration tracking. |
| Visual Dispatch & Master Project View | Centralized drag-and-drop board with 8 standardized shift statuses, explicit publish discipline, and mandatory typed notes for anomalies. | ~Rigid calendar dispatch views that notify technicians of unfinished draft revisions immediately. | Disconnected schedules per location with no multi-property contractor view or real-time status tracking. |
| Job Evidence & Photographic Documentation | Up to 5 photos attached directly to the job/incident record (before/after repair, serial numbers, damaged parts) + DWC workers' comp tracking. | ~Loose photos stored in generic customer attachments, often disconnected from the technician's actual payroll timesheet. | Unstructured plain-text notes field or external supervisor text messages with zero OSHA or workers' comp audit defensibility. |
| Software Economics & Flat Enterprise Licensing | Predictable flat enterprise licensing with zero per-technician monthly seat tax; add seasonal technicians and apprentice helpers with zero cost penalty. | ~High per-technician monthly fees ($50-$250/tech/mo) that penalize contractor fleet expansion and apprentice hiring. | Compounding per-user monthly seat tax ($4-$8/user/mo) that escalates costs when rotating field crews. |
Stop Ghost Dispatches & Invoice Disputes
10m geofence boundaries, facial anti-spoofing verification, and Enhanced Punch routing data ensure every billed service hour reflects verified on-site work.
Zero Per-Technician Headcount Tax
Scale field service crews and dispatch apprentice helpers across commercial jobs without incurring escalating monthly per-user software fees.
Frequently asked questions about maintenance dispatch software.
Clear operational answers on how Hirebase proves technician arrival, reconciles multi-stop routes, prevents premature draft dispatch, and scales under flat licensing.
How does Hirebase prove that a maintenance technician physically arrived at a job site?
Hirebase enforces a dual-verification check on every service call: an admin-defined 10-metre GPS geofence boundary around the commercial address, paired with a 1.5-second live camera selfie with facial anti-spoofing algorithms. The arrival punch button stays disabled until the photo is verified, ensuring technicians cannot log jobs remotely.
How does Hirebase track travel duration and routing distance between multiple service calls?
The Enhanced Punch report computes the actual routing distance, elapsed travel time, and traffic duration between sequential job stops using real GNSS coordinates. A technician visiting multiple properties in a single shift can nest up to five job-site check-ins within one session, providing clients with auditable travel records.
Can field service dispatchers handle mid-day schedule changes without sending confusing alerts to technicians?
Yes. Schedulers build and modify routes in a Master Project View where assignments stay in Draft mode until explicitly published. Technicians only receive shift alerts once the dispatcher confirms the route, ensuring field crews never drive to canceled or reassigned calls.
Does Hirebase charge per-technician monthly subscription fees or software seat licenses?
No. While legacy field service software charges $50 to $250 per technician per month, Hirebase operates under a flat enterprise licensing model. Service contractors can dispatch direct technicians, seasonal helpers, and subcontracted specialists without paying per-seat software fees.
Go deeper
Practical answers for your evaluation
A job isn't done
until there's proof it was done.
We will map Hirebase to your compliance framework,
your ERP and your region.