Recording a breakdown for asset health

An asset's replacement recommendation (see Service contracts) is driven by how often it breaks down. To keep that count trustworthy, a breakdown is something you mark explicitly — not something Roldesk infers.

The breakdown flag

On the work-order detail page there's a "This was a breakdown" checkbox with a short hint. Tick it when the visit was a reactive repair of an asset that failed — as opposed to a scheduled maintenance visit, an install, or an inspection.

On → this work order counts toward the covered asset's breakdown history and can push it over the replacement threshold.
Off → it doesn't count against the asset's reliability, even if it was on a broken machine incidentally.

Why explicit, not inferred

We used to infer breakdowns from the work-order type (Corrective / Emergency). That turned out to be fragile:

Renaming or reconfiguring your order types silently changed historical counts.
A single visit can touch several assets — only some of them actually failed.
Not every "corrective" visit is a true failure (a tweak, a customer-caused issue, a warranty adjustment).

An explicit flag fixes all of that: the count reflects what actually happened, decided by the person who was there, and it stays stable no matter how you reorganise your order types later.

How it's set by default

When you create a work order, the flag is pre-filled from the order type (an Emergency/Corrective order starts ticked) so you're not doing extra work for the common case — but you can always override it. It's the flag, not the type, that the health score reads.

When to tick it

✅ A unit stopped working and you went out to fix it.
✅ An emergency call-out for a failure.
❌ A quarterly preventive visit.
❌ A new installation or a quote visit.
❌ A cosmetic or customer-requested tweak that wasn't a failure.

Where it shows up

Ticked breakdowns feed the asset's health check, which in turn drives the replacement recommendations in the contract monthly report and on the equipment detail page.