Instead of IAMTech iPermit
Stop renting IAMTech iPermit. Own your permit to work system.
We build your version around your permit kinds, your isolation points and your site procedure, bring your iPermit training matrix and permit register across, and run it for you through Omni by Enterprise DNA.
IAMTech lists iPermit at US$19,500 a year for up to 10 named users, US$39,000 for up to 100, US$65,000 for up to 500 and US$97,500 for up to 1,000.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
Where the money goes
What an iPermit licence pays for beyond your permits
A site's permit system lives on a few records: the permit, who is on it, what is isolated and locked, the gas readings and who went in. iPermit puts those behind a licence counted in named users, with its own screens, mobile app and integrations. Most of the bill is the layer between your people and those records.
Tiers counted in named users
The Small tier stops at 10 named users. The eleventh issuer, receiver or isolator moves a site to the US$39,000 tier.
Training sold by the course
On the Small and Medium tiers, each online training course is listed at US$1,560. Large and Enterprise include one.
Integrations marked as add-ons
IAMTech's price list marks Active Directory sign-in and an on-premise install as add-ons, alongside the annual licence.
Screens and an app for every role
Request, review, approve and sign screens for each role, on desktop and phone. That is the part a database and plain questions replace.
Answers limited to its reports
A new question, such as which assets were isolated most this quarter or whose tickets lapse before the shutdown, waits for a report someone builds.
Your safety history in its format
Permits download as PDF. A list of every permit, isolation and ticket in a form you can query is something you ask the vendor for.
What your site gets
The checks that matter, run on records you own
Permits
Permits that will not issue on a missed control
Each permit kind carries what it needs. Issuing refuses until those are in place, and the only way past is a named person accepting it, written on the permit.
- check Hot work, confined space, electrical, height, excavation, lifting and general, each with its own controls
- check Clashes caught before issue: hot work in the same area as an open confined space, a lift over work at height
- check Permits past their time, or running a shift with no handover, on the list every morning
- check Hot work closed before the fire watch ran its time, flagged for 30 days
Isolations
Every energy point, every lock, every person
An isolation covers one piece of plant and every energy source on it, each with its lock number. It is proved dead before work starts, and it cannot come off while anyone still relies on it.
- check Points still live on an isolation named by device and energy type
- check Isolations nobody proved dead, stopped at issue
- check Personal locks left on by someone who has signed off or whose job has closed
- check Isolation hours by asset over 90 days: where maintenance keeps going back
Confined spaces
Who is inside, on what air, with whom outside
Gas tests are recorded against limits with their source, and entry is refused on a stale or failed test, with no standby, or for anyone not signed on and ticketed.
- check Who is inside right now, how long, and their standby, first in every answer
- check Oxygen and flammable gas limits from the confined spaces standard and code of practice
- check Tests older than your retest interval flagged, and who took them
- check An entry log printed per permit, with every reading and every in and out
People and contractors
Tickets checked against the role, not a spreadsheet
Every issuer, receiver, crew member, standby, gas tester and isolator on an open permit is checked against the ticket that role needs, and every contractor against their induction and their company's insurance.
- check Lapsed tickets on live permits, by person and role
- check Tickets, inductions and insurance lapsing in the next 30 days, by company
- check Sign-on refused for a contractor whose induction or insurance has lapsed
- check A renewal note to each contractor drafted for you, never sent without you
Make it yours
Design your own IAMTech iPermit replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from IAMTech iPermit. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your IAMTech iPermit data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Permit to Work for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Permit to Work for Claude Code
Connected to your own database
What is isolated on site right now, and is every point locked and proved dead?
ISO-305
- Asset
- RM1
- Asset name
- Roller mill 1
- Area
- MILL
- Status
- verified
- Isolator
- Sione Fifita
- Verified by
- Sione Fifita
- Points locked
- 2 of 2
- Personal locks on
- 1
- Hours isolated
- 32.5
- Lockbox
- LB-2
ISO-310
- Asset
- BE2
- Asset name
- Bucket elevator 2
- Area
- SILO
- Status
- applied
- Isolator
- Raj Patel
- Points locked
- 2 of 2
- Personal locks on
- 1
- Open permits
- P-2044
- Hours isolated
- 20.5
- Lockbox
- LB-1
ISO-311
- Asset
- SIL3
- Asset name
- Wheat silo 3
- Area
- SILO
- Status
- verified
- Isolator
- Sione Fifita
- Verified by
- Sione Fifita
- Points locked
- 2 of 3
- Personal locks on
- 3
- Open permits
- P-2041
- Hours isolated
- 4.5
- Lockbox
- LB-3
ISO-312
- Asset
- PK1
- Asset name
- Bagging line 1
- Area
- PACK
- Status
- verified
- Isolator
- Kiri Ngata
- Verified by
- Kiri Ngata
- Points locked
- 2 of 2
- Personal locks on
- 1
- Open permits
- P-2045
- Hours isolated
- 6.3
- Lockbox
- LB-4
| Code | Asset | Asset name | Area | Status | Isolator | Verified by | Points locked | Personal locks on | Open permits | Hours isolated | Lockbox |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ISO-305 | RM1 | Roller mill 1 | MILL | verified | Sione Fifita | Sione Fifita | 2 of 2 | 1 | 32.5 | LB-2 | |
| ISO-310 | BE2 | Bucket elevator 2 | SILO | applied | Raj Patel | 2 of 2 | 1 | P-2044 | 20.5 | LB-1 | |
| ISO-311 | SIL3 | Wheat silo 3 | SILO | verified | Sione Fifita | Sione Fifita | 2 of 3 | 3 | P-2041 | 4.5 | LB-3 |
| ISO-312 | PK1 | Bagging line 1 | PACK | verified | Kiri Ngata | Kiri Ngata | 2 of 2 | 1 | P-2045 | 6.3 | LB-4 |
Ask it anything
Ten questions this version answers
These run against the free version today. iPermit has its own reports. The difference here is that you own the records and the rules, and you ask in your own words.
Switching
How to switch from IAMTech iPermit
A move usually involves exporting and mapping your records, checking the import, then running both systems side by side for a week before you stop using iPermit.
- 1
Request your records
Ask IAMTech or your administrator for the training matrix and permit register as spreadsheets. iPermit permits can be downloaded as PDFs, but IAMTech does not publish a spreadsheet format, so check what your account allows and ask IAMTech about exporting the register as CSV or Excel. Decide which history you need to bring across, including whether you need closed permits or only the records needed to operate.
- 2
Load people and permits
Save the training matrix and permit register as CSV if your account can provide them that way, then use the import process to bring them into the new system. It loads people and tickets first, followed by permits. Open permits arrive as requested, not as active permits. They need to be isolated, tested and issued again in the new system, so no one inherits an isolation they did not see applied.
- 3
Review import findings
Check the import results before relying on the records. Review anything the import flags, and compare the people, tickets and permits with your iPermit records. Pay close attention to fields that did not map cleanly and to information that is missing. Resolve gaps before using the new system to issue permits. Confirm that each open job has the right people and controls recorded, then isolate, test and issue it here.
- 4
Run both systems together
For a week, raise every new permit in both systems. Compare the live board, the isolations and who is inside at each shift change. Check that the people and tickets on permits match, and that open work, gas tests and handovers are recorded correctly. Use any differences to fix your records or mapping before you depend on the new system alone.
- 5
Stop using iPermit
When the board, isolations and who is inside match at every shift change, stop raising permits in iPermit. Make sure the team knows which system is now used for new permits and that active work has been checked and reissued in the new system. Keep any iPermit records you still need to retain according to your site's recordkeeping requirements.
Where the real effort goes
The main work is usually mapping your own fields and rules, then deciding how much permit history to bring across. The import uses a training matrix and permit register, but IAMTech does not publish a spreadsheet format, so getting and matching the right columns takes attention. If you have Enterprise DNA run the system, they handle this mapping work with you.
Not ready for a call?
Get your IAMTech iPermit switch plan by email
We will send you the step-by-step plan for moving your business off IAMTech iPermit, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your IAMTech iPermit switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Choose who builds and runs your version
Open source
Do it yourself
Free code. Your hosting and agent costs.
- 1 Clone the repo, run npm install and npm run demo
- 2 Open it in Claude Code, Codex, OpenCode or Cursor and type /start-of-shift
- 3 Add your areas, plant and isolation points, then dry-run your iPermit training matrix and permit register
- 4 Set your permit kinds, gas limits, fire watch time and clash rules
Built around your business
We customise it
One setup fee, then an agreed retainer
- check Your permit kinds, isolation points, clash rules and ticket list, from your site procedure
- check Your iPermit people, tickets and permit history brought across and checked
- check A phone screen for crews to sign on, test gas and log entries, with signatures and photos, if you want one
- check Your maintenance system and training records connected
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed and operated through Omni by Enterprise DNA
- check Start-of-shift and lockout checks done and sent to your coordinator
- check Contractor renewals chased before they lapse
- check Your monthly permit audit written for the safety meeting
Questions
Instead of IAMTech iPermit, answered
Our crews sign on and test gas on their phones in iPermit. Do we lose that? expand_more
The free version is run by whoever coordinates permits: they record sign-ons, gas readings and entries, and the permit, isolation certificate and entry log print for the job. If your crews work from phones, Enterprise DNA builds a phone screen into your version, with signatures and photos, on the same records.
Is a rule check here a substitute for our permit to work procedure? expand_more
No. It checks what is recorded against the rules your site sets, each with its source: the oxygen and flammable gas limits for entry, standby and rescue before a confined space entry, isolation proved dead before work, tickets for each role. Your procedure, your competent people and your regulator still decide what is safe. What it does is catch the stale gas test and the lock left on before someone relies on them.
How do our records come out of iPermit? expand_more
IAMTech says permits download as PDF, and that iPermit connects to SAP PM, IBM Maximo and other systems through its interface. It does not publish a spreadsheet format. Ask IAMTech or your administrator for the training matrix and the permit register as spreadsheets. Mapping their columns is part of what Enterprise DNA does. Open permits come across as requested, to be isolated, tested and issued again, so nobody inherits an isolation they did not see applied.
What about permits for work we do not have, like asbestos or radiation? expand_more
Permit kinds are a list your site owns. Adding one, with the ticket its crew needs and whether it needs isolation, a gas test, a standby or a fire watch, is a plain request in your own words. The same goes for your gas limits, your fire watch time and which permits must not run side by side.
We are partway through an iPermit licence. When should we switch? expand_more
Use the time left. Set up your plant and isolation points, bring your people and tickets across, then raise every new permit in both for a week. When the board, the isolations and who is inside match at every shift change, stop raising permits in iPermit.
Show Sam your isolations and who is inside today
In a 30-minute call, walk Sam through how your site raises permits, isolates plant and keeps track of contractors today, and the check you wish your permit system did. Sam will scope your version and what it takes to bring your iPermit records across. If it fits, we build it and run it. If not, the free version is yours to keep.
Permit to Work for Claude Code is free and open source, published by Enterprise DNA.
Done paying for IAMTech iPermit?
Get your version built