Service · App development

Custom work order app for your field service team.

A digital work order on the phone of your engineer, installer or service engineer. Receive the work order, tick off tasks, take photos at start and completion, scan materials, have the customer sign with a finger — all available offline, all straight into your ERP. We build it custom, in your branding, native for iOS and Android.

Offline-firstPhoto & signatureMaterial trackingERP integration

A work order is not a form, it is the handover between field and office.

For decades the paper work order was the heart of your operation: the engineer fills in what was done, the customer signs off, and that slip of paper is the basis for your invoice, your timesheet, your warranty administration and your quality file. When that paper goes missing or comes back illegible, you lose revenue — and the engineer who fills everything in properly loses you time.

A digital work order app takes over that role and does more with it. The data is instantly available in your time-tracking software, your planning and your invoicing. Photos come along, the location is stamped automatically, and the signature is legally valid under eIDAS. And because it is custom-built, it fits your work process step by step: no workarounds for features that don't exist, no fields your engineers ignore.

We build work order apps for installers, construction companies, service engineers, cleaning organisations, security firms and landscapers. The underlying technology is similar, but the details (which fields, which photo moments, which signature status, which ERP integration) differ per industry and per organisation. That is where the work is, and that is where the value lies.

The choice between custom and an off-the-shelf package comes down to a specific point: as soon as your work process no longer fits the form fields of a SaaS tool, or as soon as your ERP integration needs to go deeper than a nightly export, you hit the limits of the package. We build from the other direction: first the actual flow of your engineer, then the app around it. It takes more thinking in the first sprints, but adoption is higher afterwards and the annual costs become more predictable.

If your field service operates under VCA, toolbox meetings and valid certificates belong in the same system as the work order; see VCA file management. Lifting equipment also has its own inspection obligation, covered on inspection app for lifting equipment.

Three flavours of work order app.

It depends on the complexity of your work orders, the depth of your integrations and the requirements your industry sets. We advise which variant fits in the first conversation; often a project starts with the first form and grows along with you.

Compact project · fixed sprint budget

Digital work orders & photo reporting

The core: the engineer receives a work order, ticks off tasks, takes photos at the start and at completion, records hours worked and materials, and has the customer sign. The PDF work order lands directly in the mailbox of the customer and the office. Suitable for organisations that still work with paper, WhatsApp photos or a spreadsheet and want to take their first digital step.

Work ordersPhotosCustomer signaturePDF email
Mid-sized project · fixed sprint budget

Work order + planning + ERP

The work order app is linked to your planning and your ERP. The engineer sees today's schedule in the app, checks in on location via GPS, scans material EAN codes, and on completion the work order is automatically sent as a draft invoice to AFAS, Exact or Visma. For organisations that want to automate their time administration and speed up invoicing.

Planning syncGPS check-inEAN scanAutomatic invoicing
Larger project · fixed sprint budget

Custom platform with industry compliance

The work order app as part of a broader field service platform. Including eIDAS qualified signature, Wkb file for construction, AS9100/IATF traceability for industry, BCT eIDAS quality marks for transport and integrations with several ERPs at once. For organisations with strict audit and compliance requirements and multiple business units.

Materials bought on the road belong on the same work order and the same project. How to capture that on the spot is covered on the ViDA app.

eIDAS QESWkb fileAudit logMulti-ERP

What you get at the end.

A working work order app in the App Store and Play Store under your own accounts, plus the back office and integrations that keep it running. You own the code, with no per-employee subscription model on top.

  • Native iOS and Android appPublished under your own Apple and Google developer accounts, in your corporate identity, ready for silent rollout via MDM or through the stores.
  • Back-office web appFor planners and the office: create, schedule and assign work orders, track statuses and search historical work orders.
  • ERP and planning integrationsTwo-way integration with AFAS, Exact, Visma, Plan-Visie or whatever combination you run today. Including retry logic and monitoring.
  • Full source codeYou own the code. Develop it further yourself, bring in another developer, or stay with Appfront — your choice, not our lock-in.
  • Documentation & runbookArchitecture overview, build instructions, API documentation and an incident runbook for your IT team.
  • Training for planners and engineersA session for the back office, a short instruction video for engineers in the field, and a first-aid card on a single A4 sheet to keep in the van.
  • Maintenance contract (optional)Monitoring, store updates, security patches and ongoing development for a fixed monthly price. Four response-time levels, transparent SLA.

When a custom job sheet app is the right choice.

Four patterns in which clients come to us. If you recognise one, we'd be happy to talk further, even if you're still unsure whether custom is really necessary.

Off-the-shelf package does not fit

Your work process is different

You have tried a SaaS package such as Jobber, ServiceM8, mHelpDesk or Mobile Field Report, but while 70 per cent of the features fit, the other 30 per cent don't match how you actually work. Workarounds pile up, engineers get frustrated, and the data ends up polluted in your ERP.

