Keep recurring equipment service connected from plan to report.

Repeated work still breaks when each visit starts from scratch.

A recurring date alone does not carry the asset history, current checklist, assigned work or completed evidence. The service team needs those records to stay connected around the equipment.

Use the current plan and due work to prepare the next service visit.

The workflow connects the maintained asset to the work the office prepares and the evidence the technician records during that visit.

• Review the maintenance plan and due work. Confirm the asset, current due date and checklist before preparing the field visit.
• Prepare the work order and visit. Choose the planned time and named field technician with the customer, site and asset context attached.
• Return evidence to the asset history. Use the completed visit for the final PDF and keep the result against the maintained equipment.

One current quarterly service requirement from plan to report.

This controlled scenario uses fictional records to demonstrate the current ilarvo workflow. It is not evidence of a customer’s completed maintenance cycle.

• Plan: Quarterly air handling service
• Due work: Air Handler 04 · 28 August 2026
• Visit: WO-2841 · Naomi King
• Final record: Service report SR-2841
• Current requirement reviewed: Asset, due date and checklist confirmed.
• Quarterly service completed: Checks, readings, photos and confirmation recorded.
• Final PDF linked to AHU-04018: Authenticated download available from the service record.

Coordinate one current service requirement across office and field.

The office reviews the due work for an air handler, prepares the visit and assigns a technician. The completed evidence and final report return to the same asset record.

• The plan and due work identify the current service requirement.
• The work order and visit make ownership and timing clear.
• The completed evidence remains usable for the next planning decision.

Grounded in the current demonstrated workflow.

This page describes maintenance plans, due work, prepared visits, completed field evidence and final reports available today.

• Your service team reviews the due work and prepares the field visit.
• The product does not decide the technical maintenance requirement.
• The controlled example demonstrates one current requirement, not an unattended end-to-end cycle.

Frequently asked questions

Answers about this ilarvo workflow and its current product boundary.

• What does ilarvo connect for recurring service work? It connects the asset, current maintenance plan, due work, prepared visit, completed field evidence, final report and usable asset history.
• Who prepares a due maintenance visit? An office user reviews the current due work, chooses the planned time and assigns the named field technician.
• Does the example prove a fully unattended maintenance cycle? No. The controlled example demonstrates one current service requirement and the supported office-to-field workflow around it.