Should you build or buy Permit to Work (PTW)?
Permit-to-work software manages the approval, issuance, and audit trail for work permits at industrial sites: hot work, confined space entry, and other high-risk tasks that require sign-off before work starts. Refineries, chemical plants, and manufacturers use it to enforce hazard controls, isolation procedures, and compliance record-keeping across contractors and employees.
For a high-hazard plant, buy a control-of-work product with isolation and SIMOPS controls and confirm the SAP PM or Maximo connector in a scenario demo; for a lower-hazard site with a bounded permit workflow, a low-code permit app is a proven option, provided you budget for lifecycle support and audit-grade records.
Build it, buy it, or bridge?
When building makes sense
Low-code permit apps have real production use at industrial sites with a bounded, well-defined process. The pattern that works is a single site with a clear permit workflow, a small internal team willing to own ongoing maintenance, and a hazard profile that doesn't require isolation management or SIMOPS conflict detection layered on top. Where this breaks down is scope creep: as soon as a site needs to check a new permit against active isolations elsewhere on the plant, or coordinate simultaneous operations across crews, the logic gets safety-critical fast, and that's exactly the depth specialist vendors build for. Building makes sense for a lower-hazard facility with a genuinely simple permit process. It stops making sense the moment isolation interlocks, live asset data, or audit-grade evidence for a regulator enter the requirements, because that's where a bounded internal app runs out of road.
When buying makes sense
For a high-hazard plant, buy a control-of-work product and confirm its SAP or Maximo work-order integration in a live demo before signing. Sphera and eVision Permit Vision connect permits directly to risk assessments, isolation management, and SIMOPS conflict detection, the safety logic that keeps two crews from working incompatible tasks on the same equipment at the same time. VelocityEHS leans toward contractor coordination, and Intelex builds permit-to-work into a broader EHSQ platform, so the right fit depends on what else you're already managing in that ecosystem. For a lower-hazard site with a bounded workflow, a low-code permit app is a legitimate alternative, provided you budget for lifecycle support and audit-grade record-keeping rather than treating it as a one-time build. Match the product's safety depth to your actual hazard class rather than buying more than the site needs.
The desk read
Build-versus-buy analysis for Permit to Work (PTW) is being written. In the meantime, the framework that drives every B4 call is on the B4 Index page.
Frequently asked
Can a company build its own permit-to-work system?
For a single low-hazard site with a bounded, well-understood process, yes, and low-code apps have run in production this way. The build case weakens fast once isolation management, SIMOPS conflict detection, or integration with live asset data enters the requirements, since that safety-critical logic is what specialist vendors are built around.
What is SIMOPS conflict detection, and why does it matter for permit software?
SIMOPS, or simultaneous operations, is when multiple crews work on interacting equipment or areas at the same time, and conflict detection flags permits that would put two incompatible activities in play together. This is the safety logic that separates a specialist control-of-work product from a basic approval workflow, and it's genuinely hard to get right without dedicated engineering.
Should a permit-to-work system integrate with SAP or Maximo?
If work orders and asset data already live in SAP or Maximo, yes: integration avoids re-entering the same equipment and job data twice and keeps permit records tied to the actual maintenance history. Ask a vendor to demonstrate the connection against your own asset data before buying rather than taking the integration on faith.
What are the main permit-to-work vendors?
Representative vendors include eVision Permit to Work (Permit Vision), Intelex Permit to Work. B4 Pro includes the category score and the full vendor list.