Why this matters
The case for permit-to-work records is that the permit is approved but the live status, scope change or close-out condition is not visible to the people managing the area. For managers controlling higher-risk work, approvals and work status, the immediate concern is whether the available facts support a timely and proportionate decision.
- Search intent
- Managers looking for practical WorkSafe guidance on permit-to-work records.
- Read time
- 3 min read
- Hub
- Permit-to-Work Management
Short answer
Permit-to-work records should give the responsible manager current evidence, clear ownership and a recorded basis for deciding whether work is authorised, active, paused, changed, extended or safe to close. It is effective when the live status can be tested without reconstructing events from separate files or conversations.
What this means in practice
Permit-to-work records can be tested in a realistic situation. For example, a manager may need to decide whether work is authorised, active, paused, changed, extended or safe to close while several teams are updating permit request, approval, conditions, isolations, extensions, evidence and close-out. In that moment, the manager must decide whether work is authorised, active, paused, changed, extended or safe to close; the record should make the relevant facts and accountable role immediately clear.
Permit-to-work records: a record can be complete on paper and still fail the manager. That happens when the permit is approved but the live status, scope change or close-out condition is not visible to the people managing the area, removing the context needed to choose a proportionate response.
Permit-to-work records: a defensible review uses permit request, approval, conditions, isolations, extensions, evidence and close-out. Keeping those records connected prevents a later note or photograph from being mistaken for proof that the original concern was resolved.
Permit-to-work records: WorkSafe can make permit-to-work records visible at the point responsibility changes hands. Linking the source record, action and verification reduces ambiguity about what is open and what has genuinely been resolved.
For permit-to-work records, day-to-day control should produce clearer permit visibility, fewer coordination gaps and stronger evidence around high-risk work. WorkSafe does not guarantee compliance outcomes, but it can make the control trail easier to manage and explain.
Key checks
- Which role creates, reviews and accepts the permit-to-work records record?
- Is superseded evidence clearly distinguishable from current proof?
- Does the review result lead to a stated operational decision?
Common mistakes
- Moving permit-to-work records between teams without a named handover point.
- Keeping photographs or notes outside the record they are intended to support.
- Assuming an updated status explains the decision history.
What good looks like
For permit-to-work 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 whether work is authorised, active, paused, changed, extended or safe to close.
When to use WorkSafe
Use WorkSafe for permit-to-work 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 whether work is authorised, active, paused, changed, extended or safe to close.
Apply these checks to one recent permit-to-work records case and note where its ownership, decision or verification becomes unclear.