The matrix is always out of date
A training matrix maintained by hand is accurate on the day it is issued and drifting by the end of the week. Nobody knows which cell is stale until an auditor points at it.
Who works here, what they are qualified to do and when they are available — held once, and checked automatically by the permit, the work order and the journey plan.
Eight tools · Shared personnel records · Feeds HSEQ, Maintenance and Logistics
Illustrative product view with sample data. Request a live walkthrough.
In field operations the cost of a stale training record is not administrative. It is a person on a job they are no longer certified for.
A training matrix maintained by hand is accurate on the day it is issued and drifting by the end of the week. Nobody knows which cell is stale until an auditor points at it.
A rope-access ticket or a medical that lapsed last month does not announce itself. It surfaces when a supervisor is standing at the worksite with a crew already mobilised.
Approvals happen in chat, balances are argued from memory, and the person planning next month’s rotation has no single place to look.
HR is not a silo here. The same record that holds a certificate is the record a permit checks before it lets someone sign.
Every employee has one record: department, job title, contract details, documents, emergency contacts and history.
Requests are raised, routed and approved in one place, and the balance updates itself.
Modules, scheduled sessions, recorded attendance, and certificates that carry an expiry date.
The matrix is a view of the underlying records, so it is current by definition.
The same chain runs for an employee and for a contractor brought in through Procurement.
Everything in the HR module, and what each part is for.
The employee register — departments, job titles, contract details, documents, emergency contacts and status.
Requests, approvals, balances and a team calendar, so absence is planned rather than discovered.
Structured roles that carry their own training requirements — change the title, and the required modules follow.
The state of competence across the organization: what is current, what expires soon, what has lapsed.
The catalogue of courses and inductions, each with a validity period and the job titles that need it.
Scheduled deliveries of a module — trainer, date, location and the people booked onto it.
People against modules in one grid, built from attendance records rather than typed in by hand.
QR-code capture for sessions and toolbox talks — people scan, and the matrix updates without a sign-in sheet.
A training record that only lives in HR is an archive. One that other modules read is a control.
Permits to work, lifting plans and risk assessments are signed by named people — and the people are the same records HR holds.
A work order goes to a technician, and that technician’s certificates and calibration competence sit on their personnel file.
Vendor personnel are tracked with the same competency requirements as employees, so a contract crew is not a blind spot.
Three very different jobs, one set of data.
Owns the personnel register, processes leave, keeps documents current and answers the audit question without a week of preparation.
Schedules sessions, records attendance by QR scan, and watches the expiry list rather than rebuilding a matrix each month.
Checks before mobilising a crew whether every person on it is current, and sees who is on leave next rotation.
The module ships with sensible defaults, and an administrator can reshape most of it without contacting us.
| Setting | Value |
|---|---|
| Personnel visible to | Own department |
| Leave approval | Line manager |
| Certificate expiry warning | 60 days |
| Attendance capture | QR code |
| Contractor personnel | Included in matrix |