PR-5988 · Live
Time Guard
When a job finishes, Time Guard reads its timesheet entry alongside the job's location and job type, then compares the technician's actual travel time, job duration, and idle time against the benchmarks set for that kind of job. When a job runs past a threshold the Payroll Specialist set, the technician gets a reminder while the day is still going. When the variance is large enough to need a second look, the Payroll Specialist gets an alert with the job and the exact variance that triggered it. The jobs that need attention show up the same day they happen, so the conversation with the technician can happen while it still matters.
The promise
The Payroll Specialist stops finding out about time-compliance problems at the Friday timecard review, days after they happened. Time Guard surfaces them the same day. A long idle stretch or a job that ran two hours over shows up while the day is still current, with the times already on it, so the conversation with the technician happens when it can still change something. By Friday the review is a confirmation of work already handled.
How it works
The path from input to value.
- 01
Timesheet data is pulled per job
For each completed job, Time Guard reads the timesheet entry alongside the job's location and job type to establish how the technician spent their time.
- 02
Expected vs. actual is compared
Travel time, job duration, and idle time are each measured against the benchmarks set for that job type and location.
- 03
The technician is reminded when guidelines aren't met
When a variance exceeds the threshold, the technician gets an automatic reminder before the issue compounds across the day.
- 04
The Payroll Specialist is alerted when escalation may be needed
When the variance meets the escalation conditions, the Payroll Specialist gets an alert with the job details and the specific variance that triggered it.
The day before. The day after.
Same moments. Lived differently.
A technician runs two hours of idle time between two jobs. No one knows until the timecard review on Friday.
2:00 PMAn idle-time variance triggers a reminder to the technician automatically. The issue is surfaced the same day, not at the Friday review.
2:00 PMBefore
A technician runs two hours of idle time between two jobs. No one knows until the timecard review on Friday.
After
An idle-time variance triggers a reminder to the technician automatically. The issue is surfaced the same day, not at the Friday review.
A customer calls to say their technician arrived ninety minutes late. The Payroll Specialist has no data on the day's travel times and cannot explain what happened.
3:00 PMThe customer call comes in. The Payroll Specialist opens the job. Travel time, duration, and variance are already there. The conversation with the technician happens while the context is current.
3:00 PMBefore
A customer calls to say their technician arrived ninety minutes late. The Payroll Specialist has no data on the day's travel times and cannot explain what happened.
After
The customer call comes in. The Payroll Specialist opens the job. Travel time, duration, and variance are already there. The conversation with the technician happens while the context is current.
Weekly timecard review. The Payroll Specialist works through variances one by one. Most are too old to act on constructively.
4:00 PMThe timecard review is a confirmation now, not a discovery process. The variances were already addressed during the day.
4:00 PMBefore
Weekly timecard review. The Payroll Specialist works through variances one by one. Most are too old to act on constructively.
After
The timecard review is a confirmation now, not a discovery process. The variances were already addressed during the day.
One technician's pattern is clear in hindsight: consistent long travel on Wednesdays. The conversation happens seven days after the pattern started.
4:30 PMThe pattern surfaced the same day it occurred and was already addressed. The week's data is clean going into the weekend.
4:30 PMBefore
One technician's pattern is clear in hindsight: consistent long travel on Wednesdays. The conversation happens seven days after the pattern started.
After
The pattern surfaced the same day it occurred and was already addressed. The week's data is clean going into the weekend.
What it doesn’t do
The edges we drew on purpose.
A product that tries to do everything ends up doing nothing well. Here’s what we left out, and why we don’t feel bad about it.
- ×Does not modify timesheets or adjust job records based on variance findings.
- ×Does not track GPS or live technician location during the job.
- ×Does not score or rank technicians on overall performance.
- ×Does not replace the Payroll Specialist's judgment on situations that require a direct conversation with the technician.