Software for maintenance and field service: work orders in the field

A maintenance and field service company lives off something that is almost never in a system: what happened the last time someone visited that unit. The request comes in by phone or WhatsApp, someone writes it down, hands it to a technician, and the result comes back on a crumpled sheet two days later. Everything learned on site is lost.

We build custom software for end-to-end work order management: the work order, the assignment, the technician app that works with no signal, spare-part consumption and the report the customer signs. It is not a routing system: the center of it is the installed unit and its history.

What kind of companies it fits

Companies whose business is going out to fix something at the customer's site: elevators, HVAC and air conditioning, electronic security, industrial machinery, medical equipment, electrical and plumbing installations, and after-sales technical service. They all share the same shape: a fleet of units installed at different addresses, contracts with response times, technicians on the road and a spare part that has to be deducted from somewhere.

Where the information gets lost today

The technician arrives, inspects, swaps a part and fixes it. What was done stays in their head and on a sheet of paper. When another technician returns to the same unit, they start from zero: no idea what was replaced, with which part, or why it failed last time. The company cannot answer what that customer costs to serve either, because hours and parts were never tied to the order.

The second gap is connectivity. The units sit in machine rooms, basements, plants and rooftops — exactly where there is no signal. Any app that needs the network to save forces the technician to redo the report outside, and that is where the detail disappears.

When a system of your own is worth it

It is worth it when service is the business, not an internal task: there are contracts with response levels, technicians billing their hours, parts being consumed and customers asking for a report. Also when what has to be recorded does not fit a standard form, because every type of unit has its own checklist.

It is not worth it if you maintain your own machines and bill nobody for it: that is a different problem and a different system.

Do your work reports come back on paper two days later? Tell us how your circuit works and we will find where to start.

Spreadsheets, an off-the-shelf product, or your own system

Off-the-shelf products handle the generic well. The limit shows up with your own checklist, with the way contracts get billed, and with integrating the management system you already run.

The field technician app has to work with no signal

This is the requirement that defines the architecture, not a detail. The app stores the order, the photos, the checklist and the signature on the phone and queues them. When the network returns it syncs on its own, resolving conflicts with explicit rules: who wins if the office changed the order while the technician was inside.

It is the same approach we use in shop-floor recording systems, where the data is captured on site and cannot depend on connectivity. If you also want the report to be drafted from a photo or a voice note by the technician, that builds on AI process automation.

Preventive and corrective maintenance in one circuit

Corrective maintenance arrives as a request: something broke, someone calls. Preventive maintenance is scheduled from the unit record, by frequency or hours of use, and generates the orders on its own without anyone having to remember. Both use the same report, the same checklist and the same history, which is what makes it possible to see which units break between preventive visits — the data that actually improves the plan.

What drives the cost?

Cost is driven by the scope of the first circuit, how many equipment types with different checklists must be covered, how many technicians and roles use the app, the integration with your management or billing system, migrating the history currently sitting in spreadsheets, and where the infrastructure runs. We estimate after mapping the real circuit and separating the essentials from what can wait. Tell us about your case and we will scope it.

Cases

Common mistakes

• Leaving offline for later: it defines the architecture. Adding it at the end means rewriting the app.
• One checklist for every unit: the technician ends up writing everything into "notes".
• Digitizing the paper as it is: if the paper report was not working, the same report on a screen will not either.
• Forgetting the end customer: the signed report is what backs the invoice and prevents the dispute.

If your operation is about fleets and delivery rather than on-site repair, the starting point is different: see software for logistics and transportation. And if you are just starting with no system at all, custom software for SMEs.