Replace fragmented field-service spreadsheets with a connected service record.

The information exists, but it does not move with the work.

The maintenance date sits in one sheet, the last finding in a PDF and the model number in a message. Each visit begins with another search for context the business already has.

Move the operational record, not just the spreadsheet rows.

Start with a standard customer, site and asset directory, then keep new work and evidence attached to those records.

• Import the standard records. Prepare customer, site and asset data in the standard CSV template and validate it before import.
• Prepare visits against the right asset. Create work orders and assigned field visits without separating the job from its service context.
• Return evidence to the service history. Keep completed work and the final PDF available against the asset for the next visit.

One service job before and after a connected record.

This controlled comparison uses fictional files and ilarvo records. It demonstrates an information flow and does not claim a measured customer result.

• Source date: Quarterly service · spreadsheet row
• Previous finding: Bearing noise · separate PDF
• Asset detail: AHU-04018 · separate message
• Connected record: Asset, visit and final report in ilarvo
• Due work without visit context: The office searches three sources before dispatch.
• Assigned visit with asset context: The technician opens one prepared work record.
• Evidence returned to asset history: The completed work and final PDF remain together.

Move one representative workflow before moving everything.

A service company starts with one customer hierarchy, a representative asset group and the field workflow used for repeated maintenance.

• The standard CSV preview exposes data issues before import.
• New work starts against the imported customer assets.
• Completed visits build a service history the team can use.

Replace the fragmented service record with a defined scope.

ilarvo focuses on customer equipment, field work, evidence and reports. Specialist business records can remain in the systems responsible for them.

• The current import follows the standard customer, site and asset template.
• Historical operational records are not created unless they are genuinely available in ilarvo.
• A focused first workflow keeps the transition reviewable.

Frequently asked questions

Answers about this ilarvo workflow and its current product boundary.

• Do we need to move every spreadsheet at once? No. A focused start can use one representative customer hierarchy and service workflow before the scope expands.
• Can ilarvo import our customer, site and asset data? Yes, when the source data is prepared in the documented standard CSV template and passes preview validation.
• What happens to service history after the import? Imported assets provide the directory structure. Their service history grows from completed work and final reports recorded in ilarvo.