Skip to main content
    QHSEtech
    Updated
    All glossary terms
    Content date: · No individual check logged· AI use

    Permit to WorkPTW

    Definition

    Permit to Work — a formal process for authorising and coordinating specified work, its controls and handover.

    Editorial definition: The QHSE Standard, updated 3 October 2026 · https://qhsetech.com/glossary/permit-to-work

    Scope: A permit supports risk control; issuing one does not by itself make work safe or replace the risk assessment.

    Example for your evaluation: Demonstrate how a changed work condition reaches the permit issuer and affected teams.

    Sources checked: . Examples are editorial illustrations.

    What HSE guidance says a permit-to-work system is

    HSE's HSG250, Guidance on permit-to-work systems (2005), describes a permit-to-work system as a formal recorded process for controlling work identified as potentially hazardous, and as a means of communication between site management, plant supervisors, operators and the people carrying out the work. The permit itself is the paper or electronic form within that wider system: it authorises certain people to carry out specific work at a specific site at a certain time and sets out the main precautions.

    HSG250 lists what the system must provide beyond the form: clear authority over who may authorise which jobs; training in issue, use and closure; monitoring and auditing; display of permits; suspension; control of activities that interact; formal handover when a permit runs longer than one shift; and formal hand-back so plant is safe before reinstatement. Permits suit non-production work such as maintenance, repair, inspection, testing and cleaning, non-routine operations, and jobs where two or more groups must coordinate. They are not normally needed for general visitors or routine maintenance in non-hazardous areas.

    For electronic permits, HSG250 expects safeguards against unauthorised issue or acceptance, such as password-protected electronic signatures; no remote issue without a site visit; communication of any change to an issued permit; the ability to print a paper permit for display at the job; training that discourages copying sections from old permits; and backup for software failure or power loss. For US process safety, 29 CFR 1910.119(k) separately requires a hot work permit for hot work on or near a covered process.

    Sources opened :

    What a permit record holds in software

    • Permit type (for example hot work, confined space entry, excavation or isolation), job description, location and equipment.
    • Hazards, a link to the task risk assessment, and gas test results where required.
    • Precautions, including isolations recorded on a cross-referenced isolation certificate.
    • Signatures with time for each role: the issuer, the person accepting the work and the area authority.
    • Validity period, suspensions, shift handovers, hand-back and cancellation, each timestamped.
    • Cross-references to other live permits in the same area; one HSG250 case study records that, at the time of Piper Alpha, work under one permit that affected another was not cross-referenced.

    Work permit or regulatory permit?

    A permit to work authorises one specific job. A regulatory or environmental permit is a licence from an authority, with conditions and renewal dates. Searching for "permit software" returns both. Two catalog evidence records draw the line explicitly: Intelex's lists Permit Management (renewals, thresholds, compliance tasks) as distinct from job-specific work authorisation, and Cority's separates its electronic permit to work from environmental licence conditions.

    A hypothetical example: two jobs on one pump skid

    The following scenario is invented and does not describe a real plant. On a Tuesday morning a maintenance team requests a permit to replace a seal on a pump. In the afternoon a separate contractor asks for a permit to grind a handrail on the platform directly above the same skid. Each request looks reasonable alone.

    The area authority reviewing the requests sees both on one screen of live and pending permits for the unit. The grinding would throw sparks onto a section being opened for the seal replacement, so she does not approve the second request for that window. She moves the grinding to the following morning, notes the reason on both permits, and asks the maintenance team to confirm hand-back before the second permit is issued. At the end of the shift the permit holder hands the job to the night crew, who read the status, countersign, and note that the pump is still isolated. The next day the pump is closed up, the area is inspected, and the permit is cancelled with the time recorded. The value lay less in the form than in the conversation it forced and the record it left.

    Common misunderstandings about permit to work

    • A signed permit is not a safe job. It records that conditions were checked and precautions agreed at the moment of issue; conditions can change, and the people doing the work still have to stop when they do.
    • A permit does not replace the risk assessment or the method statement. It refers to them and adds the time, place and authority for the specific job.
    • More permits do not mean more safety. A system that issues permits for routine low-hazard work tends to teach people to sign without reading, which weakens the cases where the permit matters.
    • An electronic permit is not automatically a better permit. A badly designed paper process turned into a form on a screen is still a badly designed process, now with faster sign-offs.
    • Issuing and accepting are not the same act. The person who authorises the job and the person who carries it out take on different responsibilities, and a record should show both.
    • Closing the permit is not paperwork at the end. Hand-back is the point at which equipment is confirmed safe to return to service, so a permit closed in the office without a check at the job is a gap.

    How permit to work relates to other glossary terms

    A permit sits between hazard analysis upstream and physical controls downstream. The terms around it clarify which record belongs to which step.

    • Lockout/tagout: the isolation of energy sources, which a permit often cites as one of its precautions but which has its own procedure and verification.
    • Management of change: decides whether a change to plant or process should happen at all; a permit controls a single job once it has been decided.
    • PSM: a US regulation that, for covered processes, includes a specific hot work permit requirement.
    • Near miss: events such as a permit being worked outside its limits belong here, and should feed back into how permits are issued.

    Records and evidence that usually exist for a permit

    • The permit itself, with the job, location, equipment and the dates and times for which it is valid.
    • Names and signatures, with times, of the person issuing, the person accepting and anyone who takes over.
    • The risk assessment or job hazard analysis it refers to, and any gas test or measurement readings recorded before and during work.
    • A reference to the isolation record for the equipment, including who applied and who removed each isolation.
    • Notes on suspension, extension, changed scope and shift handover.
    • A hand-back and cancellation record showing that the area was inspected and the equipment returned to the operator.
    • Periodic audit or monitoring results on whether permits are completed as the procedure intends.

    What a software tool needs to capture for permit to work

    • Distinct states (requested, issued, accepted, suspended, handed over, cancelled) with a time and a named person for each change of state.
    • Permit types with their own required fields and approvers, so a confined space entry asks different questions from a general maintenance permit.
    • A live view of all permits in an area, so overlapping work can be seen by the person authorising it.
    • Roles that prevent a single person from issuing and accepting the same permit unless the procedure allows it.
    • A link to the isolation record and the risk assessment, rather than free text that says one exists.
    • A paper fallback and a way to print the permit for display at the job, and a defined process for what happens if the system is unavailable.
    • Immutable history on issued permits: changes after issue should create a visible amendment, not overwrite the original.

    Catalog profiles documenting permit-to-work workflows

    Same rule for every product: tagged “Permit to Work”, “Permits to Work (PTW)” or “Control of Work”, with a sourced permit-to-work or isolation capability in its record, or one the vendor stated to us, labelled as vendor-stated. Documented and conditional capabilities qualify; check the linked scope before treating a module as included.

    Tekmon pays for a sponsored placement (above); its place in this list follows the same rule as every entry. How lists are ordered

    All 21 matching profiles are shown. Documentation review, not hands-on testing or a claim of compliance.

    Related software

    Frequently asked questions

    Does a permit replace risk assessment?

    No. The permit communicates and coordinates defined work and controls within the wider safe system of work.

    What should a SIMOPS demo show?

    Use two proposed jobs that may interact. Ask how conflicts are identified, reviewed and resolved; establish which steps are manual.

    How long should a permit remain valid?

    Use the site's procedure, work conditions and applicable requirements. Demonstrate how changed conditions, suspension and handover are handled.

    More safety terms

    Related guides