Employee Training Records NZ: Template + Simple System

You know the moment.

A customer asks for proof your team is trained. A manager needs to confirm who can operate a piece of equipment. A refresher expires quietly. An incident happens and suddenly it’s not “did we train them?” — it’s “can we prove it, quickly, with the right context?”

That’s where most training record systems fall over.

Not because people don’t care — but because the “system” is usually a spreadsheet that:

• drifts into multiple versions
• loses links to evidence
• has no clear owner
• doesn’t handle contractors or site differences
• turns refreshers into a monthly panic

This guide gives you two things you can use immediately:

1. a copy/paste-ready training records template (4 tabs)
2. a simple, maintainable workflow that keeps records accurate without turning HR or H&S into full-time administrators

It’s grounded in the NZ reality: while records aren’t always explicitly required, WorkSafe is clear that PCBUs must ensure, so far as is reasonably practicable, that the information/training/instruction/supervision provided is suitable and adequate, and records are useful evidence of what occurred.

In some areas — like hazardous substances — record-keeping is explicitly required and must be available to inspectors or compliance certifiers.

At a glance: Employee training records NZ (what “good” includes)

If you want employee training records that hold up in NZ (audits, incidents, tender checks), your record needs to capture four things:

• Training delivered (what, when, to whom, version trained to)
• Competency verified (who confirmed they can do it safely, and how)
• Evidence retained (where the proof lives — not “in someone’s inbox”)
• Refreshers managed (expiry rules + next due date + reminders)

The minimum fields to track (for most NZ organisations):

1. Worker + role + site/team
2. Training item + version/policy reference
3. Completion date + status
4. Verifier (where required)
5. Evidence link (where required)
6. Expiry/refresher date + next due date

Why training records matter in NZ (even when they feel optional)

The real risk isn’t “no training” — it’s “can’t prove it”

Most organisations do some training. The risk is that:

• it’s inconsistent across sites
• it’s not tied to a role or hazard
• it’s not tracked properly
• competency is assumed after completion
• refreshers lapse unnoticed

When you can’t prove training happened (and was relevant), you’re exposed in audits, investigations, tenders, and even internal governance reviews.

WorkSafe’s view: training must be suitable and adequate — and records are strong evidence

WorkSafe’s guidance focuses on ensuring workers get information, training, instruction and supervision that is suitable and adequate (so far as reasonably practicable). The guidance also reinforces practical thinking: when training happens, how it’s delivered, and how you’ll supervise until people can demonstrate competence. In other words: even when record-keeping isn’t spelled out as mandatory for every situation, good records are how you show you met your duty.

What “good” employee training records look like (the NZ version)

Training ≠ competency (your record needs to show both)

A completion tick is not the same as “this person can do the task safely, to standard, at this site.”

So “good” records usually separate:

• training completion (course/module/event)
• competency verification (observation, checklist, sign-off, assessment, licence)

If you blend those together, you end up either over-trusting completions or over-administering everything.

The minimum data fields most teams forget

If you want training records you can actually defend, these fields are the backbone:

• Person (name + unique identifier)
• Role + site/team (context matters)
• Training item (what it was)
• Version / policy reference (what rules they were trained to)
• Completion date
• Verifier (if required)
• Evidence link (where proof lives)
• Expiry / refresher date
• Notes / exceptions (why it’s different)

If you capture those consistently, you’ve solved 80% of the chaos.

Quick decision guide: when to record training and keep evidence

Use this simple rule-of-thumb to decide how heavy your record needs to be:

Low-risk, low-consequence tasks

• Record completion
• Evidence optional (usually not needed)
• Refreshers triggered by policy change or cadence (e.g., 2–3 years)

Medium-risk tasks (customer, safety, regulatory exposure)

• Record completion + version trained to
• Record refresher due dates
• Evidence recommended (e.g., sign-off, short quiz result, attendance)

High-risk tasks (serious harm potential or regulated work)

• Record completion + competency verification
• Keep evidence (sign-off/checklist/licence/cert)
• Refreshers managed proactively

Example: hazardous substances and other critical safety tasks often require stronger evidence and record-keeping.

The NZ legal/guidance basics (plain English, non-lawyer)

Duty to provide training, instruction and supervision (context)

Under NZ’s health and safety framework, PCBUs must ensure (so far as reasonably practicable) that workers receive suitable and adequate information/training/instruction/supervision.
That applies across roles: office, frontline, supervisors, contractors — the duty is about the work and risk.

