Paper job sheets get lost, arrive three days late and are illegible. The information you need to run the business is sitting in a van door pocket.
TL;DR Count the taps before you buy. Offline mode must genuinely work. Invoice from site, which transforms cash flow. Roll out with one technician before all of them.
Count the taps
The single best evaluation test, and almost nobody does it.
Complete a full job in the app, on a phone, and count every tap and every screen.
- Under 15 taps for a routine job: good.
- 15 to 25: workable, expect some resistance.
- Over 25: it will not be used properly and your data will be incomplete.
Do this on a phone, not a tablet, not a laptop. Most technicians use a phone regardless of what the business bought.
Do it wearing work gloves if that is realistic for the trade. Small touch targets fail in real conditions and no demo will show you this.
Offline is non-negotiable
Plant rooms, basements, lofts, rural properties, lift shafts. Signal fails routinely.
Test properly
- Put the phone in airplane mode.
- Complete an entire job, including photos.
- Turn connectivity back on.
- Verify everything synced, including full-resolution photos.
Failure modes to watch for
- Photos queue but never upload.
- The app appears to work but discards data on reconnect.
- Sync conflicts if the office edited the same job.
- A spinner that never resolves, forcing a force-quit that loses the entry.
If offline mode fails this test, the platform is unsuitable, whatever else it does well.
The mobile job sheet
Structure it in the order the work actually happens.
- Job details and customer history. What was done last time, visible immediately.
- Arrival. Tap to start, which triggers the on-the-way text and the time log.
- Before photos.
- Findings. Fixed list plus free text.
- Work done. Fixed list.
- Parts used. Selected or scanned.
- After photos.
- Recommendations, for the next visit or a follow-up quote.
- Customer signature.
- Complete, which triggers invoicing and the feedback sequence.
Fixed lists wherever possible. Free text does not aggregate, cannot be reported on, and takes longer to enter on a phone.
Required fields on the things that matter, and nowhere else. Over-requiring produces junk entries as people work around it.
Photos
The most valuable data captured on site.
- Minimum counts enforced. Two before, two after, at least.
- Automatic tagging to the job, with timestamp and location.
- Sensible compression. Full resolution on mobile data is slow and expensive.
- Annotation on device, to circle the problem.
- Same angle before and after.
Photos are your defence in a dispute, your marketing content, and your customer communication. Treat the requirement as non-negotiable.
Digital signatures
On the phone, on site, before leaving.
What it needs to capture
- Signature and printed name.
- Timestamp and location.
- What exactly is being signed for. Work completed, or authorisation for extra work.
- Automatic copy to the customer.
The extra-work authorisation is the one that saves money. A signed on-screen approval for additional work found on site prevents the most common invoicing dispute in the trades.
Invoicing from site
The highest-impact change in this whole article.
Traditional cycle: job done, paperwork returns to office, invoice raised days later, payment terms start, payment arrives weeks after the work.
On-site cycle: job done, invoice generated on the phone, emailed or texted immediately, payment link included, frequently paid before the van leaves the street.
What it changes
- Days sales outstanding falls substantially.
- Disputes drop, because the customer is standing there while the invoice is explained.
- Admin time collapses. No re-keying.
- Payment on the spot becomes normal rather than awkward.
Enable card payment on the device. Tap to pay on a phone removes the last friction point.
Rolling it out
One technician first. The one most likely to engage, not the one who most needs fixing.
- Pilot with one person for two weeks. Real jobs.
- Fix what they hit. There will be things.
- Have them train the next two. Peer training beats management training substantially.
- Roll out with paper running in parallel for a fortnight.
- Set a hard paper cut-off date and hold it.
The parallel period must end. Indefinite dual running means nobody commits to the app.
Expect a temporary productivity dip. Say so in advance so it does not read as failure.
Handling resistance
Most resistance is reasonable and specific.
- “It takes longer.” Often true at first. Count the taps and fix the genuinely slow parts.
- “My phone battery dies.” Real. Provide chargers, and check the app’s background behaviour.
- “I cannot see it in sunlight.” Real. Nothing you can do about the screen, but you can reduce how much reading is required.
- “It is surveillance.” Address directly and honestly. Say what is tracked and what is not.
Listen to the specifics. Blanket resistance is rare. Specific complaints are usually accurate and fixable.
Measure it
- Time from job completion to invoice sent. Should be minutes.
- Days sales outstanding, before and after.
- Jobs with complete records. Photos, parts, signature. Target near 100 percent.
- Admin hours per week in the office.
- Taps per job, revisited after a few months as the workflow settles.
Time yourself completing one full job in your current app, on a phone, counting taps. If it is over twenty-five, fix that before rolling anything out further.
Need a pro to set it up? [BOOK A CALL]