Work Orders and Preventive Maintenance

How work flows through Rivolq

Work orders are the execution layer of the platform. They track work from request to completion.

A strong work-order process usually moves through these stages:

1. 01issue is reported
2. 02work order is created or approved
3. 03assignment and priority are clarified
4. 04work is completed and documented
5. 05the history remains attached to the asset for future review

What makes a good work order

Include enough detail that another technician or supervisor can understand the issue without guessing.

A strong work order usually includes:

• clear title
• facility and asset
• meaningful priority
• symptom or problem statement
• notes, attachments, or follow-up findings

How PM schedules fit in

Preventive maintenance sits above reactive work.

A PM schedule defines:

• what recurring work should happen
• how often it should happen
• which asset or facility it belongs to
• whether it is time-based or meter-based

PM setup guidance

Start with assets that are:

• critical to operations
• costly to replace
• failure-prone
• heavily regulated

How to keep work history useful

Completed work should stay attached to the right asset. That is what turns the work board into useful long-term operational memory.

That history later supports:

• reporting
• downtime review
• recurring failure analysis
• vendor review
• replacement and capital decisions

Healthy operating pattern

• critical assets have PM coverage
• exception work is handled through standard work orders
• backlog is reviewed routinely
• work is closed with enough context to be useful later
• PM generation is monitored so recurring work is actually being created