Field service documentation
Capture the evidence needed to complete a service visit.
ilarvo gives technicians a structured place to record what they checked, found and did, keeping the evidence with the visit and the maintained asset.
A completed visit should not leave the office asking what happened.
Free-text notes alone rarely provide the same evidence from every technician. The office needs the checklist result, finding, action, photo and confirmation attached to the actual visit.
Record evidence within the visit, not as a separate reconstruction.
The checklist defines the expected structure while findings, actions and media explain the work that was actually completed.
- Follow the visit checklist. Record each required position and the reading or outcome the service process calls for.
- Add findings and actions. Describe an issue, record the action taken and attach photos where they add useful evidence.
- Confirm the visit outcome. Finish with time, summary and a customer signature or documented exception.
Structured evidence from one fictional maintenance visit.
These fields and records belong to a controlled ilarvo sample. They demonstrate how visit evidence is organized and do not represent a customer outcome.
- Checklist: Quarterly AHU service · seven positions
- Visit time: 09:32–10:52
- Photos: Three sample images attached
- Confirmation: Customer signature recorded
- Belt tension outside target: Observation recorded against Air Handler 04.
- Belt tension adjusted: Completed action linked to the finding.
- Supply temperature · 18.4 °C: Measured value stored with the visit.
Document an inspection that includes corrective work.
During a quarterly service, the technician records a checklist exception, adjusts the equipment, adds supporting photos and captures the customer confirmation.
- The finding and completed action remain connected.
- Photos and readings stay with the same field visit.
- The final report uses evidence already recorded by the technician.
Your service process defines the evidence that matters.
ilarvo provides the documentation workflow. Your team remains responsible for the checklist, technical standard and records required for its work.
- Checklists structure technician input but do not make technical decisions.
- Photos, findings and actions reflect what the signed-in user records.
- Customer confirmation is stored as a signature or documented exception.
Frequently asked questions
Answers about this ilarvo workflow and its current product boundary.
- What field evidence can ilarvo store? The current visit workflow supports time, checklist results, findings, actions, readings, photos and customer confirmation.
- Can a finding and its action stay connected? Yes. A technician can record the observed issue and the action taken within the same visit record.
- Does ilarvo provide the technical checklist for every trade? No. Your service team defines and reviews the checklist content appropriate to its equipment and work.