Work orders & hours Offline on the road Integration with the office

Custom field service app development

A field service app is the app in your engineer's hand: today's schedule, the registration at the customer's site, the materials used and the hours logged. Appfront builds that app to your requirements, tailored to how your field team really works and integrated with the systems at the office. It keeps working in basements and at remote locations, because that is where your engineers actually are.

What is a field service app?

A field service app supports the entire day of the employee who is out at the customer's site. They open the app and see their jobs, drive to the first location, carry out the work, record what they have done and which materials were used, get the customer to sign off and log their hours. At the end of the day the admin is done, instead of still having to begin.

That sets a field service app apart from a work order app, which focuses on a single document, and from a broader field service platform, in which the planner in the office also works with a planning board and dispatch. The field service app is deliberately the narrow part: everything the employee needs on the road, and nothing more.

Why keeping it narrow helps becomes clear in practice. An engineer often uses their phone standing up, with dirty hands, with a customer waiting beside them. Every screen they have to go through that gives nothing back costs you support. Apps that fail in the field rarely fail because of the technology, and almost always because of the number of actions they demand.

The day at a glance

Jobs, addresses and special notes are ready before the engineer drives off. Anything added along the way from the planning appears in the same list, with no need for a phone call.

Keep working without a signal

In a crawl space, a car park or a remote area, registration carries on. The app syncs as soon as there is a connection, instead of leaving the engineer waiting on a loading screen.

Finished before leaving the site

Registration, materials, hours and signature are completed on the spot. That saves the evening spent filling in receipts after the fact, with the inaccuracy that comes with it.

How we build your field service app

We start by riding along. Not for show, but because a day spent shadowing yields more than a work meeting: you see where the time goes and which steps the engineer is already working around.

1
Riding along and mapping the process

We spend a day out on the road. We record how a job reaches the engineer, what they currently register, what they are waiting for and which information they lack when they are standing at the customer's.

2
Design and integrations

We design the screens around the actions that occur most often and define the integrations with your planning, stock and administration systems. We also determine what needs to be available offline.

3
Building with engineers involved

We build in short iterations and have a number of engineers try out working versions. They weed out the screens that looked logical in the office but don't work in practice.

4
Rollout and maintenance

A phased rollout, usually starting with one crew and then widening. After that, ongoing maintenance and further development as your services or your systems change.

If your field staff work at locations covered by the Dutch Critical Entities Resilience Act (Wwke), you also need records that stand up to inspection. See the Wwke app for on-site resilience.

Two components that often belong in a field service app: receipts and invoice approval on the road, and, for those visiting housing locations, site checks and resident changes.

Two checks that often belong on the same device: whether a temporary worker has been registered and, for excavation work, whether the excavation notification is still valid.

If your field staff also inspect playground equipment in public spaces, that calls for its own round and its own file. See the app for playground equipment inspections.

What a field service app actually does

Which components carry the most weight differs from company to company. An installation company with service contracts has different priorities from a breakdown service. These are the features that come up most often.

Daily planning and route

Today's jobs with address, contact person and special notes, in the order in which they are scheduled. Changes from the office come in without anyone having to phone.

Digital work order

Record what was done, with photos and the customer's signature on the screen. The customer receives a confirmation straight away, which avoids discussion afterwards about the work carried out.

Materials and items

Record materials used on the work order, scanned or chosen from your own item catalogue. That keeps charging accurate and keeps the stock in the van visible.

Time registration

Hours are logged against the job they belong to, including travel and waiting time. This gives you a time record that works for both invoicing and payroll.

Installation history

On arrival, the engineer can see what has previously happened at this customer or on this asset. This stops a recurring fault from being investigated from scratch every time.

Additional work and follow-up jobs

If the engineer finds work that is not part of the job, they record it on the spot as a follow-up job or quote request, instead of taking it back on a scrap of paper.

The field services we build for

The nature of the work determines what the app needs to excel at. A fault-repair engineer and a periodic maintenance engineer have almost opposite needs.

Installation and service companies

Companies with a permanent team of engineers and a mix of maintenance, fault repairs and projects. See also our software for installers.

Technical management and maintenance

Teams that carry out periodic maintenance on a fixed portfolio. Here the history per asset carries the most weight, along with the integration with the maintenance system.

Fault-repair services

Teams that respond to reported faults and whose daily schedule is constantly changing. The app has to show changes without the engineer needing to refresh or phone in.

Field staff with a sales role

Employees who advise or sell alongside service work. They need customer data and a way to record a next step on the spot.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

The core of a field service app is the offline layer with well-thought-out conflict handling. Beyond that, the integration with the office determines how much the app really delivers: jobs come from your planning system, parts from your stock, and the completed job sheet goes on to invoicing. Without those integrations, you simply move the retyping from the engineer to the back office. If you would like to see what is on the market first, take a look at our overview of job sheet software suppliers.

