Enterprise DNA

Instead of Dashpivot

Stop licensing Dashpivot seat by seat. Own your site safety records.

We build your version around the pre-starts, permits and incident reports your crews already fill in, carry your Dashpivot registers across, and keep it running for you. Adding an engineer or a supervisor costs nothing extra.

Dashpivot lists contributor licences from US$25.20 to US$84.60 per user per month, plus US$10.80 to US$16.20 per paid field app user on Pro and above.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the licence pays for

A template builder, billed per person, with the limits set by tier

Dashpivot turns paper forms into digital templates and stores each filled-in form in a register. Underneath, a safety system is a short list of records: people, sites, hazards, events and the actions that close them.

group

Every engineer and supervisor is a licence

Contributor licences run from US$25.20 a user a month on Standard to US$84.60 on Platinum. Anyone with your company email counts as a contributor, and so does anyone on a Gmail or Hotmail address.

groups

A ten licence floor and blocks of three

Firms of 10 to 99 staff start on at least ten contributor licences, and extra licences come in blocks of three. A small civil outfit pays for seats before anyone has logged in.

construction

Field crew seats on top

On Pro and above, a paid field app user costs US$10.80 to US$16.20 a month on top of the contributor licences, depending on the plan.

tune

Tiers decided by how many fields you build

Standard allows 250 template fields, Pro 500, Premium 750, Platinum 1,000. Approval rules, visitor access and single sign-on also wait behind the higher plans.

event_busy

Annual terms you cannot leave early

Sitemate says an annual agreement cannot be cancelled at any time, and a multi-year deal commits you for the full term.

grid_view

One register per form, exported one at a time

Each template keeps its own register. Getting your history out means exporting each one, and the CSV leaves out signature images and sketches.

What your sites get instead

One safety record across every site, with no seat count and no field cap

Headcount

Everyone on the record, nobody on a meter

Staff and subcontractors all sit in the same database at no charge per person, so a new project manager is a name, not a purchase order.

  • check One flat monthly retainer whether ten people or a hundred touch the records
  • check Subbies and their tickets on file beside your own crew, with no visitor licence rules
  • check Add a field or a whole new register by asking for it, with no tier to move up to
  • check The director, the project manager and the safety lead each ask their own questions of the same records

Before work starts

Inductions and tickets checked per site, per person

Ask who is on a project without a current induction or an in-date ticket and the answer comes back by name, worst first.

  • check Missing inductions listed for each project, subcontractors included
  • check Tickets running out in the next sixty days, so renewals are booked before the job needs them
  • check A lapsed ticket shows beside the incidents that person was involved in
  • check A project that has gone two weeks without a toolbox talk comes up on its own

Serious harm

A notifiable event that stays on top until the regulator is told

Log what happened and, when the regulator needs to hear about it, the event leads the morning list every day until someone records the date they called.

  • check No investigation closes without a fix or a written reason for none
  • check The written notice is drafted from the record for a person to check and send
  • check Each hazard lists the incidents it has caused, so the repeat offender is plain to see
  • check Near misses per project across twelve months, so a site that goes quiet stands out

Your history

Every register in one place, and readable by anything

Pre-start, incident, inspection and hazard records land in a single database the business controls, instead of one register per template.

  • check Your Dashpivot register exports brought across and checked, with a trial run before anything is saved
  • check An imported serious harm event with no regulator date goes straight to the top of the list
  • check Hazard registers and incident reports printed from the data under your own logo
  • check Nothing locked away if you stop paying anyone, because the records are yours

Make it yours

Design your own Dashpivot replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Dashpivot 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 Dashpivot data across and run it for you.

Switching

How to switch from Dashpivot

