Workplace practice sheets
Use the fictional evidence in your own notes. The exercises do not create or approve operational records.
Permit live-condition review
For the contractor case, identify the exact work boundary, roles, field evidence, interacting jobs, invalidating changes and handback restrictions. Explain what a signature can and cannot establish.
- Fictional exercise: Two contractors prepare maintenance near an operating process. Their individual permits look complete, but the work boundary, adjacent activity and final handback are not consistently understood.
- For the contractor case, identify the exact work boundary, roles, field evidence, interacting jobs, invalidating changes and handback restrictions. Explain what a signature can and cannot establish.
- Make three columns: observed facts, missing evidence and the responsible action. State the condition that prevents starting or requires stopping, and the verification needed before release. Do not invent results or approvals.
Open the live SHAREhub resource ↗
Optional extension. Live SHAREhub tools may need a separate sign-in. The included exercise works offline and submits no workplace record.
Optional visual practice and worked application
Use these fictional exercises to compare evidence and rehearse decisions. They do not alter course completion or assessment requirements. You can work through the same choices on paper.
Separate the permit record from the physical controls
Fictional continuing case. The board shows 100% completion. At the work point, the crew identifies an asset mismatch and an area log records a safeguard impairment not reflected on the permit.
Authorisation has a defined basis
A permit coordinates and authorises defined work under stated conditions. It does not physically establish the correct asset or restore an impaired safeguard.
Contradictory state
Resolve the asset identity and impairment through the responsible site process. Do not choose whichever document or signature count permits the earliest start.
Worked issue check
Scope: stated inspection on the exact asset. Conditions: physical identity and credited safeguard unresolved. Decision: retain the affected hold. Record which responsible role must verify and accept the corrected state before issue/reliance.
Sort the permit-readiness evidence
Fictional worked application: A fictional processing site uses a digital permit board. Every mandatory field is complete, but the field asset tag differs from the permit. A lift is then added above a separately accepted work crew, and two work packs each assume the other authority performs a critical check. Stage evidence: The board shows 100% completion. At the work point, the crew identifies an asset mismatch and an area log records a safeguard impairment not reflected on the permit.
Sort the permit-readiness evidence. Use the evidence in this stage, rather than assuming what happened off screen.
- The actual tag differs from the permit identity. Physical/interface condition to resolve. The unresolved work-point identity governs release.
- The area log records an impaired credited safeguard. Physical/interface condition to resolve. A signed permit cannot make the safeguard available.
- All mandatory digital fields are complete. Record status insufficient on its own. Processing completeness does not establish physical control.
- The permit has more signatures than the contradictory log. Record status insufficient on its own. Signature quantity cannot resolve the actual plant state.
Prepare the task and interface assessment before permit issue
Draft a fictional permit-lifecycle record: exact asset/scope, physical prerequisites, shared checks, issue authority, suspension trigger, revalidation and actual hand-back state. Keep the permit separate from proof that controls exist.
Draft a fictional permit-lifecycle record: exact asset/scope, physical prerequisites, shared checks, issue authority, suspension trigger, revalidation and actual hand-back state. Keep the permit separate from proof that controls exist.
Use only a fictional or authorised non-confidential example. Keep planned actions separate from verified current protection.
A saved practice entry does not alter the graded course or authorise work.
Coordinate scope and shared verification
Fictional continuing case. The task changes from inspection to opening equipment while another operation proposes lifting overhead. Each work lead believes the other party owns the critical verification.
Reassess the extension
Opening equipment is not automatically within an inspection scope. Review and accept changed hazards and controls before the extension starts.
Resolve the interaction
Separate job acceptance does not assess a new overhead-work exposure. Coordinate the combined activities and define any limits or hold points through the site system.
Assign the check explicitly
Identify who performs, verifies and accepts the critical condition. Two cross-references do not make a check happen. Consider a suitable non-intrusive method before relying on a more complex permit.
Choose the actions needed before the changed jobs proceed
Fictional worked application: A fictional processing site uses a digital permit board. Every mandatory field is complete, but the field asset tag differs from the permit. A lift is then added above a separately accepted work crew, and two work packs each assume the other authority performs a critical check. Stage evidence: The task changes from inspection to opening equipment while another operation proposes lifting overhead. Each work lead believes the other party owns the critical verification.
Choose the actions needed before the changed jobs proceed. Select every defensible evidence or action; leave unsupported substitutes unselected.
- Review the opening scope and current controls before extending the task. Relevant evidence. The new intervention changes the authorisation basis.
- Coordinate the overhead interaction and name the verifier/acceptor for the shared check. Relevant evidence. Separate packs left a practical responsibility and exposure gap.
- Keep the old task title so the existing permit remains valid. Insufficient evidence. Renaming cannot contain a real scope change.
- Assume the older permit takes priority and resolves every later interaction. Insufficient evidence. Relative issue time does not control the new combined exposure.
Prepare the task and interface assessment before permit issue
Draft a fictional permit-lifecycle record: exact asset/scope, physical prerequisites, shared checks, issue authority, suspension trigger, revalidation and actual hand-back state. Keep the permit separate from proof that controls exist.
Draft a fictional permit-lifecycle record: exact asset/scope, physical prerequisites, shared checks, issue authority, suspension trigger, revalidation and actual hand-back state. Keep the permit separate from proof that controls exist.
Use only a fictional or authorised non-confidential example. Keep planned actions separate from verified current protection.
A saved practice entry does not alter the graded course or authorise work.
Suspend and hand back the actual state
Fictional continuing case. A plant change interrupts work. Later the repair entry is complete, but containment verification remains outstanding and the permit is about to be closed to clear the board.
Validity must be current
After changed conditions, use required revalidation rather than changing a date and assuming the original permission still applies.
Close-out is state communication
Record incomplete tests, impairments and continuing restrictions. Closing the form neither performs a test nor establishes unrestricted operation.
Audit the work, not just processing
Closed-permit totals can show administrative throughput. Compare them with current task conditions and implemented controls before treating them as assurance.
Follow the permit to a defensible close-out
Fictional worked application: A fictional processing site uses a digital permit board. Every mandatory field is complete, but the field asset tag differs from the permit. A lift is then added above a separately accepted work crew, and two work packs each assume the other authority performs a critical check. Stage evidence: A plant change interrupts work. Later the repair entry is complete, but containment verification remains outstanding and the permit is about to be closed to clear the board.
Have current scope, interfaces and required conditions been reaccepted after the plant change?
- Have current scope, interfaces and required conditions been reaccepted after the plant change?
- No / not established in this case: The old date and signatures do not establish current validity. Next: Current decision — Retain suspension/hold and resolve the changed basis through the site system.
- Yes, supported by the stated evidence: Proceed to the separate verification question; the first condition alone is not the final decision. Next: Are containment checks, restoration and the required release evidence complete?
- Current decision
Retain suspension/hold and resolve the changed basis through the site system.
- Are containment checks, restoration and the required release evidence complete?
- The relevant evidence is still missing: State the incomplete verification and retain the relevant restriction. Next: Verification still required — State the incomplete verification and retain the relevant restriction.
- Yes, the responsible check is evidenced within its scope: Record the accepted actual state and communicate remaining limits. Next: Scoped decision supported — Record the accepted actual state and communicate remaining limits.
- Verification still required
State the incomplete verification and retain the relevant restriction.
- Scoped decision supported
Record the accepted actual state and communicate remaining limits.
Prepare the task and interface assessment before permit issue
Draft a fictional permit-lifecycle record: exact asset/scope, physical prerequisites, shared checks, issue authority, suspension trigger, revalidation and actual hand-back state. Keep the permit separate from proof that controls exist.
Draft a fictional permit-lifecycle record: exact asset/scope, physical prerequisites, shared checks, issue authority, suspension trigger, revalidation and actual hand-back state. Keep the permit separate from proof that controls exist.
Use only a fictional or authorised non-confidential example. Keep planned actions separate from verified current protection.
A saved practice entry does not alter the graded course or authorise work.
Optional choices save on this browser, separately from recorded course progress. Live tools retain their own access and competent-review requirements.