Equipment Inspections

The Equipment Inspections register logs the result of every inspection carried out on a machine, ladder, or other piece of equipment, and when that asset's next inspection is due.

Equipment that fails an inspection but keeps getting used because the failed result lives only in a paper checklist is a real hazard, not a paperwork gap. Recording every inspection as its own record, with a clear pass/fail result and the asset it was for, keeps a full history per asset rather than only the most recent check.

Each inspection record captures the asset, its type (Machine, Ladder, or Equipment), when it was last inspected, when the next inspection is due, the result (pass or fail), and who inspected it. There's no separate "asset register" distinct from the inspection log — each record is one inspection event tied to a named asset.

The list page shows every inspection with its result and next-due date, filterable and sortable by result or next-due date. The detail page shows the full record; create and edit forms share the same fields.

• Asset — required. The name or identifier of the machine, ladder, or equipment inspected.
• Asset type — required. One of Machine, Ladder, Equipment.
• Last inspection — required date.
• Next due — required date. When this asset is next due for inspection.
• Result — required. Pass or fail.
• Inspector — required. Who carried out the inspection.

Creating or editing an inspection record validates every field as required. There's no separate action to "retire" or "take out of service" an asset that fails — a failed result is simply the value of the Result field on that inspection's record.

A failed result has no automated downstream effect elsewhere in the product in the current version — it's a value on the record, meant to be visible to whoever reviews the register, not a trigger that blocks other actions (such as issuing a Permit to Work that would use the asset).

Can the same asset have more than one inspection record? Yes — each inspection is its own record, so an asset that's inspected repeatedly over time will have one record per inspection, giving a full history rather than a single "current status" field.