Why this matters
The value of competence records comes from giving the responsible manager enough evidence to decide who is authorised for the task, who needs support and which gaps affect safe or compliant work. The arrangement earns its place when it helps the accountable person reach and explain the right operational judgement.
- Search intent
- Managers looking for practical WorkSafe guidance on competence records.
- Read time
- 3 min read
- Hub
- Skills, Training and Competence Management
Short answer
Competence records should give the responsible manager current evidence, clear ownership and a recorded basis for deciding who is authorised for the task, who needs support and which gaps affect safe or compliant work. It is effective when the live status can be tested without reconstructing events from separate files or conversations.
What this means in practice
Competence records can be tested in a realistic situation. For example, a manager may need to decide who is authorised for the task, who needs support and which gaps affect safe or compliant work while several teams are updating training history, refresher dates, task authorisations, evidence and competence gaps. In that moment, the manager must decide who is authorised for the task, who needs support and which gaps affect safe or compliant work; the record should make the relevant facts and accountable role immediately clear.
Competence records: the specific failure mode is that work is allocated based on familiarity rather than current evidence of competence. The consequence is not simply untidy administration: the next person may act on a status that no longer reflects the job, asset or operating condition.
Competence records: the minimum useful trail covers training history, refresher dates, task authorisations, evidence and competence gaps. It should show both the operational facts and the point at which an accountable person accepted, restricted or escalated the work.
Competence records: WorkSafe supports this issue by preserving the connection between competence records, accountable action and review evidence. That makes it easier to challenge weak close-out without recreating the whole story.
For competence records, day-to-day control should produce safer task allocation, stronger training evidence and fewer competence-related repeat issues. WorkSafe does not guarantee compliance outcomes, but it can make the control trail easier to manage and explain.
Key checks
- Is ownership of competence records explicit at every handover?
- Are exceptions separated from routine completions?
- Can the manager explain who is authorised for the task, who needs support and which gaps affect safe or compliant work from the record alone?
Common mistakes
- Using the same response for routine and exceptional competence records cases.
- Assigning an action without defining the evidence needed for acceptance.
- Reporting totals without examining overdue, repeated or high-consequence exceptions.
What good looks like
For competence records, ownership is named, the status reflects current conditions and supporting records stay attached to the decision. Routine completions and exceptions can be reviewed separately, allowing the manager to justify who is authorised for the task, who needs support and which gaps affect safe or compliant work.
When to use WorkSafe
Use WorkSafe for competence records where evidence passes between roles, shifts or systems and the current position is difficult to establish quickly. Configure the first workflow around the source record, accountable role and proof needed to decide who is authorised for the task, who needs support and which gaps affect safe or compliant work.
Apply these checks to one recent competence records case and note where its ownership, decision or verification becomes unclear.