• The trusted Australian LMS. Build your own learning. Only pay for active users!
STORE

|

LOGIN

Contact Sales

DEMO

Health & Safety Training Software NZ: What to Track

Table of Contents

Health & safety training software NZ: the short answer (copy/paste summary)

If you want to stay audit-ready in New Zealand, your health & safety training software (or training register) should track three layers of evidence:

  1. Completion — who did what training, when, and on which site/role requirement
  2. Competence — evidence of understanding (quiz results) and ability (practical sign-offs) for higher-risk tasks
  3. Currency — refreshers, licence/ticket expiries, and version control so you can show what someone was trained on at the time

Auditors and inspectors typically look for proof that you can answer these questions fast:

  • Who is compliant for X (by role and site) right now?
  • Show me one worker’s full training/competency history
  • What’s overdue or expiring in the next 30/60/90 days?
  • What version of the training did they complete, and who approved it?

WorkSafe NZ guidance reinforces that PCBUs must provide suitable information, training, instruction, or supervision for workers — and that records are useful evidence of what you’ve done.
External source:

Use the tracking checklist + Audit Pack template in this article to set up your system (or sanity-check your current one).

Health & Safety Training Software NZ: What to Track

Why “we do training” isn’t enough in NZ (you need evidence)

Most organisations don’t skip training on purpose. The issue is that evidence gets scattered:

  • a spreadsheet for inductions
  • emails for contractor sign-offs
  • folders of PDFs for certificates
  • a separate register for licences/tickets
  • and a “we’ll update it later” approach to versions

That works — right up until you’re under pressure.

The real risk: audits, incidents, tenders, contractor management, client compliance

You’ll be asked for training evidence when:

  • an incident triggers internal and external scrutiny
  • a WorkSafe interaction requires you to demonstrate training/instruction/supervision
  • a customer asks for proof before approving you as a supplier
  • a principal contractor requires site induction and competency evidence
  • a prequal process asks for “training registers” and “competency records”
  • leadership wants assurance that critical risk controls are actually in place

The requirement isn’t “have training somewhere.” It’s produce defensible evidence quickly.

WorkSafe’s expectation: suitable training/instruction/supervision (and why records matter)

WorkSafe NZ’s guidance on providing information, training, instruction, or supervision reinforces that PCBUs must ensure what’s provided is suitable and adequate for the work and risk — and that keeping records is useful evidence.

That framing matters because it shifts the standard from:

  • “we ran a module”
    to
  • “we trained the right people, on the right hazards/tasks, and can show it.”

What auditors and inspectors typically want to see (in plain English)

Most audit requests boil down to three proof types.

1) Evidence of training completed (who, what, when)

This is your baseline:

  • learner identity
  • training item name
  • assigned date + due date
  • completion status
  • completion date/time
  • site and role context (why that person had to do it)

If you can’t answer who did what, when, everything else becomes difficult.

2) Evidence of competence (not just attendance)

For low-risk content, completion is often acceptable.

For higher-risk tasks, the question becomes: did they understand it and can they do it safely? Evidence typically includes:

  • quiz score and pass mark (knowledge check)
  • practical sign-off (supervisor validation)
  • uploaded evidence (photo/video/doc) where appropriate
  • a record of reassessment if someone failed

ACC’s Accredited Employers Programme audit guidelines provide examples of competency evidence such as training records, certificates, and practical demonstrations (and signed evidence of achievement).

3) Evidence you manage refreshers & currency

This is where spreadsheets usually collapse.

Auditors want to see you can manage:

  • refreshers tied to completion dates
  • licence/ticket expiry dates
  • upcoming due items (30/60/90 days)
  • overdue items + documented exceptions
  • interim controls when someone can’t complete on time (supervision, restricted duties, reassignment)

4) Evidence of site-specific and role-specific training

The common failure mode: a generic module that doesn’t reflect:

  • the hazards of a specific site
  • the risk level of a specific role
  • contractor access rules
  • site emergency procedures
  • controlled work zones or local plant/equipment

In audits, “everyone completed induction” is less useful than “everyone at Site A completed the Site A induction and role pathway.”

