Enterprise DNA

Instead of ecoPortal

Stop renting ecoPortal. Own your health and safety system.

We build your version around how you log hazards, run incidents and track actions, bring your ecoPortal data across, and run it for you. No plan tiers, and the system is yours.

ecoPortal quotes each business privately, with published installs starting around US$5,000 before the subscription, and reviewers note it can become expensive to add modules.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What you are paying for

Most of the bill is forms and dashboards over nine sets of records

The safety record is yours and the law already defines most of it. What you rent is the layer of screens on top, priced by the module, and their own reviewers say where that goes.

paid

A privately quoted, per-module subscription

ecoPortal quotes each business behind a demo call, with published installs starting around US$5,000 before the subscription. Reviewers on Capterra note it "can become expensive to add modules", and every module is another year of rent.

schedule

A configuration project before the first record

Onboarding, register setup, form building and training before a single hazard is on the books. Here the demo takes sixty seconds and your import is one step.

extension

Form builders and workflow screens

The product is the front end: form templates, approval chains, dashboards. The records underneath are hazards, incidents, actions, people and tickets, and you already own them.

dashboard

Reporting you still have to rework

Reviewers report that exporting incidents takes "quite a bit of formatting" before it is report-ready. Here the board pack and the printable hazard register render from the data, in your brand, in one command.

lock

Change requests for your own fields

Enterprise reviewers ask for more control over minor form and field changes. Here a new field is one sentence to your agent: the migration is written, applied and tested in the same minute.

layers

Compliance sold back as modules

The notifiable-event workflow, the risk matrix, the training matrix and the substance inventory are duties the Act and the Regulations already define. The incumbent gates them by tier; here they are eight rules in a file you can read, with their sources.

What you get instead

The same system, over a database you own, with the sharp edges kept sharp

The event

An incident pipeline that will not let a notifiable event slide

Report it the moment it is safe. If it is notifiable, the two duties print on the spot: phone WorkSafe as soon as possible (HSWA s 56) and preserve the scene (s 55). The written notification drafts itself from the record.

  • check A notifiable event cannot be closed until the WorkSafe notification date is on the record, and there is no force flag
  • check An investigation cannot close with nothing changed: a corrective action or a recorded reason, no third option
  • check The scene log becomes the WorkSafe draft and the investigation record, in your brand, never sent by the system
  • check An unreported notifiable event outranks everything on the attention list, every morning, until it is handled

The registers

Hazards, tickets and substances that argue back

The risk register scores on the real 5x5 and knows the hierarchy of controls. The training matrix covers contractors, because overlapping duties do. The substance inventory knows how old every SDS is.

  • check A high or critical hazard cannot enter the register without controls recorded (GRWM reg 6)
  • check PPE-only on a high hazard stays loud on the attention list until the hierarchy has been worked
  • check Every hazard shows the incidents it has caused: the repeat-offender view no dashboard offers
  • check An expired ticket sits beside the incidents that person was involved in, so the sharpest question asks itself

The rituals

The week's safety work as commands, in the trade's own words

The morning attention list, the toolbox talk, the inspection round, the Monday review. Each one is a slash command that reads the record and says the one next action, with the owner named.

  • check Attention lists everything that wants a decision, worst first, ordered by what hurts a person before what costs money
  • check A site quiet past a fortnight on toolbox talks surfaces by itself (worker engagement is a duty: HSWA Part 3)
  • check Closing an inspection schedules the next one, and findings become actions while they are fresh
  • check Compliance checking runs eight rules from the Act and the Regulations against your live records, each citing its source

Your data

a database you own, any agent, and an import that audits as it lands

Runs on a laptop with no software install, or on your own shared system for the whole business. Works with Claude Code and other assistant tools: your records are the product, the assistant is just the door.

  • check Import people, hazards, incidents and training from ecoPortal or SiteDocs exports in one command, dry run first
  • check The import is the first audit: any imported notifiable event with no regulator-notified date tops the attention list immediately
  • check The near-miss trend per site over twelve months, so reporting drying up reads as the warning it is
  • check MIT licence, plain records, five-year records kept by design (HSWA s 57), no vendor to leave

