Most staff training registers don’t fall apart because people don’t care.
They fall apart because spreadsheets were built for lists, not for managing competence across roles, sites, contractors, refreshers, and changing rules.
And in New Zealand, the “do we have proof?” question shows up more often than people expect:
- an incident triggers a request for training evidence
- a principal contractor asks for competence before site access
- a client review wants refresher compliance by role
- leadership asks, “Are we covered across every location?”
If your evidence is scattered across email threads, shared drives, and someone’s memory… you don’t have evidence. You have hope.
The NZ competency record test (the 4 things you must prove fast)
In New Zealand, a “good” staff training record should let you prove four things quickly:
- Who is competent right now (by role/site/task)
- What evidence supports it (assessment, sign-off, licences)
- Which version of the rule they were trained on (policy/SOP version)
- What happens next (refreshers due/overdue + exceptions)
If your spreadsheet can’t do those four things in minutes, it’s not a competency system — it’s a list.
This guide shows you what to track, how to structure it, and how to move to a no-spreadsheet setup without losing control.
Why spreadsheets fail for staff training records (especially in NZ)
Spreadsheets fail because training records are connected evidence — and spreadsheets don’t keep evidence, versioning, and audit trails together. You can force them to, but the moment your organisation grows, the system becomes fragile.
The 5 classic spreadsheet failure points
1) Version chaos
Training registers multiply. One becomes five. “Final” becomes “final_v9”. Teams stop trusting the file, so they keep their own copies. That’s not decentralisation — it’s confusion.
2) “Completed” with no proof attached
The spreadsheet shows a tick. The certificate is in a manager’s inbox. The practical sign-off is on a paper form. The photo evidence is on someone’s phone. When you need proof fast, the record doesn’t travel with the evidence.
3) No audit trail
If dates or outcomes change, you can’t reliably show who changed it and why. In high-risk work, “we think it was updated” is not a comfortable position to be in.
4) Manual reminders (and quiet expiry risk)
Refreshers rely on someone checking the sheet. If they’re busy, you drift into overdue territory. And overdue doesn’t always show up until it becomes a problem.
5) Reporting pain
The question “Who is competent right now?” becomes an afternoon of filters, pivot tables, and arguments about which tab is correct.
The real risk: you can’t prove training happened when it matters
New Zealand guidance is pretty clear: training, instruction and supervision sit inside risk management — and records are useful evidence when you need to show what occurred.
WorkSafe’s guidance on providing information, training, instruction or supervision (IITS) explicitly notes that keeping records can help demonstrate what was provided and support ongoing management (including refreshers).
And in some areas, record-keeping is more than “useful”. WorkSafe’s hazardous substances guidance states you must keep a record of training and instruction, and make it available to inspectors or compliance certifiers.
So the practical question isn’t “Do we like spreadsheets?” It’s:
Could you export credible training + competency evidence quickly — without scrambling?
Quick answers (NZ) — before we go deeper
Q: Do I legally need training records in NZ?
A: Not in every case — but WorkSafe notes records are useful evidence, and some areas (like hazardous substances) have explicit record-keeping requirements.
Q: What’s the minimum you should track?
A: Training completion + competency outcome + evidence + refresher rules + policy version.
Q: What’s the fastest way to move off spreadsheets?
A: Define competencies by role, build role-based pathways, capture evidence inside the record, and automate refreshers and reporting.
What NZ workplaces actually need to track (the “competency record” model)
A competency record is a connected chain:
Role → risk → requirement → training → competence outcome → evidence → refresher rules → exceptions
If you track only “training completed”, you’ll constantly struggle to answer the bigger question: “Are they competent today?”
The competency record framework (table)
| Record element | What to capture | Why it matters for audits / due diligence |
|---|---|---|
| Training completion | course/module, date, method, site | proves the learning occurred |
| Competency outcome | pass/fail, score, supervisor sign-off | proves capability, not attendance |
| Evidence | certificates, licences, uploads, observations | makes proof portable and exportable |
| Role + risk link | role/site + why required | shows the requirement is risk-based |
| Version control | policy/SOP version trained on | proves training was current to the rule |
| Refreshers | expiry + next due date + cadence | prevents silent risk drift |
| Exceptions | reason + interim control + closure | demonstrates governance when overdue |
Now let’s break those down into practical fields.
Training completion (course/module, date, delivery method)
A training completion record should be specific enough to stand alone. Capture:
- training item name (course/module/topic)
- completion date
- delivery method (online, classroom, toolbox talk, on-the-job)
- site/location (when risk varies by location)
- facilitator/provider (if relevant)
Competency outcome (pass/fail, score, sign-off, observed competence)
Competency is the outcome you can defend. Depending on the task, capture:
- assessment result (pass/fail, score)
- practical sign-off (observed competence)
- licence/ticket verification (and expiry date)
- supervisor declaration (who signed, when)
If it’s high-risk, a “tick” without an outcome is a weak record.
Role + risk linkage (why this person needs this training)
Your strongest training records explain “why”. Include:
- role/position
- team/site (where relevant)
- risk/hazard controlled by the training
- trigger (internal SOP, client requirement, legal duty, prequal)
This is what turns a training register into a defensible system.
Evidence attachments (licences, photos, documents, observations)
Evidence should live with the record, not in someone’s inbox. Examples:
- certificates, tickets, licences
- practical observation forms
- signed acknowledgements (for key policies)
- photos or supporting documents (where appropriate)
If evidence is separated, retrieval becomes a scavenger hunt.
Version control (which policy/procedure version they were trained on)
Rules change. Procedures change. Your records must keep up. Track:
- policy/SOP name
- version number or effective date
- version trained/acknowledged at the time
- current version link (for re-training triggers)
If you want a deeper guide on policy versioning and acknowledgements, this is relevant. See Compliance policies
Refresher rules + expiry dates (automatic due/overdue)
Refreshers are where spreadsheets quietly fail. For every requirement, define:
- cadence (e.g., 12/24/36 months)
- due date logic (from completion date vs expiry date)
- reminders (30/14/7 days)
- escalation path (learner → supervisor → ops)
The goal isn’t “remind harder”. The goal is build a system where overdue is visible early.
Exceptions + remediation (what happened when someone missed training)
Overdues happen. The difference between mature and messy is whether you can show control.
Track:
- reason (leave, role change, site shutdown, operational disruption)
- interim control (restricted duties, extra supervision, reassignment)
- remediation plan + completion date
- closure confirmation
This is often what auditors and clients look for when something is overdue: “What did you do about it?”
NZ context: duties, evidence, and what inspectors/auditors look for
In NZ, training and instruction sit inside your duty to manage risk. You don’t need to be a lawyer to understand the expectation: people must have what they need to work safely.
HSWA: duty includes providing training/instruction/supervision
HSWA’s primary duty of care includes the requirement to provide information, training, instruction, or supervision necessary to protect people from risks.
So even when “record-keeping” isn’t explicitly mandated in your scenario, training evidence is part of how you demonstrate due diligence.
WorkSafe NZ: why keeping records still protects you
WorkSafe’s IITS guidance makes two practical points that matter for record systems:
- training/instruction/supervision must be suitable and adequate
- records can help show what was provided and support ongoing management
Industry expectations (principal contractors, client audits, prequals)
A lot of “audits” aren’t WorkSafe. They’re commercial. Common examples:
- principal contractors verifying competency before site access
- clients requesting refresher compliance evidence
- supplier governance checks
- prequalification reviews (where evidence and expiry dates matter)
This is why your records must answer: who is competent today, not just “who completed a course last year”.
The “no-spreadsheet” system: how to track competency properly
A no-spreadsheet system is not about buying software first. It’s about designing your model first. Then you choose a platform (or process) that supports it.
Step 1 — Define competency by role (and link it to risk)
Start with roles, not courses.
Pick your top 10–20 roles (or your highest-risk roles) and define:
- critical tasks performed
- key hazards/risks
- what “competent” means (knowledge + practical performance)
- what evidence is required (assessment, sign-off, licence)
This becomes your training matrix by role, but designed for proof — not admin.
Step 2 — Build training pathways by role/site/team
Pathways reduce human error. Instead of enrolling people manually, build pathways like:
- New starter induction (site + culture + baseline safety)
- Role pathway (SOPs, systems, equipment)
- High-risk controls pathway (where relevant)
- Refresher pathway (auto rules)
When roles change, the pathway changes — and your records stay aligned.
If you’re mapping this transition from manual to structured training, see
Implement online compliance training
Step 3 — Capture competence inside the record (not in email threads)
Make a clear decision: where does competence evidence live?
Options that work well:
- online assessment results recorded automatically
- supervisor sign-offs captured via a form (mobile-friendly helps)
- licence uploads attached to the person’s record
- on-the-job tasks with evidence upload + reviewer confirmation
The rule: if evidence lives in email threads, your system will always be fragile.
Step 4 — Automate refreshers and overdue workflows
Automation is your safety net. Build:
- due dates generated from defined rules
- reminders sent automatically
- escalation to supervisors/managers
- exception tracking (with interim controls)
This is where organisations feel the biggest shift: less chasing, more visibility.
Step 5 — Export audit-ready reporting in minutes
Your reporting must answer — without manual cleanup:
- who is competent now (by role/site/task)
- who is overdue (and what the exposure is)
- who completed training but lacks evidence/sign-off
- which policy version was acknowledged
A good system doesn’t just store data. It produces answers.
What to look for in staff training records / competency tracking software (NZ checklist)
The best platform is the one that helps you prove competency quickly — and keeps records current when things change.
Here’s what matters in practice.
Role-based enrolments + automation
Look for:
- enrolment by role/site/team
- pathway-based onboarding
- role-change workflows (auto add/remove requirements)
- contractor/casual controls (access windows, expiry enforcement)
Evidence capture (uploads, sign-offs, observations)
Look for:
- uploads attached to the individual record (not “somewhere else”)
- supervisor sign-off workflows
- evidence from in-person and on-the-job activities
- clear visibility of “completed but not signed off”
Reporting that answers “who is competent right now?”
Ask for reporting that can filter:
- competent / not yet competent / expired
- missing evidence / missing sign-off
- by role, site, team, manager
- drill-down into the evidence
If a platform only shows completions, it won’t solve your real problem.
Audit trail + versioning
Ask directly:
- can I see who changed records and when?
- can I link training to policy/SOP versions?
- can I reassign training when a version changes?
Integrations or clean imports (HRIS, payroll, identity)
Even without full integrations, you need clean imports.
For a practical view of what data belongs in an HRIS versus an LMS, see:
HRIS vs LMS
Quick templates readers can copy (even before you buy software)
If you’re not ready to change platforms yet, you can still upgrade your spreadsheet model so it migrates cleanly later.
Minimum viable training register fields (10–15 columns)
Use this structure:
- Person (name)
- Employee/contractor ID
- Role
- Site/location
- Competency item (not just “course”)
- Why required (risk/client/legal/internal)
- Training method (online/classroom/on-job)
- Completion date
- Outcome (pass/fail/score)
- Practical sign-off required (Y/N)
- Signed off by + date
- Evidence link/location (stable link)
- Expiry date (if relevant)
- Next due date
- Exceptions/remediation notes
Tip: If you do nothing else, add columns 6, 9, 11, 12, and 14. Those are the difference between “a list” and “defensible proof.”
Competency sign-off template (supervisor observation)
Copy/paste format:
- Worker name + role + site
- Task observed (specific)
- Criteria (3–5 bullets):
- performed steps in correct order
- used controls/PPE correctly
- identified hazards and responded appropriately
- followed SOP version X
- Outcome: Competent / Not yet competent
- Notes + remediation actions
- Supervisor name + position + date
- Next review date (if required)
Refresher cadence rules (examples by training type)
Examples (adjust for your risk profile):
- high-risk tasks: 12 months
- licences/tickets: aligned to expiry date
- critical SOPs: refresh on version change + periodic review (e.g., 24 months)
- low-risk policies: version change only, or 24–36 months
The important part isn’t the cadence — it’s having a defined rule you can explain and automate.
“Audit pack” export structure (what to export)
When someone asks for proof, you want a consistent pack:
01_Scope (site/team/time period)
02_Training_Records (by role/site)
03_Competence_Evidence (sign-offs/licences)
04_Policy_Versions (register + current versions)
05_Signoffs (acknowledgements)
06_Refreshers (due/overdue)
07_Exceptions (remediation + closure)
This structure is simple, repeatable, and defensible.
Are your training records audit-ready?
If you want to sanity-check your current staff training records in NZ, run this quick test using one high-risk role:
- Can you show why each training item is required?
- Can you show competency evidence (not just completion)?
- Can you show policy versions and acknowledgements?
- Can you export it in under 15 minutes?
If the answer is “not yet,” book a demo of Tribal Habits and we’ll walk through an audit-pack workflow using your real scenarios (roles, sites, contractors, refreshers) — so you can see what “clean proof” looks like in practice.
FAQ: Staff Training Records NZ: Track Skills Without Spreadsheets
What’s the difference between training records and competency records?
Training records show learning activity (who did what, when). Competency records show the outcome (pass, sign-off, licence) and keep the evidence attached — so you can confidently answer “Are they competent right now?”
Do NZ businesses have to keep training records?
Not in every situation — but WorkSafe notes records are useful evidence for showing what occurred and managing ongoing training needs. And for hazardous substances, WorkSafe states you must keep a record of training and instruction and make it available to inspectors/compliance certifiers.
How do I track contractors and casuals?
Track them by task exposure and site access requirements: role/site, required competencies, evidence, and due dates. The record model is the same — you may simply enforce different access windows or refresher rules.
What evidence should sit inside each competency record?
For higher-risk tasks: assessment results, practical sign-offs, licence/ticket copies, and any observations required by your process. For low-risk policies, an acknowledgement plus version control may be sufficient.
How often should refresher training run?
Use risk-based rules: high-risk tasks more frequently (often annually), tickets aligned to expiry, SOP refresh on version change, and periodic reviews for stable low-risk topics. What matters most is consistency and visibility.
What does “audit-ready reporting” actually mean?
It means you can export a clear view of competence by role/site — including evidence, versions, and overdue/exception handling — without manual spreadsheet cleanup.
What should be included in a staff training register in NZ?
At minimum: role, requirement (why), completion date, outcome, evidence, version trained on, and next due date. If you can’t show those, you’re not really tracking competency.
How do I move off spreadsheets without losing historical data?
Start by upgrading your columns to the competency model, then migrate in phases: highest-risk roles first, then expand. Keep evidence links stable, and don’t attempt a “perfect” migration before you’ve defined your role requirements.
This information is general in nature and doesn’t constitute legal or compliance advice. Requirements vary by region, sector and organisation, so we’d always recommend checking with your regulator or professional adviser before relying on it.
Further reading
- Training Software for New Zealand Organisations: Compliance, Records & Reporting
- Going Beyond Spreadsheets in Training Compliance
- What Regulators Expect From Your Training Records
- Free Compliance Training Framework Checklist
- LMS for Compliance Training: Keeping Teams Certified
- Does the LMS Give You Clear, Actionable Reporting – or Just Completion Ticks?
- What LMS Reporting Should Actually Look Like
- Online Compliance Training – The Ultimate Guide
- Audit Proof Training: Prove Compliance in Minutes
- Health & Safety Training Software NZ: What to Track