A move usually involves exporting each register, matching your template fields, checking a trial import, and running both systems side by side for a few weeks before you let Dashpivot lapse.

  1. 1

    Export every register

    In Dashpivot, export the register for each template you want to bring across, choosing all columns rather than only the visible ones. Export the safety records you need, and include other registers you want incorporated into your version. The CSV includes the signer’s name, time and date, but not signature images or sketches. If you cannot find the export option, check with Dashpivot.

  2. 2

    Map and load the records

    Dashpivot names columns after fields in your own templates, so the exports need to be matched to the new database before they load cleanly. Have Enterprise DNA map them during setup, or ask Claude Code to map them and do a trial run first. Review the trial before loading the records, so you can correct field matches before bringing everything across.

  3. 3

    Check the import findings

    Review the trial results and confirm the records and fields landed where you expect. Treat the import as a first audit, not just a copy: the system flags imported notifiable events that have no regulator-notified date, putting them at the top of the attention list. Check those records and resolve any gaps you find before relying on the new database.

  4. 4

    Run both side by side

    Keep Dashpivot available while you use the new system for a few weeks. Compare the records you enter and the information you need to find, and check that the fields and rules fit how your business works. This gives you time to catch mapping problems and confirm that the new process works before you stop using Dashpivot.

  5. 5

    Switch and let Dashpivot lapse

    Once you have checked the imported records and are comfortable using the new system, make it your working record and stop relying on Dashpivot. If you are on an annual Dashpivot term, Sitemate says it cannot be cancelled early. Plan the handover around the renewal date and let the term lapse rather than assuming you can end it immediately.

construction

Where the real effort goes

The main work is matching Dashpivot’s business-specific template fields to the new database, deciding which registers and history to bring across, and checking the results. CSV exports do not include signature images or sketches, so decide how to handle those separately. If Enterprise DNA runs the installation, it handles the field mapping and setup as part of that work.

Not ready for a call?

Get your Dashpivot switch plan by email

We will send you the step-by-step plan for moving your business off Dashpivot, 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 switch

Try the free version yourself, or have Enterprise DNA build and run yours

Open source

Do it yourself

Free

  1. 1 Download Health and Safety for Claude Code from GitHub
  2. 2 Run npm run demo, then open the folder in Claude Code
  3. 3 Type /attention to see what needs a decision on the demo sites
  4. 4 Export each Dashpivot register with all columns and map them into the import
Get it on GitHub

Omni by Enterprise DNA

Have Enterprise DNA build and run it

One setup fee, then a monthly retainer

  • check We export every Dashpivot register across your projects, match its columns and check each record arrived
  • check Your pre-starts, permits and incident forms set up in the words your crews already use
  • check Quality checks, site diaries, timesheets or a phone form for the field added if you run them today
  • check Kept running inside Omni, our managed Command Center, alongside the rest of your business
Book a discovery call

Questions

Instead of Dashpivot, answered

Dashpivot also runs our ITPs, site diaries and dockets. Does this cover those? expand_more

The free version is a safety system: incidents, hazards, inductions, toolbox talks, inspections and actions. Quality checks, diaries and timesheets are records too, and Enterprise DNA builds them into your version during setup, in the same database, so you are not left running two systems.

How do I get our records out of Dashpivot? expand_more

Sitemate's help centre shows how to export each template's register as a CSV. Pick the option for all columns, not only the visible ones, and do it for every register you care about. Signature images and sketches do not come out in the CSV, though the signer's name, time and date do.

Will those exports load in as they are? expand_more

Not straight away. Dashpivot names its columns after the fields in your own templates, so every company's export looks different. Matching them is part of Enterprise DNA's setup, or you can ask Claude Code to map them and do a trial run first.

We are part way through an annual Dashpivot term. Is it worth talking now? expand_more

Yes. Sitemate says annual terms cannot be cancelled early, so the sensible plan is to build and fill your own version before the renewal date, run both side by side for a few weeks, and let the term lapse.

Our crews like filling forms on their phones. What do they use? expand_more

In the free version, whoever keeps the safety records works in plain English on a computer. For crews on site, Enterprise DNA builds a simple phone form into your version. However a record arrives, it lands in the database you own.

Stop paying per seat for your own safety record

Thirty minutes with Sam. We look at how many Dashpivot licences you carry, which registers your crews actually use, and what your own version would look like across your projects. If it fits, we build it and run it. If not, the free version is yours to keep.

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

Done paying for Dashpivot?

Get your version built