The loop is always the same
Work arrives, it is scheduled to someone, it is completed, it is invoiced. The variety is in the constraints: skills, certifications, geography, equipment, customer requirements.
Generic scheduling software models the loop and not your constraints, which is where the fit breaks down and the whiteboard appears.
Scheduling constraints that matter
- Skills and certifications required for the work
- Geography and realistic travel time
- Equipment or vehicle availability
- Customer access windows
- Working time rules and existing commitments
Propose assignments; let a person confirm. Schedulers know things the data does not — who is having a difficult week, which customer needs the senior engineer.
The mobile side decides everything
- Works offline and syncs when signal returns
- Minimal interaction per job
- Photograph and signature capture that is quick
- Billable extras recorded — waiting time, additional work
- Exceptions reportable in one action
Anything requiring typing on site will not be used consistently, and inconsistent capture is worse than none because you cannot trust any of it.
Capture the follow-up work
Job notes contain future revenue: things that will need replacing, work the customer asked about, faults recurring at the same site. Most of it is written down and never read again.
Extracting that into a diarised list is frequently the highest-value part of an operational system.
Then invoice from what was captured
| Captured | Bills as |
|---|---|
| Completion with evidence | The base charge |
| Waiting time | Frequently unbilled today |
| Additional work | Variation |
| Failed access | Abortive visit |
| Out of hours | Premium rate |
Most operations businesses under-bill because these events are not captured reliably, not because they choose not to charge.