Work orders and dispatch Offline in the field Integrated with your ERP

Field service app development

A field service app supports engineers in the field and the planners who allocate their work: work orders, dispatch, offline working, asset registration, digital signatures and invoicing. Appfront develops custom field service management (FSM), built around your own working process, integrated with your ERP, and usable in a basement with no signal.

What is a field service app?

Field service management (FSM) is the software layer that keeps a service organisation running: scheduling work orders, supporting the engineer on site, recording what was done, and passing it on to invoicing. It touches dispatch, execution, reporting and invoicing all at once, and has to work on a phone in a lift shaft with no reception. Field service is the English term for what we describe on our field service app page.

What sets it apart from a general planning app is the combination: dispatch based on skills, location and SLA priority, a mobile app that works without coverage, an asset register that remembers which valve belongs to which customer, and reporting that makes first-time fix rate and SLA compliance measurable. Much of what distinguishes a good FSM solution lies in the edge cases: a part that is unexpectedly missing, an inspection signed off by the customer, a rejected installation that becomes a new work order.

For standard service, ServiceMax, Salesforce Field Service or Microsoft Dynamics 365 Field Service often cover it well. We build custom for organisations that are too specific for those packages, sometimes as an addition to an existing system, sometimes as a complete field service app that replaces the paper work order.

Engineer app with dispatch

Work orders, history, photos and signature, with a planning board for the planner.

FSM with assets and contracts

Asset register, SLAs, preventive maintenance and route planning.

FSM with IoT and customer portal

Sensor alerts that create a ticket automatically, and self-service for the customer.

How we build your field service app

We start with the flows through your service organisation: how a fault comes in, who plans, which skills are needed, which assets are under contract and which systems talk to each other. Then we shadow an engineer and the planning team, because that is where we see the real way of working rather than the version on the process diagram. From that come the integrations, the data model and the first screens. We build in short iterations: your planner tests the planning board, and one or two engineers test the app under real conditions in the field. A pilot with one region or one service team follows, and a phased rollout to the rest, with training for planners and engineers and ongoing development based on what the field reports back.

1
Introduction and scope

Faults, planning, skills, assets and systems mapped out.

2
Shadowing and architecture

Shadowing an engineer and the planning team, then integrations and data model.

3
Build and field test

Planning board and app tested by your planner and engineers.

4
Pilot, rollout and management

One region or team first, then the rest.

What a field service app actually does

No organisation needs everything at once. We start with the modules that remove the biggest bottlenecks and build further once the foundation is in place. For maintenance of installations and machines alongside engineer scheduling, we connect to a CMMS (maintenance management system).

Planning by skill and route

Work orders to the right engineer based on skills, certification, location and SLA, with route optimisation.

Mobile engineer app

Work order, customer and asset history, photos, signature, materials, hours and serial or QR code scanning, fully offline.

Job sheet and reporting

Job sheets generated from what the engineer records, with first-time fix rate, mean time to repair and SLA compliance.

Flow through to invoicing

Hours, materials and mileage to accounting or ERP, with contract hours and time-and-materials hours split and the correct VAT rate.

Asset and contract register

Installations per site with serial number, warranty, contract and history, plus preventive orders generated from contract triggers.

Parts and van stock

Stock per service van and reordering; for scanning per job and replenishment orders there is our app for the technician's van stock.

Customer portal

Report a fault, track the planning, view asset history, contracts and invoices, all under your own brand.

Integrations

ERP, CRM, accounting, customer contact centre, IoT monitoring and a custom order management system.

Who we build a field service app for

Service organisations differ widely in working methods, regulations and assets. These are sectors where we often end up building custom, because each sector has its own inspections and liabilities.

HVAC, electrical and plumbing

For installation companies with maintenance contracts, a fault service and projects, where NEN 3140 inspections and NEN 1006 demand rigorous record-keeping.

Lifts

NEN-EN 81 and the statutory inspection requirement call for maintenance history per lift, certificates and data that is kept for years.

Fire protection

NEN 2535 and NEN 2654 require records per installation, signed reports and alerts when maintenance is overdue.

Medical equipment

Service under the MDR, with UDI registration, traceability per action and retention periods.

Grid operators and smart meters

Large work order volumes, fixed appointment windows and certification per type of work for gas, electricity and water.

Aftersales on machinery

Service contracts, parts, retrofits and remote diagnostics. For the machine with its configuration and history there is our app for a machine builder's service department.

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 technician app runs on iOS and Android and works fully offline, including in basements, on ships and in underground networks; as soon as there is coverage, it synchronises. The planner works in a web app with a planning board, drag-and-drop rescheduling, the current status of every technician and estimated arrival times for the customer. For the service vehicles, we integrate with a fleet management app where needed.

iOS and Android Offline synchronisation QR and barcode scanning Digital signature SAP Exact AFAS Salesforce HubSpot Microsoft Dynamics IoT monitoring Route optimisation

Why Appfront for your field service app?

A generic FSM package is a poor fit if your sector has its own inspections, if sensors need to create tickets themselves, or if you deliver service under your own brand. That is where we build, together with your planners and technicians rather than from a feature list. You receive the source code, documentation, an admin manual and training for key users. You can find examples of previous projects on our work.

Built with the field

We ride along with technicians and sit in on planning before we build.

Only what you use

The modules you need, without licences for features you never touch.

No vendor lock-in

The source code, documentation and architecture are yours.

Security and privacy in a field service app

A field service app processes data about customers and employees: addresses, contact details, signatures, photos on site and often the technician's location. That is personal data under the GDPR. We only record location where it is needed for planning, restrict access by role, and log who changed what.

Data on the phone is stored encrypted, so a lost device does not become a data breach. The environment runs in a European data centre, with encrypted connections, backups and monitoring. We retain inspection reports and certificates for as long as the regulations in your sector require. We document the processing in a data processing agreement.

Frequently asked questions about a field service app

What clients usually want to know before we start.

Field service management (FSM) is software for service organisations with technicians in the field: scheduling work orders, supporting the technician on site, recording what was done, and passing that on to invoicing. A field service app is the part the technician uses on their phone.

Field service is the English term for buitendienst. A field worker app can be simpler, such as a digital work order. An FSM solution combines that app with dispatch by skill and SLA, an asset register, contracts and reporting on first-time-fix rate and SLA compliance.

Yes. The technician app works fully offline, including in basements, lift shafts, on ships and in underground networks. Work orders, history and forms are stored on the device, and everything the technician records syncs as soon as there is coverage again.

For standard service, those packages are often a good choice. Custom is worth considering if your industry has inspections that no package covers, if sensor data needs to create a work order automatically, if an enterprise package is too heavy for what you actually use, or if you want a customer portal under your own brand.

With ERP systems such as SAP, Exact and AFAS, with CRM systems such as Salesforce, HubSpot and Microsoft Dynamics, with your accounting, the customer contact centre, IoT monitoring and a fleet management app for the service vehicles. Hours, materials and mileage then flow to invoicing automatically.

Yes. We build forms with mandatory fields and logic per inspection, for example for NEN 3140, NEN-EN 81 for lifts or NEN 2535 and NEN 2654 for fire alarm systems, with the customer's signature and reports that are retained for as long as required.

First in a pilot with one region or one service team. After their feedback comes a phased rollout to the rest, with training for planners and technicians, monitoring from day one, and releases in the app stores as part of ongoing management.

Talk to us about your field service app

Tell us how your service organisation works, which systems you use and which inspections you need to record. We will give you direction, even if the outcome is that a standard package is a better fit.

Edit content