- Field service software has four jobs: get the right person to the right job, give them what they need on site, capture the work, and turn it into an invoice the same day.
- The technician app must work with weak or no signal, because basements, plant rooms and rural sites are where the work happens.
- Continuous location tracking is tightly controlled by Android, Google Play and iOS; recording location at check-in and check-out is often enough.
- Job sheets should be checklists and forms the office can change without a new app release.
- Buy an off-the-shelf tool for standard trade work; build or extend when inspections, reports or integrations are specific to your business.
What does field service software need for a team on the road?
Field service software needs to do four things well: get the right person to the right job, give them everything they need on site, capture the work with photos, notes and a signature, and turn it into a report and an invoice the same day. It must also keep working where the signal is weak, because plant rooms, basements and rural sites are where field work happens. Everything else is secondary until those four work.
Whether you buy a field service tool or have one built, judge it by a normal day: how a job comes in, how it is assigned, what the technician taps on site and how long it takes the office to send the invoice.
What should the office side do?
- Take in jobs from every channel: phone, web form, email and repeat maintenance contracts, all landing in one list.
- Show a scheduling board by technician and day, with travel between jobs visible.
- Dispatch by skill, area and availability, including certificates or vehicle stock a job needs.
- Notify customers with confirmations, reminders and an on-the-way message.
- Handle changes: reschedules, cancellations and emergency jobs that bump the plan.
Availability rules, time zones and calendar sync work the same way here as in any booking tool; our guide to booking and scheduling systems covers them in more depth.
What does the technician's app need?
- Today's jobs in order, with address, access notes and a tap to open directions.
- Customer and site history: past visits, equipment on site, photos from last time.
- A job sheet with checklists, readings and required photos, set up per job type.
- Parts and materials used, ideally scanned, so van stock and the warehouse stay correct. Our article on inventory software for a small warehouse covers the stock side.
- Time on the job recorded from status changes rather than typed in afterwards.
- Customer sign-off with a signature or name, and an option to email the report on the spot.
Keep the screens few and the buttons large. A technician wearing gloves on a ladder will not use a form with twenty small fields.
Should the app track technicians' location?
Decide this early, because the platform rules are strict. Continuous tracking while the app is closed counts as background location:
- Android: apps targeting Android 10 (API level 29) or higher must declare a separate background location permission. On Android 11 and higher, the permission dialog does not offer "Allow all the time"; users must turn it on in a settings page.
- Google Play: its location policy allows background location only when it is needed for the app's core functionality, and apps that use it must be approved through the permissions declaration process in the Play Console; without that approval, updates can be blocked.
- iOS: Apple's documentation says an app must request When In Use permission first and only then ask for Always authorization.
For many teams, recording the location when a technician taps "on my way", "arrived" and "finished" is enough. It happens while the app is open, gives the office what it needs and is easier to explain to staff. If you do track continuously, tell staff exactly what is recorded, limit it to working hours and keep the data only as long as you need it.
How should the app work with weak or no signal?
Download the day's jobs, forms and customer details in the morning. Save every change on the device first and send it when the connection returns, photos included. Show clearly what has not been sent yet. If two people can edit the same job, decide which change wins. Our guide to planning offline mode walks through storage, sync and conflicts step by step.
A web app can work offline too: MDN's guide to offline and background operation explains how service workers make that possible. The trade-offs between a web app and a native one are covered in our PWA or native app comparison; background location is one of the features that usually tips the decision towards native.
How do jobs turn into invoices without retyping?
The job already holds the labour time, the parts used and the customer. Turn it into a draft invoice automatically when the technician finishes, let the office review it, and send it with the job report attached. Sync invoices and payments to your accounting software in one direction so they are not entered twice. If technicians take payment on site, use your payment provider's card reader or a payment link rather than storing card details in your own app.
Off-the-shelf or custom field service software?
An off-the-shelf tool fits well when your work looks like a standard trade: plumbers, electricians, cleaners or HVAC teams with common job types. Look for one with good mobile apps, an API and a clean data export.
Custom software, or a custom app on top of your existing systems, makes sense when:
- inspections and reports follow your own or a regulator's format that the tools cannot produce;
- jobs depend on equipment records, contracts or stock held in your own ERP;
- you run several kinds of work, such as installs, rentals and repairs, with different flows;
- the per-user price of a tool grows faster than your team.
Our mobile app development team usually starts with the technician's job sheet and the office board, then adds invoicing and reporting once the core flow is in daily use. For back-office pieces, see custom software development.
Frequently asked questions
Can technicians use their own phones for the app?
Yes, many small teams do. Protect company data with proper sign-in, ideally with a second factor, and make sure the office can revoke access the day someone leaves. Keep customer photos and documents inside the app rather than in the phone gallery, so they do not end up in personal backups.
Do we need a native app, or will a web app do?
A web app or progressive web app can handle job lists, forms, photos and signatures, and it can work offline with a service worker. Choose a native or cross-platform app if you need background location, reliable barcode scanning at speed, or deeper access to the device. Many teams start with a web app for the office and a native app for the field.
What should customers see from the system?
At minimum, a booking confirmation, a reminder before the visit and a message when the technician is on the way. After the job, send the report, photos and invoice in one message. A simple link that shows the job status saves the office a lot of phone calls.
How do we handle checklists and inspection forms that change often?
Build the forms as data, not as screens. The office edits questions, required photos and answer types in an admin panel, and the app downloads the new version. Keep old versions with the jobs that used them, so a past report always shows the questions that were asked at the time.
What reports should managers get from field service software?
Start with jobs completed and outstanding, first-time fix rate, time on site versus time travelling, parts used and invoices raised but unpaid. Pick the few that drive decisions each week, and make sure each one is defined the same way for every technician.
Last updated