The H&S training tracking checklist (what to track in software)

If you’re setting up health & safety training software NZ (or rebuilding your training register), use this as the core data model.

Learner identity + role + worksite (the “who”)

Track:

  • full name
  • unique ID (employee ID or payroll ID)
  • employment type (employee / contractor / labour-hire / volunteer)
  • role/position
  • team/department
  • worksite (and ideally site group/region)
  • manager/supervisor

Why it matters: almost all audit questions are filtered by site and role.

Training requirement mapping (the “why”)

Track why the training exists:

  • hazard-based requirement (e.g., hazardous substances handling)
  • role-based requirement (e.g., forklift operator pathway)
  • site-based requirement (e.g., Auckland Depot induction)
  • customer/principal requirement (e.g., prequal training evidence)
  • internal procedure requirement (e.g., SOP training)

This is the difference between “we trained them” and “we trained them because this risk exists.”

Course/module version control (what they were trained on)

This is one of the most important audit-protection features.

Track:

  • module version (v1.0 / v1.1 / v2.0)
  • effective date (published date)
  • owner
  • approver
  • change log summary (1–2 lines)
  • superseded version reference

Why it matters: when something goes wrong, the question is often what they were trained on at the time — not what the latest module says today.

Completion data (assigned, due, completed, attempts)

Track:

  • assigned date
  • due date
  • completion date/time
  • status (not started / in progress / completed / failed / expired)
  • number of attempts
  • time spent (optional but useful)

Assessment evidence (score, pass mark, question set)

Track:

  • quiz score
  • pass mark
  • attempt history
  • question bank or randomisation logic (if used)
  • “achieved/not achieved” result label

This helps evidence “understanding,” not just “attendance.”

Practical competency sign-offs (supervisor validation + attachments)

For higher-risk tasks, track:

  • who assessed/signed off
  • date of sign-off
  • competency checklist used
  • evidence uploads (photo/video/doc where relevant)
  • reassessment date (if required)

This aligns well with competence evidence examples referenced in ACC audit guidelines.

Licences, tickets, certifications + expiry dates

Track:

  • licence/ticket type
  • licence number (if relevant)
  • issue date
  • expiry date
  • evidence attachment
  • renewal workflow (assigned training + reminder cadence)

Refresher scheduling + automated reminders

Track:

  • refresher interval (annual / 2-yearly / risk-based)
  • trigger type (from completion date / from expiry date / from hire date)
  • reminder schedule (e.g., 30/14/7 days)
  • escalation (manager notified if overdue)

Induction + site onboarding records (including contractors)

Track:

  • site induction module completion
  • contractor company (for non-employees)
  • host/sponsor/manager
  • acknowledgement of site rules, PPE, emergency procedures
  • project induction (if relevant)

WorkSafe’s training/instruction/supervision guidance is often referenced when demonstrating how PCBUs ensured people were informed and instructed for the risks.

Hazardous substances training records (where expectations are more explicit)

Where hazardous substances are involved, WorkSafe notes businesses must ensure workers have the knowledge and practical experience to safely use, handle, manufacture, and store hazardous substances.

Track (where relevant):

  • substance handling role scope (use/decant/store/dispose)
  • SDS access/acknowledgement
  • spill/exposure response training
  • PPE competence (fit/use)
  • supervisor sign-off for higher-risk activities

Training exceptions (overdue + why + interim controls)

In real operations, “overdue” happens. What matters is whether it’s controlled.

Track:

  • reason (leave, injury, redeployed, access issue, etc.)
  • interim control (supervision, restricted duty, reassignment)
  • next review date
  • approver

This is one of the fastest ways to demonstrate maturity.

raining exceptions (overdue + why + interim controls)

Structured data: copy/paste “tracking fields” table

Use this table to review your current system or to brief a vendor.

