An asset's repair history
When you link a work order to an asset, Habitia builds a repair history on that asset automatically. Over time this becomes the paper trail behind the lifecycle alerts — and the answer to “has this fridge been trouble before?”
Linking a work order to an asset
Any work order can point at a specific asset. On the Add / Edit work order form, after you choose the property (and optionally the unit and room), pick the item from the Asset dropdown — the refrigerator in unit 101, the water heater, the AC condenser. See Logging a work order for the full form.
The same picker is on the tenant’s maintenance request form, so a tenant who reports “the provided fridge stopped cooling” can choose the fridge itself instead of only describing it in the notes.
Tip: You can attach the asset later too. Open the work order, click Edit, and set the Asset field — useful when a request comes in without one.
The Work Orders tab on an asset
Open any asset (from Assets in the left sidebar, or a property’s Assets tab) and select the Work Orders tab. You’ll see every work order that references this asset — newest first — with its title, category, reported date, and status. Click any row to jump to the work order.
This is the quickest way to answer “how many times have we worked on this?” without hunting through the global work-order list.
Completed repairs land on the asset’s timeline
When you mark a work order Completed and it’s linked to an asset, Habitia automatically adds a repaired entry to that asset’s Event History. The entry carries the completion date, the vendor, the cost, and the resolution notes — you don’t log it twice.
This is what powers the repeat-failure trigger in Lifecycle rules: the engine counts those repair events to decide when an asset is breaking too often. It also feeds the repair-cost picture on the asset’s Lifecycle panel.
Habitia only logs one event per work order, so re-saving or reopening and re-completing a work order won’t create duplicates.
Why it’s worth linking
A loose work order (“fridge repair, unit 101”) is a one-off note. A linked one becomes part of the asset’s record, which means:
- The asset’s Work Orders tab and Event History stay complete on their own.
- The repeat-failure and repair-cost lifecycle triggers actually have data to work with — without linked repairs, those rules stay silent.
- When the fridge fails for the third time in a year, the alert is there to tell you it’s cheaper to replace than to keep fixing.
What’s next
- Reading an asset’s lifecycle — the stage, signals, and recommendation on each asset.
- Lifecycle rules — the per-category thresholds these repairs feed into.
- Logging a work order — the full work-order form and how costs are recorded.