If it is not about engineers but about account managers and sales representatives who visit customers, take a look at our app for account manager visit reports.

If your field team works door to door, in areas divided between teams, take a look at our route planning app for door-to-door canvassing.

Offline-first architecture Conflict handling during synchronisation iOS and Android (native or Flutter) On-screen signature Photos with compression Barcode and QR scanning of parts Location tracking and routing Push notifications for schedule changes Integration with ERP and accounting Integration with planning and dispatch REST integrations Role-based authorisation Encryption in transit and at rest Monitoring and alerting CI/CD pipelines

Why Appfront for your field service app?

We build custom software with smart technology and thoughtful design. In field service, that thoughtfulness is mostly about what you leave out. Every extra question on a screen is asked hundreds of times a week, and that is exactly where resistance to a new app comes from.

We work in design and development sprints, with engineers trying out working versions along the way. That feedback is more valuable than an extensive requirements document, because people only recognise what goes wrong in their day when they see a real screen.

The process runs from a no-obligation introduction through planning and development to maintenance. For a field service app, that maintenance phase matters: your services change, new contract types appear and your back-end systems get replaced. The app has to move with all of that without the engineer noticing anything.

Also take a look at our broader app development and what we do in custom software for business processes.

  • Custom apps for iOS, Android and web that fit your business process
  • A day riding along before anything is designed
  • Offline working as the starting point, not an optional extra
  • As few steps as possible per job
  • Integrations with your planning, inventory and accounting systems
  • Engineers involved during the sprints, not just at delivery
  • Phased rollout, starting with one crew and then widening
  • Clear documentation of integrations and data flows
  • Ongoing maintenance when your systems or services change

Security and data on the move

A field service app carries company data out of the door. The device holds customer addresses, contact details, contract agreements and sometimes access codes for buildings. A phone left behind in a van or lifted from a jacket is therefore a real risk that you cover in advance, not after the fact.

We encrypt local storage, tie the app to a user rather than a device, and make sure a lost device can be wiped remotely. Authorisation is role-based: an engineer sees their own jobs and the customer history they need, not the full customer database. Customer data falls under the GDPR, and so does the location data of your own employees.

That last point deserves an explicit decision. Location tracking is useful for routing, but tracking employees is a form of processing with its own legal basis and a sensitive conversation with your works council. We agree up front what is and is not recorded. Read more in our information security policy and coordinated vulnerability disclosure policy, or discuss it via our contact form.

  • Encrypted local storage on the device
  • Remote wipe in case of loss or theft
  • Sign-in per user, not per device
  • Authorisation by role and assigned jobs
  • Encryption in transit (TLS 1.2 or higher) and at rest
  • An explicit decision on recording location data
  • GDPR-compliant processing of customer and employee data
  • Documented data flows for your processing register

Frequently asked questions about building a field service app

What service companies usually ask us first.

If your field team carries out building surveys for energy performance, the survey sequence is bound to a protocol and each attribute needs supporting evidence. We cover that in building an energy label app.

A work order app revolves around one document: recording what was done and getting it signed off. A field service app supports the employee's whole day, including planning, route, material usage, time recording and customer history. The work order is just one part of it. Which of the two you need depends on how much is left over beyond that document.

Yes, and for most field teams that is a hard requirement. Crawl spaces, car parks and rural areas have no reliable coverage. The app keeps the day's jobs locally and synchronises as soon as there is a connection. Conflict handling is key: if the office has meanwhile changed the same job, that has to be resolved explicitly.

Usually, yes. We integrate with planning, inventory, ERP or accounting systems via their API. Without those integrations you merely move the retyping from the engineer to the back office, and the app delivers little net benefit. If your system has no usable API, we build an intermediate layer.

That is less often the problem than you might expect. What counts is the number of steps per job. We design around the actions that occur most often and let engineers review the app during the build. Where it goes wrong is with an app that was conceived at head office and only reaches the field at delivery.

Yes, and that is usually where most of the time savings come from. If hours and materials used are recorded on the job and that job is linked to your administration, the manual step between the work order and the invoice disappears. This does require your product catalogue and rate structure to be clearly set up in the source system.

We make the parts that change often, such as the fields on a work order, checklists per type of work and product groups, configurable so you can manage them yourself. Structural changes to the process or new integrations are development work. We agree up front which parts fall into which category.

In phases. We usually start with one crew who will genuinely use it, work in their feedback, and only then move the rest across. Rolling out to everyone at once creates too many simultaneous problems with a field service app to be able to tell which of them are structural.

That is often the sensible approach. Start with the tasks that take the most time, usually the work order and hours, then expand to materials, history and extra work. That way you can quickly see whether the process works before investing in the parts that are used less often.

Ready to build your field service app?

Tell us how your field staff work today and where the time goes: registration done in the evening, receipts that don't match invoicing, or engineers phoning in for information they should be able to see. We are happy to ride along for a day before we design anything.

Edit content