Subscription costs keep growing

Per-user pricing doesn't scale

You grow from twenty to fifty engineers and the monthly SaaS bill grows proportionally, while the functionality stays the same. Beyond a certain number of employees, your own software often works out cheaper over its lifetime.

Industry compliance

Audit requirements that SaaS doesn't cover

You work in a sector where Wkb, AS9100, IATF, NEN 7510 or a transport quality mark is mandatory, and the SaaS package only covers the generic layer. You have to build the compliance reporting yourself, which is close to custom territory.

Integration depth

ERP, planning and CRM need to work seamlessly together

Your API integration with AFAS, Exact, Plan-Visie or NTOS needs to be bidirectional, with retries, idempotency and monitoring. Standard connectors don't reach that level, so it takes a custom architecture.

Brand & customer experience

The job sheet is a brand moment

The job sheet is often the last point of contact between engineer and customer. An impersonal SaaS app with a stranger's logo in the corner doesn't tell the same story as an app that is fully in your brand. For service organisations with strong customer loyalty, that carries through to NPS and renewals.

Data ownership

Your historical data belongs to you

With a custom solution, your data sits in a database that you own, not with a third party. That makes reporting, BI integration and exports for research or acquisition processes trivial — instead of a batch export function that your SaaS supplier might get round to prioritising one day.

Job sheet apps by industry — because the details differ.

The underlying app is similar, but the fields, photo moments, compliance layer and integrations with industry-specific systems vary widely. Here is a selection of the sectors we build job sheet flows for:

Installation engineering (electrical, heating, plumbing)

Work order with meter readings, boiler or installation type, gas certificate, F-gas registration and maintenance stickers. Often linked to a maintenance contract and automatically recurring appointments.

Construction & finishing

Job sheet with Wkb file export (Dutch Building Quality Assurance Act), quality photos per construction phase, materials list and hours integration. See also our app development for construction.

Service engineers & fitters

Multi-stop daily planning, GPS check-in, scanning materials from the van, photo on completion, customer signature on screen. Often linked to an SLA tracker for response times.

Cleaning organisations

Location object map, cleaning protocols per room, quality control by the team leader, and customer feedback per round. Often with QR codes at locations.

Security

Rounds with QR checkpoints, incident reporting with photo and classification, client signature, and an audit log for the regulator. Suitable for site security and mobile patrols.

Lift and climate engineering

Job sheet with inspection records, F-gas administration, EN‑81 checklists, and an integration with your maintenance file per object. Including an audit log for the inspection body.

Landscaping & grounds maintenance

Work order with object map, materials receipts, weather logging, and before-and-after photo reports. Suitable for both private and municipal maintenance.

Transport & logistics

Trip job sheet with eIDAS-qualified signature, loading and unloading confirmation, CMR photos, and an integration with your TMS. For distribution, removals and special transport.

Industrial service & breakdown engineers

Fault analysis form, AS9100/IATF traceability, RCA fields, photo and video reporting, and a direct integration with your CMMS or asset management system.

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 →

How a work order app project runs.

No black box, no fixed template — your process leads, and we break it down piece by piece.

1

Introduction

A conversation in which we learn which work orders you handle, which ERP and planning system you run, how many engineers will be involved and what is causing you pain right now. We show you what we have built before for similar organisations and give you an honest steer — even if the conclusion is that a SaaS package fits better after all.

2

Work process review

A workshop with your planners, engineers and office staff. We join your people in the field, look at your existing work orders and speak to two to four engineers — because the pain sits in the details the office rarely sees. Result: a concrete process diagram, the scope for the app, a list of fields per work order type and an acceptance checklist.

3

Building in sprints

A working build every two weeks. First sprint: an engineer can receive a test work order, take a photo and sign. After that we build up materials, planning sync, GPS, ERP integration and the compliance layer — in order of your priority. A small group of engineers is already using the app from sprint two, so we find out early what works in practice.

4

Pilot with one team

Before an organisation-wide rollout, the app first runs in one region, one team or one branch of your work. We monitor error reports, sync failures and engineer feedback daily and patch immediately. The pilot ends with a go/no-go — no go unless it genuinely works.

5

Rollout & support

A phased rollout to your entire field team, MDM integration where applicable, app store publication and ongoing management. Our support line is built into your incident procedure. Further development runs in a rhythm of sprints or on request — your choice.

How we differ from SaaS packages.

Jobber, ServiceM8, mHelpDesk, Mobile Field Report and some twenty similar solutions do a perfectly good job for those who fit them completely. For those who don't, these differences weigh more heavily than many organisations realise.

Code ownership, no lock-in

