HSE: permits to work, incidents and corrective actions to closure

#Purpose and scope

This chapter follows the two HSE chains that BSuit enforces: a permit to work, which must be approved before hazardous work starts, and the incident closure chain (incident, non-conformance report, corrective actions). Risk assessments, risk categories, checklist templates and inspection runs live in the same module and are touched on briefly at the end.

#Before you start

1. An approval workflow linked to the PERMIT-WORK record type. Without one, a permit cannot be submitted (“No active workflow is configured for record type ‘PERMIT-WORK’.”).
2. Incident categories and severities are set up so incidents can be classified.
3. The named HSE permissions are granted to the people who act: hse.permit.activate, hse.permit.close, hse.corrective_action.verify, hse.ncr.raise, hse.ncr.close and hse.incident.close. The seeded HSE Officer role holds all six; superusers pass as well.

#1. Permit to work

1. Open Permits to work and add a permit: permit number, type (Hot Work, Confined Space, Working at Height, Electrical, Excavation or General), location, work description, valid from and valid to, hazards and precautions.
2. Choose Submit. The permit moves from Draft to Submitted and starts the PERMIT-WORK approval workflow.
3. The approver chooses Approve or Reject. Approval sets the status to Approved; rejection sets it to Revoked.
4. A supervisor chooses Activate when the work actually starts. The status becomes Active.
5. When the work is finished, choose Close. The status becomes Closed.

#2. Record an incident

1. Open the Incident timeline. It lists every incident, newest first, and can be filtered by severity, status and near misses only. Use its link to the incident list to add a record.
2. Enter title, incident date, location, status (Open or Investigating), category, severity, reporter and investigator.
3. Tick Near Miss when nothing was injured or damaged. Record injuries, fatalities, property damage, root cause and a photo.

#3. Raise a non-conformance report

1. Open the incident and go to the Closure chain tab (save the incident first).
2. Choose Raise NCR. BSuit numbers it NCR-yyyy-nnnn, copies the description and root cause from the incident and links it to the incident.
3. Severity defaults from the harm recorded: critical if there are fatalities, major if there are injuries, otherwise minor.

#4. Corrective actions

1. Add corrective actions against the NCR (title, type, owner, due date).
2. Track them on the Corrective actions board: drag a card between columns or use Move to. The columns are Open, In Progress, Done and Verified.
3. In the incident’s Closure chain tab you can also choose Mark done on an action.
4. When an action is Done, an authorised person chooses Verify. The verifier and time are recorded from the login.

#5. Close the NCR, then the incident

1. In the Closure chain tab, choose Close NCR when all its corrective actions are Done or Verified.
2. Choose Close incident when no NCR raised from it is still open. The closing user and time are recorded.
3. To reopen, choose Reopen on the closed NCR or incident: both return to Investigating.

#6. Monitor

HSE dashboard shows open incidents by severity, overdue corrective actions, permits expiring within a window, and inspections due. Each panel links to its list.

#Related HSE records

Risk assessments score likelihood times impact on a 1 to 5 scale; the server calculates the score and level (1 to 4 low, 5 to 9 medium, 10 to 15 high, 16 to 25 critical) so a form cannot record a lower level. Checklist templates define inspections, checklist runs record them, and a failed item on a run can raise an NCR.

#Who can do what

Activating and closing permits, raising and closing NCRs, closing or reopening incidents and verifying corrective actions each need the matching named permission; without it the action fails with “You need the ‘…’ permission to do this.” Approving or rejecting a permit is done by the approver in the workflow. Superusers hold every permission.