Imagi-Tech

Software

Field Service Software for Small Business: Dispatch, Timesheets and Offline Job Tickets

Field service software for a small business needs four screens done well: a dispatch board, a job ticket, proof of the work, and a timesheet that feeds payroll. On rural and basement jobs it also has to keep working with no signal, and that one requirement rules out more apps than any feature list does.

Use this as a test sheet. Whatever app you are looking at, subscription or custom, put each screen below in front of one of your crew and see whether it does the job in the truck, not in the demo.

The 4 screens every field crew app needs

1. The dispatch board

This is the office’s screen. Upcoming jobs wait in a queue, and whoever schedules drags them onto a day and a crew. Good crew dispatch software shows the whole week at once, makes it obvious when a truck is overbooked, and pushes changes to the crew’s phones the moment they are made. Test it by moving a job from Tuesday to Thursday and timing how long the tech takes to see it.

2. The job ticket

This is the crew’s screen: the address, the customer, what to do, and anything special about the site, like a gate code or a dog. It should open in one tap from the day’s list, and it should hold the history, so the tech can see what was done last visit without calling the office.

3. Proof of the work

Photos, a signature, and the few notes the office actually needs. Photos should attach to the job as they are taken, not get emailed later from someone’s camera roll. When this screen works, the photos and signature are the report, and techs close the job on a phone before leaving the driveway.

4. The timesheet

Time logged against the job, not against the day. On The PM Company’s tablets, crews pick a job, start tracking time, and switch to another job without starting over. Whatever the app, the hours have to reach payroll without retyping, and in a union shop they have to meet the reporting rules. Force Electric’s time tracking satisfies union reporting across several states.

An app that does those four well lets the office send the invoice the same day the job closes. One that does ten more things badly does not.

Working offline on rural job sites

Crews in our area work in places phones don’t reach: farm buildings, basements, steel buildings, and stretches of road between towns. An app that needs a signal to open a ticket fails right where the work is.

A real offline job ticket app works like this:

  • The day’s jobs load onto the phone before the crew leaves, with the history and the site notes.
  • Everything the tech does is saved on the phone first: notes, photos, signatures, time. Nothing waits for a connection.
  • Changes queue up and send themselves when the phone finds a signal again, and photos upload in the background.
  • The tech can see what has synced, so nobody wonders whether the office got it.
  • There is a rule for clashes. If the office edits a job while the tech is offline, the app decides which change wins and tells someone, rather than quietly losing one.

Test it the simple way: put a phone in airplane mode, work a job from start to finish, then turn the signal back on and check what the office sees. Ask whether offline support means working a whole job or only reading the ticket.

Off-the-shelf apps vs a custom build

For most small businesses, a subscription app that passes the tests above is the right start. A custom build makes sense when your job types, your reports or your per-seat bill no longer fit. We compared the two in detail, including what drives the cost of a build, in field service scheduling software: off-the-shelf or custom. For how we build crew apps, see custom software for mobile workforce companies.

Rolling it out to crews without pushback

The rollout question is mostly answered by the four screens. If a tech can open the day’s jobs, close each one with photos, and log time in less effort than the paper took, they use it. If any of those is slower than paper, no training session will fix it.

So test with crews before you buy or build, in the truck and on a site with bad signal, and change what they trip over. Our post on getting field crews off paper covers the order to roll it out in, and what the office has to give up.

Example: JobTrax for The Proz

JobTrax, the app we built for The Proz in Parkersburg, maps onto those four screens. The general manager drags queued jobs onto the week calendar and loads each truck. Customer records hold contracts and routine jobs, so each ticket carries its history. Photos taken in the mobile app reach the office while the crew is still on site and turn into the job’s report. We have been building and improving the same system with The Proz for more than eight years, one round of crew feedback at a time.

Free audit

Let's get started

Tell us what's giving you trouble, in your own words. "Our Access database is dying" is plenty to go on.