Time & attendance
The first job of the day
Geofenced check-in marks the start from the customer site in Austin. The board shows the Kent and Almeria patches filling up on the same screen.
The workforce
Mobile, ticketed, and rarely in the office.
Patches · on site now
Austin9All in
Kent71 late
Almeria51 on leave
A field service workforce is engineers and technicians who start from home or a depot, drive to the customer, and finish the day somewhere else. Supervisors cover a patch of jobs rather than a single floor. The people furthest from HR carry the licences, the van kit and the hours that pay has to get right.
Where it breaks
The problems that live in this world.
Not generic HR pains: the specific ways this environment grinds people teams down, one honest description at a time.
The timesheet lives in the van.
Hours are written down at the end of a long day, driven back on Friday, and typed up by someone who was not there. Memory rounds them, and the payroll argument is scheduled for month end.
Tools leave with the person.
Meters, tablets and van kits are issued in a hurry and forgotten when someone moves patch or leaves. The next job starts short, and nobody can say who still holds what.
A lapsed ticket stops the job.
Gas safe, electrical and access tickets each expire on their own clock. The office finds out when the customer does, at the door, on a morning that was already booked.
Cover is a phone tree.
When an engineer calls in sick before the first job, someone has to re-plan the day by text. If absence lives in one supervisor’s phone, the rest of the operation finds out when a customer is left waiting.
Day to day
Three operational realities, handled.
Attendance, pay and compliance are where this world gets judged. Here is how each one runs on a connected record.
01
Clock in at the job.
Geofenced check-in records the start of the day from where the work actually is. The live board shows every patch at once: who is on a job, who is late, who has not arrived.
02
Hours to pay without a middleman.
Approved overtime feeds the next pay run with nothing re-entered. Each run is validated and two people must sign off before anything pays out on the hours the clock recorded.
03
Tools and tickets on the same record.
What each person was issued sits beside the licences they carry. Expiry warnings fire well before a ticket lapses, and the leaver checklist surfaces outstanding returns before the final day.
The modules that fit
Take what fits, leave the rest.
HarmoniHRM is modular. These are the pieces that earn their keep in this world, each reading and writing the same connected record.
Time & attendance→
Geofenced check-in at the job, and one live board across every patch.
Asset & equipment tracking→
Van kits, meters and tablets tracked from issue to return, surfaced at offboarding.
Compliance watch→
Trade tickets and medicals watched with expiry countdowns per person.
Payroll→
Hours from the clock reach a validated, dual-control run with nothing retyped.
Organo→
Patches and depots on one live chart, with presence visible site by site.
Leave management→
Approvals that show who else on that patch is already off before you say yes.
A working day, connected
How the day actually runs.
Follow one realistic cycle through HarmoniHRM, step by step, from the first event of the day to the numbers that close it.
01
The first job of the day
Geofenced check-in marks the start from the customer site in Austin. The board shows the Kent and Almeria patches filling up on the same screen.
02
A dawn absence gets covered
The no-show is visible the moment the shift should have started. Cover is arranged from the patch roster, and the absence lands on the record rather than in one supervisor’s phone.
03
A 60 day ticket warning fires
Compliance watch flags a gas safe certificate two months out. The renewal is booked while the engineer can still legally take the job.
04
A van kit is issued and remembered
The meter and tablet sit on the record against that person. When they move patch, the kit moves with them or is marked for return.
05
Overtime flows to the run
The late call-out is approved on the timesheet and appears in the next pay run automatically, at the statutory treatment configured for that country.
06
A leaver hands the kit back
The offboarding checklist surfaces the van kit and access before the last day, so the next engineer does not start short.
Who lives this
The people inside this playbook.
Asset & equipment tracking
A dawn absence gets covered
The no-show is visible the moment the shift should have started. Cover is arranged from the patch roster, and the absence lands on the record rather than in one supervisor’s phone.
Compliance watch
A 60 day ticket warning fires
Compliance watch flags a gas safe certificate two months out. The renewal is booked while the engineer can still legally take the job.
Payroll
A van kit is issued and remembered
The meter and tablet sit on the record against that person. When they move patch, the kit moves with them or is marked for return.
Asked before buying
The questions that come up every time.
How does clock-in work for someone who never visits the office?
Geofenced check-in is built for field teams: the day starts on the person’s own record from where the job actually is. Hours land on the same record payroll reads, so claimed hours and paid hours stop being different numbers.
Can we see several patches as one organisation?
Yes. Each patch is part of one live structure in Organo, with presence, absence and open roles visible per site, and the attendance board covers every team at once.
What happens to tools when someone leaves or changes patch?
Asset tracking holds what each person was issued. The leaver checklist surfaces outstanding returns before the final day, and a transfer keeps the kit on the same record so it does not vanish between patches.
How do trade tickets stay current?
Every ticket sits on the employee record with expiry warnings well before the date. The renewal is a task in the office, not a discovery at the customer’s door.
Run it on your own organisation.
Modular pricing, no long contracts. Start with the modules this world actually needs and add the rest when you are ready.