You receive the source code in your own repository. If you want to bring in another party in two years' time, or develop it further yourself, you can do so without data migration or contract penalties. We earn by delivering value, not by keeping you tied in.

No per-user pricing

You pay for the build and the management, not per engineer per month. With a team of twenty that may come out the same; at fifty or a hundred it scales differently. We make the calculation transparent in the second conversation.

Built vendor-independent

We build on open standards — native iOS, native Android, mainstream backend frameworks, established cloud platforms. Not on a proprietary SaaS layer that forces you to stay. Our API integration layer is a separate component that you can replace or extend independently.

Truly custom, not just branded

Many SaaS packages offer "white-label" with your logo on it. We build the flow ourselves around your process: which fields, in which order, with which validation and which automation. No work order field you never fill in, no missing field you need every day.

Compliance is not an add-on

eIDAS signatures, GDPR data processing agreements, working-time-compliant hours registration, Wkb files for construction, AS9100 or IATF for industry — we build them in from the design stage, not as a layer on top. Audit logs are standard, not an "enterprise tier feature".

You work with a dedicated team

No ticketing system sending you through level 1, 2 and 3. One developer knows your codebase and is your point of contact. A second developer acts as back-up so that holidays or illness don't affect your operation. Short lines of communication, even after go-live.

Frequently asked questions.

What clients usually want to know before we start a work order project.

Does the work order app also work without mobile coverage?
Yes. For a field app it's a hard requirement, and it's the first sprint we build. Work orders are synced to the device in advance. Text, photos, signatures and materials can all be recorded fully offline. As soon as there is a network connection again, they sync automatically with your back office. We resolve conflicts with a last-version-wins rule and an audit trail.
Is the customer's digital signature legally valid?
As standard we deliver an eIDAS-compliant "Advanced Electronic Signature" (AES), with biometric data captured at the moment of signing and an audit log. For sectors where it is mandatory — transport (BCT), certain public-sector contracts, healthcare — we build a "Qualified Electronic Signature" (QES) via a trusted provider such as Signicat or Cleverbase. Both stand up to legal scrutiny.
Which ERP and planning systems do you support?
We have built integrations for AFAS, Exact, Visma, Plan-Visie, Manage-X, NTOS, Mollie, Stripe and Quinyx, among others. For any new system, we carry out an integration study at the start of the project. If your ERP has an open API, we can integrate with it. If not, we advise on practical workarounds — for example an intermediate database or a batched export.
What is the difference from a general field service app?
A work order app is a specific type of field service app. The field service app is broader: it could be an account manager app, an inspection app, a healthcare app or a sales app. A work order app is aimed specifically at service work where a work order is closed with a customer signature and a billable line. If in doubt, we first talk about your work process — then we choose the right form.
How do you handle GDPR and privacy?
A DPIA for every project, a data processing agreement as standard, encryption in transit and at rest, an audit log for all data access, and a built-in retention layer — work orders are not kept longer than you are legally required to or want to keep them. For healthcare-related sectors we add NEN 7510; for public tenders, ISO 27001 compliance.
Can engineers record their hours via the work order app?
Yes, time tracking is almost always built in: start time, end time, travel time, any breaks and a project code. For organisations with strict working-hours compliance or a complex collective labour agreement, we build the hours layer as a separate module, often in combination with our time tracking solution.
Do you work with our IT department and our own cloud?
Almost always. We can run in your Azure, AWS or Google Cloud, or in our own environment. We deliver infrastructure as code so your administrators know exactly what is deployed. For rollout via MDM (Intune, Jamf, MobileIron), we supply the configuration profiles.
What if I already use a work order package?
Then we talk about migration. We can bring over historical work orders via an ETL job, we first run the integrations to your ERP in parallel, and rollout happens team by team or region by region. Many clients start with a hybrid approach — new orders through the custom app, ongoing orders in the old package — and phase over two to three quarters.
How long until the first engineer is actually using it?
An MVP with the core (receiving a work order, photos, signature, PDF to mailbox) is ready for a pilot after a few sprints. A full project with planning sync, ERP integration and a compliance layer runs over several sprints. We don't commit to a calendar date for the pilot going live — but we do commit to a working build every two weeks.
Who writes the copy and designs the app?
We handle design in-house: UX, UI and a visual identity that fits your brand. We propose fields, labels and validation messages based on your work orders and discuss them every sprint — because this is where the details that irritate engineers live. Do you have a brand style guide or your own designer? Then we'll work with them.

Talk to us about your work order app.

A no-obligation introductory call of half an hour. Tell us about your work process, your ERP, the size of your fleet and your industry — we'll give you direction on what is realistic, what is unnecessary and where the first gains lie. Prefer to email directly? That works too: fabian.vandijk@appfront.nl.

Share this page: LinkedIn Email

Edit content