Scheduled is not the same as completed.
A maintenance or service company has to dispatch technicians efficiently and then prove, job by job, that the work actually happened, not just that it was on the calendar.
“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.
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 gate, 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.
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 job isn't done
until there's proof it was done.
We will map Hirebase to your compliance framework,
your ERP and your region.
© 2026 Hirebase. All rights reserved.