Most PTW demos look the same for a reason
Every permit-to-work vendor demo follows a similar sequence: raise a permit, route it through approval, capture an e-signature, close it out. That workflow is table stakes now. It tells you almost nothing about whether the system can show an Area Authority what else is happening on the same plant, at the same time, in the same zone.
That gap matters more than most procurement checklists reflect. On assets running several concurrent activities — hot work near a confined space entry, crane lifts over live process lines, contractor teams working different systems in overlapping areas — the risk usually isn't inside any single permit. It's in the interaction between permits that nobody in the room is looking at together.
What real-time cross-permit visibility actually means
Real-time cross-permit visibility is the ability of a permit to work system to show every live permit, isolation, and simultaneous activity on an asset in one view, updated as work starts, changes, or closes — so conflicts between concurrent jobs can be identified before they become incidents rather than discovered afterwards.
Most commercial PTW products can produce a list of open permits. Fewer can show where those permits sit in relation to each other physically, or flag automatically when two jobs shouldn't run at the same time. That distinction is the one this checklist is built around.
Why the standard feature list doesn't tell you this
Vendor comparison pages tend to converge on the same set of features: configurable workflows, digital signatures, mobile forms, reporting dashboards. These are necessary. None of them answer the question that actually determines whether the system helps with simultaneous operations — can a duty holder see, in one place, every live permit and its interactions across the site, or does the software just move a paper form onto a screen?
A genuinely useful evaluation has to test for that specifically, because a system can score well on every generic feature and still leave SIMOPS visibility to the same manual cross-checking teams do today with a permit board and a radio.
What to test in a demo
Ask the vendor to show these directly, on their own system, not on slides.
- **A shared site or zone view.** Can the system display every currently live permit against an asset layout or zone map, rather than as a flat list sorted by permit number or requester?
- **Automatic conflict flagging.** If two permits are raised for adjacent zones with incompatible work types — for example a hot work permit and a nearby confined space entry — does the system surface that automatically, or does it rely on the person raising the permit to remember the interaction matrix?
- **Isolation register integration.** Ask them to show a permit that depends on an isolation shared with another live permit, and what happens if someone attempts to remove that isolation while the second permit is still open. If the isolation register is a separate document referenced by number rather than a linked, live record, that's worth noting. We've written before about why isolation is the weak point in permit to work, and it's usually the first place cross-permit visibility breaks down.
- **Offline and mobile behaviour in the field.** Ask what happens to a permit accepted on a handheld device when connectivity drops mid-shift, and how the record reconciles once the device reconnects. Offshore and remote onshore sites need an honest answer here, not a demo run entirely on office wifi.
- **Audit trail depth after amendment.** Pull up a permit that's been suspended, extended, or amended, and ask to see its full history — not just the current state. If the system can only show what a permit looks like now, it can't show you what actually happened during a shift handover.
Red flags that suggest digitised paper, not a live system
A few patterns are worth watching for during procurement conversations. If the vendor describes conflict checking as something the permit issuer does manually with a matrix document open in another window, the software hasn't actually absorbed that logic. If "real-time visibility" turns out to mean a report that refreshes on a schedule rather than as permits change state, it isn't real time in the sense that matters for SIMOPS. And if mobile use is a scanned PDF with a signature box rather than a live connection to the permit record, offline reconciliation is likely to be a manual step someone has to remember to do later.
None of this means the vendor is being dishonest. Digitising a paper-based workflow is a genuine improvement over paper, and for some sites it may be sufficient. But it isn't the same capability as shared, automated cross-permit visibility, and buyers should be clear with themselves about which one they're evaluating.
Building this into a scoring framework
A simple way to keep the evaluation objective is to score each candidate system against a fixed set of criteria rather than a free-form impression of the demo: site/zone visibility, automated conflict detection, isolation and interaction-matrix integration, field performance (mobile and offline), and audit trail completeness after amendment. Weight these according to how the asset actually operates — a single-site facility with low concurrent activity has different priorities to an offshore platform running a turnaround with multiple contractor crews on site. Our buyer's guide to permit to work software goes into the wider procurement process this checklist sits inside, including contract and implementation questions beyond the software itself.
On assets with a high volume of contractor-issued permits, it's also worth checking how the system handles competency verification alongside the permit itself — a separate but related evaluation point covered in our piece on closing the competency gap on critical equipment.
If you're partway through a PTW procurement process and want to work through this checklist against your own site's SIMOPS profile, we're happy to talk through what a live demonstration should actually show for an asset like yours.