A technician can complete every item on an inspection checklist and still have an unresolved observation to hand over. If the app marks the whole job green, the office can miss the fact that someone needs to decide what happens next.
Our field-service mobile app separates those facts. Six items are recorded, one observation is flagged and the report awaits office review. The design follows the work from a particular asset into a reviewable handover.
Keep the equipment identity attached to the observation
The sample job concerns air-handling unit AHU–02. Its reference and plant-room location remain part of the inspection context. The checklist records that the equipment reference matches the site record before moving into the visual observations.
A well-written note attached to the wrong machine is still a bad record. The app should not require repeated navigation back to the asset screen just to confirm which equipment is selected. Our asset register and planned-visits workspace gives a broader view of that relationship: office planning and mobile inspection can show different details while retaining the same identity.
Completed recording is not completed remedial work
The flagged item concerns visible accumulation on the intake grille. It has observation reference O–017 and an attached image. The report explicitly states that no remedial work was recorded during the visit.
That sentence prevents a completed inspection from being read as a completed repair. It also defines the technician's contribution: a visual observation is being handed over for review.
A finished checklist can still contain an open observation
In a production app, decide what a completion label describes. The checklist, visit, report and underlying maintenance work may each finish at different times. One green status cannot safely stand for all of them.
Give the office a useful next task
The prepared report asks the reviewer to compare the observation with the earlier 17 September record and confirm the next action and owner. It names a service coordinator and shows that review as pending.
This is more useful than “see attached photo.” It tells the recipient what needs attention and provides a route into the relevant history. The reviewer can inspect whether the observation is new or continuing before deciding what should follow.
The visit was recorded as complete at 10:35; the report was prepared for review at 10:42. Keeping those events separate helps the next person understand what the technician completed and what the office still needs to do.
Asset to report
- 01IdentifyVerify the equipment and visit context.
- 02RecordKeep observations attached to that asset.
- 03Hand overDistinguish a working note from an issued report.
Design around the job on the small screen
We gave equipment, inspection and reporting their own compact screens. A technician beside a machine does not need every control in the central register. They do need the asset reference, current task and save state to remain clear.
Review the layout while entering a long note, with the keyboard open, as well as while reading. Then decide which features the working environment actually requires. Scanning and offline capture are separate requirements, not assumptions that come free with a mobile layout.
If offline work is needed, define what can be read and saved without connectivity, how unsent changes appear and what happens after an interrupted upload. The portfolio illustrates the recording sequence; a live synchronisation service needs its own implementation and tests.
Hand over the observation, not just the report file
Our architecture guide helps map those connections. In custom software development, we use the handover as an acceptance scenario: can the reviewer trace the observation to the equipment, inspect the image and identify the outstanding decision? If reports are formally approved or amended, the approval workflow guide explains how to preserve the earlier version.
Sources and calculation notes
The article follows job 2841, asset AHU–02, observation O–017 and report FR–2841 in the original mobile pages. The six recorded items, one flagged observation and one attached image are sample record counts. The report states that no remedial work was recorded and office review remains pending.
- Our field-service mobile app project. The project page includes the design account, delivered scope and screenshots discussed in this article.
- Our commercial field service asset register and planned visits project. The project page includes the design account, delivered scope and screenshots discussed in this article.
External references checked on 31 October 2026.