Field categoryWhat to captureAudit question it answers
Identitylearner ID, role, site, employment type, manager“Who is this person and where do they work?”
Requirement mappinghazard/role/site/customer requirement tags“Why did they need this training?”
Version controlversion, effective date, owner, approver, change log“What content did they complete at the time?”
Completionassigned/due/completed dates, status, attempts“Was it done, and was it managed?”
Assessmentscore, pass mark, attempts, achieved status“Did they understand it?”
Competencepractical sign-off, assessor, checklist, evidence“Can they do it safely?”
Currencyrefresher intervals, expiry dates, reminders“How do you keep it current?”
Exceptionsoverdue reason, interim controls, review date“What happens when someone isn’t current?”

Reporting views that make audits fast

If you’re picking or configuring a system, these are the reporting views that reduce audit work from days to minutes.

“Show me everyone compliant for X” report

This report should be filterable by:

  • training item (e.g., Confined Space Awareness)
  • site (e.g., Christchurch workshop)
  • role (e.g., maintenance team)
  • employment type (employee/contractor)
  • status (compliant / overdue / expiring soon)

Output goal: one list you can export and explain.

“Show me one worker’s complete training history” report

This is your incident-ready view. It should show:

  • all completed training with dates
  • versions completed
  • quiz results
  • practical sign-offs and attachments
  • current licences/tickets and expiry dates
  • overdue items + documented exceptions/interim controls

“What’s overdue in the next 30/60/90 days” report

This helps you avoid “audit panic” by staying ahead of expiry.

Best practice is to split this report into:

  • expiring licences/tickets
  • refreshers due
  • site inductions due
  • high-risk competency reassessments due

Export formats + audit pack creation (PDF/CSV)

Exports should be:

  • consistent column structure
  • time-stamped (export date/time)
  • filterable
  • easy to bundle into one “Audit Pack” folder

Common gaps that fail audits (and how software prevents them)

These are the patterns that repeatedly cause evidence problems.

Training that isn’t mapped to hazards/roles

Symptom: everyone gets the same module, regardless of work.

Fix: role and site-based pathways, tied to hazard controls and procedures.

No evidence of understanding/competence

Symptom: completions exist, but nothing shows learning or capability.

Fix: quizzes with pass marks + practical sign-offs + evidence uploads where appropriate.

ACC audit guidance includes examples of competency evidence expectations (records, certificates, practical demonstration).

Refreshers not managed

Symptom: refreshers are “supposed” to happen, but no triggers exist.

Fix: automated refresher scheduling + reminders + escalation.

Contractor / multi-site chaos

Symptom: contractor training evidence is scattered across emails and portals.

Fix: contractor enrolment + site induction records + site-filtered reporting.

The “old module” problem (no version trail)

Symptom: training content changes, but you can’t prove which version people did.

Fix: version control + approval trail + completion by version.

What to look for in Health & Safety training software NZ (buying criteria)

This section stays intentionally practical (and non-salesy): these are the capabilities that reduce risk and admin.

1) Assignment by role/site + automation

Look for:

  • role and site-based enrolment rules
  • automatic due dates
  • reminder automation
  • manager escalation workflows
  • fast contractor onboarding

2) Evidence quality (assessment + competency + attachments)

Minimum evidence features:

  • assessments with pass marks
  • attempts tracking
  • competency sign-offs
  • evidence upload support
  • certificate/licence register with expiries

3) Reporting speed (filters, dashboards, one-click exports)

Look for:

  • saved report views
  • drill-down by site/role/contractor
  • one-click exports
  • dashboards for expiring and overdue items

4) Data hygiene (HRIS/payroll/SSO or clean imports)

Most evidence breakdowns happen because user data is messy:

  • duplicate accounts
  • wrong roles/sites
  • offboarded workers still active
  • contractors recreated repeatedly

Integrations help — but even without them, clean import/export workflows matter.

5) NZ context + support + privacy expectations

Practical considerations NZ teams often care about:

  • local support response time
  • privacy expectations and data handling transparency
  • content relevance (NZ terms, NZ hazards, NZ operating realities)

How Tribal Habits supports audit-ready H&S training in NZ (positioning)

If you’re comparing platforms, here’s how Tribal Habits aligns to the evidence model above.

Build and launch faster with editable modules + pathways

Teams can start with editable training modules and tailor them to:

  • your hazards and procedures
  • your sites
  • your role pathways
  • your contractor induction requirements

Track completion, understanding, and competency

