Keep every asset’s service history in one usable record.

A service history is only useful when the team can find it.

When previous work sits across spreadsheets, PDFs and individual inboxes, technicians arrive without context and the office has to reconstruct the asset story again.

Return completed work to the asset that needed it.

The asset record provides the starting context. The completed visit and final report add the next reliable entry.

• Open the maintained equipment. See the customer, site, manufacturer, model, serial number and upcoming work attached to the asset record.
• Record what happened on site. Keep the visit time, checklist results, findings, actions, photos and customer confirmation with the work order.
• Carry the result forward. Completed work and the final report appear against the asset for the next office user or field technician.

An asset record with service context attached.

This controlled ilarvo sample shows demonstration data from a fictional service workspace. It illustrates the product record and is not customer evidence.

• Asset: Air Handler 04 · AHU-04018
• Customer: Atlas Property
• Site: Atlas House · roof plant room
• Next service: 28 August 2026
• Quarterly air handling service: Checklist completed and belt tension adjusted.
• Filter inspection: Filter condition recorded with three photos.
• Service report SR-2714: Final PDF available to an authenticated user.

Prepare a return visit without rebuilding the asset story.

A technician is assigned to equipment another colleague serviced three months earlier. The asset history provides the previous finding, completed work and final report before the new visit begins.

• The dispatcher confirms the correct customer, site and asset.
• The technician reviews previous work before arriving on site.
• The completed visit adds another dated entry to the same asset.

Focused on service history, not every asset discipline.

ilarvo keeps operational service records around customer equipment. The asset remains the reference point for field work and reports.

• History covers completed work and final service reports recorded in ilarvo.
• Equipment values, depreciation and financial lifecycle records remain outside this workflow.
• The quality of the history depends on the work your team records.

Frequently asked questions

Answers about this ilarvo workflow and its current product boundary.

• What appears in an asset’s service history? The current product shows completed work and final reports linked to the asset, alongside the asset’s customer, site and identifying details.
• Can a technician review earlier work before a visit? Yes. An assigned technician can open the asset and visit context available to their role before recording new work.
• Does importing an asset create past service records? No. The standard CSV import creates customer, site and asset records. Service history grows as work is completed and reports are finalized in ilarvo.