There’s no shortage of inspection apps. Most of them do the same thing: build a checklist, assign it to an inspector, capture some photos, generate a PDF. The market treats inspections as a standalone function — isolated from training, disconnected from compliance, unlinked to incidents.
That’s the problem. An inspection that can’t tell you whether the operator was certified to use the equipment being inspected is just paperwork.
The training cross-reference
Every inspection in Lattice Look runs against the training matrix. When an inspector records an observation about a specific piece of equipment or work activity, the system automatically surfaces the operator’s certification status for that equipment type.
The inspector doesn’t need to leave the form. They don’t need to look up a separate system. The certification status — current, expired, never held — is right there in context, at the point of observation.
This changes what inspections can find. A plant inspection isn’t just “are the guards in place?” — it’s also “is the person operating this plant qualified to do so?” The two questions belong together, and separating them into different systems creates blind spots.
23 Victorian OHS requirements
Victoria’s OHS regulatory framework imposes specific inspection obligations across workplace categories. We mapped all 23 applicable regulatory requirements and built them into configurable inspection templates.
When you create a new inspection type, the relevant regulatory requirements are pre-loaded. You can add organisation-specific items on top, but the regulatory baseline is always there. This means an inspector can’t accidentally skip a requirement because the template didn’t include it.
The regulatory mapping also feeds into compliance reporting. Your compliance dashboard doesn’t just show training gaps — it shows inspection coverage against regulatory obligations.
Photo evidence and corrective actions
Every inspection item supports photo capture with GPS tagging and timestamp metadata. The photos are stored with the inspection record, not in a separate media library. When an auditor reviews an inspection, the evidence is inline — they don’t need to cross-reference a folder of images against a spreadsheet of findings.
Corrective actions are tracked as first-class objects. Each finding can generate a corrective action with an assigned owner, a due date, and automatic follow-up reminders. Overdue corrective actions surface in the compliance dashboard alongside training gaps and document review dates.
From inspections to incidents
When an inspection uncovers something serious — a near-miss, a hazard that should have been reported — the inspector can escalate directly into the incident management workflow. The inspection record becomes linked evidence on the incident, and the competency snapshot captures the state of all involved workers at that moment.
This link between inspections and incidents eliminates the gap where hazards get noted on a clipboard but never formally reported. The escalation path is one tap, not a separate form in a separate system.
The inspection data also flows into the PPE & asset management module — equipment flagged during inspections triggers review of pre-start certification gates and maintenance schedules. Everything connects back to the training matrix backbone.