Every compliance platform on the market treats training tracking as a feature — one checkbox in a list of twenty. We looked at how Victorian councils actually work and realised the training matrix isn’t a feature. It’s the foundation.
The spreadsheet problem
When we sat down with compliance officers across a dozen councils, the same story emerged. Training records lived in Excel. Certificate expiry dates were tracked by hand. When WorkSafe audited, someone spent two weeks pulling evidence from six departments into a single pack.
The spreadsheet wasn’t the problem. The problem was that training data was disconnected from everything else — incidents, inspections, SWMS, document control. A worker’s certification status existed in isolation.
Five requirement types
Most systems model training as a binary: required or not. But Victorian compliance is more nuanced. We identified five distinct requirement types:
- Mandatory — legally required for the position
- Preferred — recommended but not legally mandated
- Competency-gated — must hold before performing specific tasks
- Recurring — must be renewed on a schedule
- Event-triggered — required after incidents or role changes
Each type has different expiry logic, different alerting rules, and different audit implications. Building this into the data model from day one meant every other module could reference it cleanly.
The backbone architecture
The training matrix became the backbone. When the incident management module needs to show what certifications a worker held at the time of an incident — it queries the matrix. When SWMS sign-on needs to verify operator competency — it checks the matrix. When the compliance engine calculates a department’s score — it aggregates from the matrix.
This wasn’t an accident. It was the first architectural decision we made, and every module since has validated it. When we built incident management with competency snapshots, the matrix provided the evidence layer. When the Compliance Horizon needed to project future scores, it drew from matrix expiry data.
What this means for councils
A council using Lattice Look doesn’t manage training in one system and compliance in another. The training matrix powers the compliance score, the gap analysis, the benchmarking, the incident reports, and the audit packs. One source of truth. No reconciliation.
That’s why we built it from scratch — because retrofitting a connected architecture onto a feature checklist doesn’t work. You have to start with the connection.