A field service app: from work order to signature and invoicing

When a service technician, installer or construction crew heads out to a site, a chain of calls, messages and paperwork often follows. The address arrives by email, an extra instruction by phone, hours get jotted in a notebook, and materials end up in Excel at the end of the day. The work is done, but the company still does not have all the data needed for billing.

A field work application connects the whole process: the office prepares and schedules the work order, the crew picks it up on their phone, records the work done, hours and materials, adds photos, obtains the customer's signature and submits the order for review. After approval the data is ready for billing or transfer to the ERP.

The same need is often also called a work order program, a field service app or an app for field teams. Whatever the name, the solution needs to connect the entire flow, not just replace paper with a screen.

What a good mobile work order needs to connect

A work order program is only useful once it reduces work both on site and in the office. If the technician fills in a digital form but the administration retypes the data back into the accounting program, only the form has been digitised, not the whole process.

1. The office creates and schedules the order.
2. The field worker picks it up on a mobile device.
3. The app shows the location, contact, description and attachments.
4. The technician records arrival, work, hours and materials.
5. They add photos, measurements or other evidence.
6. The customer reviews a summary and signs it if needed.
7. The responsible person reviews and approves the order.
8. The confirmed data go into billing, the ERP or an archive.

Each step has a status, a responsible person and a time. The office therefore knows, without calling anyone, whether an order is scheduled, taken on, in progress, completed, returned for completion or ready for billing.

The office schedules work without improvising over the phone

The process starts in the office. A dispatcher, service manager or project manager opens an order and enters only the data the team actually needs:

• the customer, contact person and address,
• the type of work and the agreed time,
• a description of the problem or scope of work,
• the expected materials and equipment,
• safety or access instructions,
• photos, plans and other attachments.

The order is assigned to an individual or a team. The schedule can be shown by day, team, location or priority. If an urgent call out comes in, the office reschedules and the worker sees the currently valid state on their phone.

The first version does not need to handle every possible exception. It first needs to reliably answer three questions: who goes where, what needs to be done, and what needs to be submitted at the end. This is also the basis of good business process automation.

The mobile screen needs to be built for the field

The mobile view should not be a shrunk down version of the office program. The worker needs to understand the order within a few seconds. At the top they need the time, address, contact and type of work, then the description, attachments and a clear button to change status: taken on, on the way, started or completed.

The address can open in navigation. If a site has several devices, entrances or work areas, an internal code, floor, serial number or on site contact needs to be shown too. A technically flawless app does not help if it sends the crew to the wrong entrance.

Buttons need to be large enough to use with one hand, forms need to be short and messages clear. Important actions such as submitting an order or deleting a photo need unambiguous confirmation. There is less room on a phone, so hierarchy matters more than the number of features.

Photos, materials and hours get entered where the work happens

Most data get lost between the completed job and returning to the office. After a few days no one remembers exactly what material was used and which photo belongs to which order.

A field service app therefore allows entry on the spot:

• arrival, departure, travel or waiting time, where relevant for billing,
• hours worked per technician,
• materials used and quantity,
• serial numbers or equipment codes,
• steps carried out and faults found,
• recommendations for the next visit,
• photos before and after the job.

A photo is saved against the specific order, not just in the phone's gallery. The same applies to a signature, document or comment. This way the office does not need to work out who a generically named file belongs to.

Entry needs to be structured enough for later use, but not so extensive that the team starts skipping it. Only fields without which the order cannot be checked or billed should be mandatory.

The customer's signature closes the agreed part of the job

After finishing the work, the technician shows the customer a summary: what was done, how long it took, what materials were used and whether an open task remains. The customer can review the record and sign on the phone or tablet.

A signature on its own does not resolve every question of proof. What matters is the entire record: who carried out the order, when, at which location, what was entered and which version of the summary the customer saw. Depending on the type of business, contractual and archiving requirements also need checking.

After signing, the customer can receive a PDF, and a copy remains attached to the order. In the event of a complaint or a question, it is immediately available to the right person.

What happens when there is no signal on site?

Construction sites, basements, production halls and remote locations do not always have a reliable connection. An app that shows only a blank page without internet is not enough for serious field work.

Offline mode needs to be part of the design. Before leaving, assigned orders and the necessary data are saved onto the device. During work, entries, photos and signatures are stored temporarily on the device. Once the connection returns, the changes sync with the central system.

• Decide which data are allowed to be stored on the device.
• Protect them in case the phone is lost or stolen.
• Decide how many large photos can wait for upload.
• Resolve conflicts if the office and the field change the same order at the same time.
• Show the user: saved on the device, waiting to upload, or synced.

The worker should never have to guess whether their completed order actually reached the office.

Review and approval before billing

A completed order is not necessarily ready for an invoice. A photo might be missing, the quantity of material might be unclear, or the recorded hours might not match the agreement. This is why a step of approval between completion and billing makes sense.

The manager or administration sees incomplete orders in one place. They confirm the order or return it with a reason for completion. Rules can be simple: a photo is mandatory for a given type of job, materials need a quantity, deviation from estimated hours needs a comment, and a required signature must be present before submission.

This kind of check catches an error before the invoice is issued, not only after a customer complaint.

Transfer to billing or the ERP without retyping

After approval, the app prepares a structured export or, via an API, transfers the customer, services, hours, materials and order reference into the ERP or billing program. Feasibility depends on the specific system, licence and available interface.

Where an API is not available, a well defined CSV or XML export can be more reliable than screen automation. It is also important to define the primary source of data: customers and price lists can come from the ERP, while the field record is created in the app. More on this in the guide to integrating business systems.

Rights, location and employee privacy

A field application contains data on customers, schedules, employees and sometimes location. A technician should see their own orders, a manager the schedule for their team, and administration the data needed for billing. Significant changes need to be traceable.

For location data, first define the business purpose. If a location at the start of an order is enough, there is no reason for all day tracking. Employees need to know what data are collected, when, why, who sees it and how long it is kept. For more sensitive cases, have the design reviewed by the person responsible for data protection or an appropriate legal expert.

Standard software or a custom application?

A standard solution makes sense when your process follows a common pattern and the team is willing to adapt to it. It rolls out faster, the initial cost is usually lower, and the provider handles general updates.

A custom solution makes sense when:

• you have special scheduling or billing rules,
• a standard program requires many workarounds and extra spreadsheets,
• you need a connection to an existing ERP or your own records,
• different teams use different forms,
• reliable offline operation is essential.

A common middle path is that the accounting or ERP system stays as it is, while a custom app manages the field part and sends confirmed data into it. The decision should be based on the process, not on the longest feature list.

What to include in the first usable version

• creating and assigning a work order,
• a mobile view of orders with clear statuses,
• entry of hours, materials and notes,
• photos and the customer's signature,
• submission for review and approval,
• a PDF summary and a basic export for billing.

If the team regularly works without signal, basic offline mode needs to belong in the first phase. Advanced route optimisation, stock, analytics and additional integrations can follow after real first use. The page how we work together shows how we get from an inventory to a prototype and a first version, and an outline of the initial scope is published in the development price list.

How to measure whether the app succeeded

Before rollout, record the starting state, then measure the same things after the first month:

• time the office spends preparing and closing one order,
• number of days from work completed to invoice issued,
• share of orders returned due to missing data,
• number of calls to the field for extra clarification,
• unbilled hours and materials,
• time spent searching for photos, signatures or paperwork.

The most useful app is not the one with the most features. It is the one the field team actually uses even at the end of a tiring day, and which hands the office data ready for the next step.

Related reading: when Excel is no longer enough and how much a custom application costs.