Asset Inspection keeps the frequency on the asset type, works out every due date from the last inspection, and puts the late ones at the top of the list.
Nothing to model, nothing to connect. Open it and start scanning.
The rulebook: inspection frequency, warning window, checklist, standard, safety-critical flag.
A scannable tag, photos, a GPS location checked against the address, site, serial and warranty.
Result, condition, checks ticked, findings, meter reading, photos, GPS and a signature.
Who inspects, how to reach them, and when their certification runs out.
Due today, due this week, never inspected, failed last check, out of service — and what to inspect next.
A printable sheet with the details, the full inspection history, and a short link back to the record.
Start with the template, then reshape it in plain English — a new asset type, a quarantined status, a second checklist. No coding required.
Try for FreeYou say it once — fire extinguishers monthly, forklifts weekly, rooftop units quarterly — and every asset of that type inherits it.
Result: change one rule and 400 due dates move with it.
A one-person workshop and a plant with a compliance auditor want very different forms. The template ships with the fields the demanding case needs, because adding a field you did not know you wanted is harder than removing one you can see.
Tap any field you do not use and choose Hide Field. It stops appearing on the form, keeps whatever was already in it, and comes back the same way.
Fields most people hide first:
Manufacturer, model and serial number
Purchase cost and warranty expiry
Meter readings for anything with an hour counter
Certifications and their expiry dates
Signatures and the printable asset report
Site, location detail and the mapped address
It is a starting point, not a finished compliance system. These are the edges you are most likely to hit — each one is a change you can ask the assistant for.
An asset works out its next due date when the asset itself is saved. Add an inspection from the asset screen and hit Save — that is one tap, and it is the tap that moves the schedule.
Inspections belong to their asset: delete the asset and its history goes with it. Export first if the record has to outlive the equipment.
An inspection does not carry a link back to its asset, so the Inspections list names each row by the tag that was scanned. Scan the tag and the history reads properly; skip it and the row says only who inspected and what they found.
For the same reason, an inspection’s own GPS stamp records where you were without measuring it against the asset. It is the asset’s photo and GPS stamp that get the distance check.
The dashboard counts what a query can answer exactly — due today, due this week, never inspected, failed last check. Overdue is a live reading, so it lives in the list (late ones first) rather than in a stored number on a card.
One interval per type. Meter readings are captured but do not drive the schedule, so "every 250 hours" is a rule you would add.
Nothing chases anyone. A date passing does not send an email or a notification — somebody has to open the app.
Each asset carries its own address. If you look after many sites, splitting Locations into a table of their own is a sensible first change.
A worker whose certification has expired is flagged, but nothing stops them being picked as the inspector.