Make it yours

Design your own ecoPortal replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from ecoPortal. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your ecoPortal replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your ecoPortal 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 Health and Safety for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Health and Safety for Claude Code

Connected to your own database

What needs my decision right now?

Needs a decision (14)

Notifiable unreported

Record
INC-201
Site
Omokoroa Stormwater Upg...
Owner
Steve Callaghan
Days
2
Detail
NOTIFIABLE (notifiable_injury) occurred 2026-09-22 and WorkSafe has n...

Action overdue

Record
Buy pipe lifter and w...
Site
Omokoroa Stormwater Upg...
Owner
Steve Callaghan
Days
6
Detail
due 2026-09-18 (incident INC-202)

Action overdue

Record
Replace damaged guard...
Site
Pyes Pa Ridge Subdivision
Owner
Marcus Tuilagi
Days
1
Detail
due 2026-09-23 (inspection: site_inspection)

Induction missing

Record
Grant Molloy
Site
Pyes Pa Ridge Subdivision
Owner
Grant Molloy
Detail
worker with no site induction on record

Induction expired

Record
Wiremu Beattie
Site
Pyes Pa Ridge Subdivision
Owner
Wiremu Beattie
Days
30
Detail
induction expired 2026-08-25

Hazard uncontrolled

Record
HAZ-103
Site
Omokoroa Stormwater Upg...
Owner
Steve Callaghan
Days
90
Detail
high (15/25): Live road traffic through the work zone is controlled b...

Hazard uncontrolled

Record
HAZ-101
Site
Pyes Pa Ridge Subdivision
Owner
Marcus Tuilagi
Days
18
Detail
high (12/25): Open excavation near live services is controlled by ppe...

Hazard review overdue

Record
HAZ-103
Site
Omokoroa Stormwater Upg...
Owner
Steve Callaghan
Days
21
Detail
high hazard "Live road traffic through the work zone" review was due ...

Investigation stale

Record
INC-202
Site
Omokoroa Stormwater Upg...
Owner
Steve Callaghan
Days
26
Detail
lost_time from 2026-08-29 still investigating: Back strain lifting a ...

Inspection overdue

Record
Site inspection
Site
Omokoroa Stormwater Upg...
Days
9
Detail
site_inspection was due 2026-09-15

Sds gap

Record
Concrete curing compound
Site
Pyes Pa Ridge Subdivision
Days
2200
Detail
safety data sheet dated 2020-09-15, older than five years

Sds gap

Record
Denso bitumen primer
Site
Omokoroa Stormwater Upg...
Detail
no safety data sheet on the inventory

Training expiring

Record
Danielle Priest
Owner
Danielle Priest
Days
12
Detail
first aid expires 2026-10-06

Toolbox quiet

Record
Omokoroa Stormwater U...
Site
Omokoroa Stormwater Upg...
Owner
Steve Callaghan
Days
16
Detail
last toolbox talk 2026-09-08 (16 days ago)

Ask it anything

Questions ecoPortal cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Is there a notifiable event on our books right now that WorkSafe has not been told about, and how many days has it been?
chat_bubble Which corrective actions are overdue, who owns each one, and which of them came out of an event that hurt someone?
chat_bubble Who is on site this week with an expired induction or none at all, including the subcontractors?
chat_bubble Which high or critical hazards are held by PPE or paperwork alone, against the hierarchy of controls?
chat_bubble Which hazards have caused more than one incident, and did the control level actually climb after each?
chat_bubble Was anyone hurt doing work their expired ticket covers, and whose tickets expire in the next 60 days?
chat_bubble Which sites have gone longest without a toolbox talk, and does that line up with where the incidents are?
chat_bubble Which in-use substances have no current safety data sheet on the inventory?
chat_bubble Is our near-miss reporting drying up while injuries hold, per site, over twelve months?
chat_bubble Which inspections are overdue right now, and what did the last one find that never became an action?

Switching

How to switch from ecoPortal

