It is twenty to seven in the evening and Javier has been parked on the hard shoulder for ten minutes, engine running, job sheet pad on the steering wheel. He has done four jobs for three different clients: an inspection of lighting panels on a business park, a fault at the pumping station of a logistics platform, and two preventive visits to transformer stations. He fills in the sheets from memory, because they are due at the office at eight tomorrow.
He thinks he spent two hours at the pumping station, although it was nearly three. He used a contactor from the van stock, but does not note it, because the pad has nowhere to put it. The photos are in his phone gallery, mixed with those from the other three sites and with pictures of his daughter. And the business park caretaker asked him, while he was there, to replace a light fitting at the entrance. He replaced it. That job was on no work order and will not be on the sheet either.
The next morning an administrator types the sheets into the system. At month end, the manager prepares the report for a client asking for evidence of the panel inspection and finds the photos cannot be linked to any specific panel. Nobody did anything wrong. The system was designed for this to happen.
What gets lost, piece by piece
When the sheet is written after the job and away from the asset, different things are lost, each with a different cost.
Hours. They get rounded, usually down on the hard job and up on the easy one. The labour cost of each order stops resembling the real one, and so does the margin per contract.
Materials. What leaves the central store is usually recorded; what leaves the van is not. That stock is replenished without being charged to any order and ends up in overheads.
Extra work. The job the client asks for on the spot is the easiest to lose. It is done, time and materials are consumed, and it is never invoiced because it never reached the office.
Evidence. A photo with no date, no position and no linked asset proves nothing. Faced with a claim, it is worth the same as having no photo.
Findings. The pit with the broken cover the technician saw on the way is on no order, so it never becomes an incident. It will be seen again when it is a fault.
Not discipline, but design
The usual reaction is to ask technicians to be more rigorous. It rarely works, because the problem lies not with them but with when they are asked to record. A form completed at the end of the day relies on memory; one that needs coverage is not filled in on a remote plant or in a pump room below ground; one that duplicates another system feels like paperwork and gets done badly.
The sector recognises this. Among the conclusions of Infraspeak's report on the state of facility management, presented at IFMA Spain's Workplace Summit in October 2025, are "operational overload" and a "lack of strategic KPIs". Both relate to what is described here: teams spend time recording afterwards what they already did, and the indicators built on that record are unreliable because the source data is too.
What rewriting job sheets costs
The calculation can be done with your own figures, and it is worth doing before discussing tools. An illustrative example: a contractor with fifteen technicians, each spending twenty minutes a day filling in sheets outside the job, over 220 working days, adds up to 1,100 hours a year. On top come the hours of whoever retypes them, the manager assembling reports at month end and the van stock that is never recharged.
None of these items appears as such in the profit and loss account. They sit within overheads, which is why they look unavoidable. Unbilled extra work does not appear at all: it is simply revenue that never happened.
What a work report app should do
A useful work report app is not an on-screen version of the paper pad. It has to change when recording happens: the sheet is completed on site, during the job, and what the technician enters is already the final data.
That takes several things at once. The technician moves the order through its states and records times on the asset itself. Forms are tied to the type of job, with the fields the client will ask for. Photos are taken inside the order, dated and positioned, before and after. Materials used are deducted from the stock they came from, van stock included. The app works offline for a full day and, when signal returns, everything goes up at once, with no half-finished uploads. And a finding outside the order can be opened as an incident there and then.
What Maptainer provides here is a field app that closes the order on the phone without connection, with forms by maintenance type, dated and georeferenced photo evidence, a sign-off signature on the device and materials deducted from stock, including the vehicle's mobile store. When signal returns, the day is consolidated in a single upload, and each closed order carries its cost of materials, hours and mileage.
How to tell whether it worked
Changing the tool is not enough; you have to check the data changes. Two or three months after rolling out a work report app, review five things: the share of orders closed on the day they are carried out; whether recorded hours approach the real working day or still fall short; whether materials used on orders match van replenishments; what share of orders has photo evidence linked to the asset; and how many incidents are opened from the field, the sign that findings are no longer being lost.
If any of these does not move, the cause is usually operational rather than technical: the order was not on the phone before leaving, the form asked too much, or someone still accepts paper sheets. Ask the technicians before blaming them. They usually know exactly what sends them back to the pad.