Tribal Habits supports evidence layers including:

  • completion data (assigned/due/completed/status)
  • knowledge checks (scores, pass marks, attempts)
  • practical sign-offs + attachments (where required)
  • licence/ticket expiry tracking + reminders

Reporting dashboards built for “prove it” moments

Audit evidence becomes easier when you can quickly produce:

  • “compliant for X at Site Y” views
  • a single worker’s full record
  • 30/60/90 day expiry and overdue reports
  • exportable evidence packs

Optional AI support to speed up training creation

Where you’re building custom content from SOPs or policies, AI assistance can help generate drafts and structure — while your team still controls approvals and versioning.

Further Reading:

Compliance expectations shift — and you need training that keeps pace​

Quick-start “Audit Pack” template (copy/paste)

If you want a repeatable process, use this as your standard pack.

The 10 items to export before an audit

  1. Training matrix (role → required training) by site
  2. Compliance-by-training report (“Show me everyone compliant for X”)
  3. Current overdue training report
  4. Expiring in 30/60/90 days report
  5. Individual training histories (sample set across roles/sites)
  6. Assessment results export for key high-risk modules
  7. Practical sign-off list + evidence attachments where applicable
  8. Licence/ticket register with expiry dates + evidence
  9. Contractor induction completion report for active sites/projects
  10. Version register (module version, effective date, owner/approver, change log)

The 5 screenshots to capture (dashboards/views)

  1. Overdue dashboard (showing escalation/ownership)
  2. Expiring soon dashboard (30/60/90)
  3. A saved “compliant for X” filtered view
  4. A learner profile showing history + evidence
  5. A module/version screen showing effective date and approval

The 3 policies/procedures to attach alongside records

  1. Training & competency procedure (requirements, assessment, refreshers)
  2. Contractor induction procedure (onboarding and evidence)
  3. Document/version control procedure (how updates are approved and rolled out)

FAQs (Health & Safety Training Records NZ)

What training records do I need to keep in NZ?

At minimum: who completed what training, when, and why it was required (role/site/hazard). For higher-risk tasks, keep competence evidence (assessments, practical sign-offs, licences/tickets). WorkSafe notes records are useful evidence of training/instruction/supervision provided.

Are training records legally required in New Zealand?

Specific recordkeeping requirements can apply in certain contexts, but broadly the duty is to ensure suitable information/training/instruction/supervision is provided. Records help demonstrate you met that duty when challenged.

How do I prove competence (not just attendance)?

Use layered evidence: quiz results with pass marks (knowledge) plus practical sign-offs and, where relevant, certificates/licences and evidence uploads (ACC audit guidance). ACC audit guidance includes examples of competency evidence such as records, certificates, and practical demonstrations.

What do auditors look for in health and safety training records NZ?

Typically: proof of completion, proof of competence for higher-risk work, refresher/expiry management, and version control showing what training content was completed at the time.

How should we track refreshers and expiries?

Track refresher intervals, expiry dates, reminders, and escalation. Also track exceptions and interim controls so overdue items are managed, not ignored.

How do we manage contractor H&S training evidence?

Track contractor identity, company, site induction completion, and any project-specific requirements. Ensure reports can be filtered by site/project and exported quickly.

What do WorkSafe inspectors ask for?

Questions often centre on whether workers received suitable information/training/instruction/supervision for the risks, and how you know it was effective. Being able to produce clear, structured records supports that.

What’s the fastest way to build an audit pack?

Use a system with role/site assignment, competence evidence capture, refresher automation, and one-click reporting exports — then follow the 10-export Audit Pack checklist above.

Is an LMS enough, or do we need extra systems?

Many organisations can cover most training evidence requirements with a well-configured training platform and clean reporting. Some environments also integrate with other risk systems — but the key is whether you can produce reliable evidence quickly.

Turn Your Next Audit Request Into a 5-Minute Export

If you’re reviewing health & safety training software in NZ and want to sanity-check whether your current setup can produce an audit pack quickly, book a demo of Tribal Habits and we’ll walk through the reporting views and export workflow using your real-world scenarios (sites, roles, contractors, refreshers).

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