When records become non-negotiable (example: hazardous substances)

Hazardous substances is the easiest example where the “optional records” assumption breaks.

WorkSafe’s hazardous substances guidance states you must keep a record of training and instruction provided to each worker, and make it available to inspectors or compliance certifiers.

So if your workplace includes hazardous substances, your record system needs to be audit-ready by design — not a spreadsheet you update “when you get time.”

The practical template (copy/paste-ready)

Below is a 4-tab template you can build in Excel/Google Sheets tomorrow.

The goal is not to build a perfect database — it’s to build something that:

• stays clean
• is easy to update
• supports evidence and refreshers
• doesn’t collapse when a key person goes on leave

Tab 1 — Training Records Register (core register)

Purpose: track training completion + version context.

Columns (copy/paste):

• Employee/Worker ID
• Full name
• Employment type (perm/casual/contractor)
• Role
• Site/Team
• Training item
• Training type (online / toolbox / workshop / external / on-job)
• Training owner (who maintains content)
• Version / policy reference
• Assigned date
• Due date
• Completion date
• Completion status
• Evidence link (URL/path)
• Refresher required (Y/N)
• Refresher interval (e.g., 12 months)
• Next due date
• Notes / exception reason

Example rows (3 roles):

Worker	Role	Site	Training item	Version	Completed	Evidence	Next due
A. Patel	Office Admin	Auckland	Privacy + data handling	POL-PRIV v3	2026-01-12	Link	2027-01-12
J. Ngata	Forklift Operator	Hamilton DC	Forklift refresher + site rules	SOP-FL v5	2025-11-03	Link	2026-11-03
S. Chen	Supervisor	Wellington	Incident reporting + lead investigations	PROC-INC v2	2026-02-01	Link	2027-02-01

Tip: keep “training item” language consistent (dropdown list). Your reporting gets dramatically easier.

Tab 2 — Competency & Verification Log (the “prove competent” tab)

Purpose: capture sign-offs, observations, practical checks.

Columns:

• Worker ID
• Name
• Role
• Site
• Task / competency
• Standard / checklist reference
• Verification method (observation / practical / quiz / assessment)
• Verified by (name + role)
• Verified date
• Evidence link (photo/video/doc/checklist)
• Competency status (competent / training required / restricted)
• Review interval (if relevant)
• Notes

Example use cases:

• operating equipment
• handling hazardous substances (site-specific handling)
• critical internal systems or safety processes
• any task where “completion” isn’t enough

Tab 3 — Licence / Certification Tracker (the expiry grenade pin)

Purpose: track tickets, licences, external certifications.

Columns:

• Worker ID
• Name
• Role
• Licence/cert type
• Issuer
• Licence/Cert ID
• Issue date
• Expiry date
• Recert requirement (course/assessment/medical)
• Evidence link (PDF/photo)
• Status (valid / due / expired)
• Notes

Pro move: add conditional formatting for “expires in 30/60/90 days.”

Tab 4 — Refresher Schedule (rules + automation)

Purpose: define refresher rules by risk level and keep them consistent.

Columns:

• Training item
• Risk tier (low/med/high)
• Who it applies to (role group)
• Refresher interval
• Reminder timing (e.g., 30/14/7 days)
• Owner (who reviews content)
• Evidence required? (Y/N)
• Verification required? (Y/N)
• Notes

Simple refresher tiers (example):

• High risk: 12 months (or as required by regulation/industry standard)
• Medium risk: 24 months
• Low risk: 36 months or when policy changes

This tab is what stops “set and forget” refreshers.

A system you can actually maintain (the “3-layer” model)

Templates don’t fail. Maintenance fails.
So here’s the model that keeps records clean without heroic admin.

Layer 1 — Assign training by role (not by person)

If you assign training one person at a time, you’re guaranteed to drift.

Instead:

• define role training profiles (Forklift Operator, Site Supervisor, Office Admin, Contractor – Maintenance, etc.)
• attach training items to roles + sites
• new starters inherit the role profile automatically (even if you’re doing it manually at first)

Outcome: you’ve built a repeatable standard.

Layer 2 — Track completion automatically where possible

Manual data entry is where quality dies.

Even if you’re not using an LMS yet, aim for:

• one source of truth for completions
• consistent naming conventions
• one owner for each training item