Moving off ecoPortal comes down to an export, one import command, a short stretch running both systems, then switching the old one off.

  1. 1

    Export your registers from ecoPortal

    Export what your ecoPortal account allows, usually CSV or Excel. Check with ecoPortal support on the exact export path for your plan. Pull four registers: people, hazards, incidents and training. These map directly to the fields the import command expects, so keep the column headings ecoPortal gives you rather than renaming anything yourself first.

  2. 2

    Run the import as a dry run

    Point the import at your four files (people, hazards, incidents and training) and do a test run first. It reads your files and reports what it would do without writing anything, so you can see how your ecoPortal records will land before you commit to any of it.

  3. 3

    Run the import for real, then check it

    Run the import again for real this time. The import doubles as an audit: any notifiable event that comes across without a regulator-notified date lands at the top of the attention list the moment the import finishes, so you find out straight away what ecoPortal was carrying that never got reported to WorkSafe.

  4. 4

    Run both systems side by side

    Keep ecoPortal live for a short stretch while your team also works from the new system, logging new incidents, hazards and inductions in both places. This is where you catch anything the import missed or mapped wrong, and where your team gets comfortable typing plain language into Claude Code instead of clicking through ecoPortal's forms.

  5. 5

    Switch off ecoPortal

    Once your team is working from the new register without falling back to ecoPortal, cancel the ecoPortal subscription. Your records now sit in a plain format you own, readable by any tool, with no export request to make and no access ending the day a subscription does.

construction

Where the real effort goes

The export and the import command are mechanical. The real work is deciding how your own fields and rules carry over: your induction periods, your hazard categories, which years of incident history are worth keeping. Getting that mapping right is what takes judgment, and it is the part Enterprise DNA does for you when they install and run it.

Not ready for a call?

Get your ecoPortal switch plan by email

We will send you the step-by-step plan for moving your business off ecoPortal, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Two ways to run it

Run it yourself, or have it run for you

Open source

Run it yourself

Free

  1. 1 Clone the repo
  2. 2 npm run demo, then open the folder in Claude Code
  3. 3 Type /attention
  4. 4 Import your ecoPortal exports and point it at your own database
Get it on GitHub

Omni by Enterprise DNA

Have Enterprise DNA install it

One setup fee, then a monthly retainer

  • check We migrate your people, hazard registers, incident history and training records from ecoPortal or SiteDocs
  • check We write your industry's rituals in as commands: your permits, your plant checks, your client reporting
  • check We tune the rule book to your business: your induction expiry, your talk cadence, your own standards, sources kept
  • check It runs inside Omni, our managed Command Center, with the rest of your business
Book a discovery call

Questions

Instead of ecoPortal, answered

Is it really free? expand_more

Yes. MIT licence. Run it anywhere, change anything, no account with us.

How do incidents get reported from site without an app? expand_more

The supervisor or the operator records it through Claude Code in the time a form takes, and the moment it lands the system does the part that matters: if it is notifiable, the WorkSafe duties print on the spot and the event cannot be closed until the notification is on the record. A phone-based intake path (a shared inbox, a message flow) is a customisation Enterprise DNA builds; the register does not care how the fact arrives.

Does it notify WorkSafe for us? expand_more

No, deliberately. It drafts the written notification from the record with the particulars filled in, and it refuses to let the event close until a person has made the call (0800 030 040) and recorded the date. The one thing that should never be automated is the phone call after someone is hurt.

Is this enough to be compliant? expand_more

It keeps the records the Act and the Regulations name, checks them against eight rules that cite their sections, and keeps notifiable-event records the five years s 57 requires. Compliance itself is how you run the sites, and no software, this one or the incumbent, makes that true on its own. Nothing here is legal advice; the rule book is a file you can read and change.

What does the installed version add? expand_more

Migration from ecoPortal or SiteDocs, your own rituals written in as commands, the rule book tuned to your standards, your team shown the five commands that matter, and someone to call. It runs alongside everything else Enterprise DNA runs for you.

Stop renting screens over your own safety record

30 minutes with Sam. We look at what you pay per module today, what your registers actually hold, and what the installed version would look like for your sites. If it is a fit, we install it. If it is not, take the free version and run it yourself.

Book a discovery call Get the free version

Health and Safety for Claude Code is free and open source, published by Enterprise DNA.

Done paying for ecoPortal?

Get your version built