If you are using a platform, the bar is higher: completions should be automatic, and you should be able to report by role/site, not “who remembers to update the sheet.”

Layer 3 — Capture evidence + verification for high-risk tasks

This is where NZ organisations get tripped up.

High-risk work often requires:

• practical sign-offs
• supervisor confirmation
• evidence retention (photo/video/doc)
• site-specific training confirmation

And in hazardous substances contexts, you must keep records of training/instruction and make them available to inspectors/certifiers.

So don’t treat evidence as an optional extra. Make it part of the workflow for the tasks that matter.

The common failure points (and fixes)

Failure: Spreadsheet drift (duplicate versions, broken links, no ownership)

What it looks like:

• “Training Register FINAL v7.xlsx”
• different sites maintaining their own “version”
• evidence links go dead when folders change

Fix:

• nominate a single owner (HR, H&S, Ops — but one name)
• lock structure (tabs/columns don’t change without approval)
• store evidence in one consistent folder structure (by training item, then by worker ID)

Failure: “Set and forget” refreshers

What it looks like:

• refreshers discovered after expiry
• compliance scramble before audits

Fix:

• refresher rules live in Tab 4
• review refreshers monthly (15 minutes)
• trigger reminders 30/14/7 days out (even if it’s calendar reminders to start)

Failure: Contractor and casual chaos

What it looks like:

• contractors trained “somewhere else”
• no site-specific sign-off
• no proof you inducted them into your controls

Fix:

• treat contractors like a role group
• require site induction evidence
• record verification (even if the training was external)

WorkSafe’s hazardous substances guidance also notes that even if someone had similar training elsewhere, they still need site-specific training when new to the workplace.

Failure: Sites/teams doing their own thing

What it looks like:

• inconsistent standards
• different evidence expectations
• managers bypassing the system “to save time”

Fix:

• role profiles are standard
• sites can add local training, but not remove core training
• quarterly review: compare sites by completion + overdue + evidence completeness

Implementation checklist (a 1-week rollout you can actually do)

Day 1–2: Define roles + required training

• list your top 10–20 roles (start small)
• define required training by role + site
• mark which items require verification/evidence

Day 3: Build your register + refresher rules

• create the 4 tabs
• build dropdown lists for roles + training items
• set refresher rules (high/med/low)

Day 4–5: Add verification/evidence for high-risk

• define 5–10 high-risk competencies
• build a checklist or simple sign-off standard
• set evidence requirements (what “good” looks like)

Day 6–7: Reporting rhythm + quarterly review

• set a monthly 15-minute review (overdues + expiring licences)
• set quarterly review (roles, refreshers, evidence quality, policy changes)
• decide who owns what (owner per training item)

This is also where WorkSafe’s broader guidance helps: think about when training/supervision occurs and how you’ll supervise until workers can demonstrate competence.

Keep records clean without extra work

If you’re ready to move beyond spreadsheets, book a demo and we’ll walk you through how Tribal Habits tracks role-based training, reminders, evidence, and reporting — using scenarios that match your NZ workforce.

FAQ: Employee Training Records NZ: Template + Simple System

What should be included in employee training records in NZ?

At a minimum: who was trained, what they completed, when, and why it was required (role/site/hazard). For higher-risk work, add competency verification (sign-offs/observations), evidence links, and refresher/expiry dates.

Are training records legally required in NZ?

Not always for every type of training — but PCBUs must ensure, so far as is reasonably practicable, that suitable and adequate information/training/instruction/supervision is provided.In some contexts, like hazardous substances, you must keep records of training/instruction and make them available to inspectors or compliance certifiers.

How long should we keep training records?

A practical approach is to keep records for as long as they may be needed to demonstrate due diligence — especially for higher-risk work — plus a buffer after someone leaves. If you have specific regulatory requirements for a training area, follow those.

What’s the difference between training records and a competency register?

Training records show completion (what training was delivered). A competency register shows capability (verification that someone can perform a task safely and to standard).

How do we track refresher training properly?

Use refresher rules by risk tier, calculate next due dates, and trigger reminders before expiry (30/14/7 days). Most refresher failures happen because ownership and reminders aren’t built into the system.

What evidence should we keep for high-risk work?

Keep evidence that someone was trained and verified competent: completed checklists, supervisor sign-offs, licences/tickets, and any required practical assessments. For hazardous substances, record-keeping is explicitly required and must be available for inspection.

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
• Fix Event-Day Staff Training for Stadiums and Venues