Instead of SiteDocs
Move off SiteDocs. Own your safety records outright.
Enterprise DNA builds your version around your pre-starts, your site inductions and the way your crews sign off work, carries your SiteDocs form history across, and runs it for you. No yearly renewal sized to your headcount.
SiteDocs publishes no prices. It sells an annual subscription quoted privately after a call, based on the size of your company.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
Where the renewal goes
A yearly fee for forms, signatures and the place they are stored
SiteDocs is built around documents: SWMS, JSEAs, pre-starts, inspections and inductions filled in on a device and signed. Each one is a record about a person, a hazard or a job. The subscription pays for the forms layer and the hosting around them.
A price that depends on how big you are
SiteDocs states its subscription is annual and based on company size, and that you need a call before you get a number. Grow the crew and the next renewal is a new conversation.
Forms where you wanted facts
Unlimited forms and signatures is the headline feature. But a signed pre-start is a page. Knowing which hazards keep recurring across those pages means reading them, or working through its analytics.
Certifications tracked inside worker profiles
Certifications live on each worker's profile in the app. The question that matters is the one across all of them: who is booked on site next week with something about to run out.
Your history on a vendor's cloud
SiteDocs keeps records on Microsoft Azure and says signed forms cannot be deleted. That is useful for audit, but it means the full history of your sites lives in an account you rent.
A two-year window if you ever leave
Its FAQ says a business that leaves has two years to remove its data. Your records stay yours, on the vendor's timetable.
Dashboards someone still has to read
Its analytics and reporting show the trends. They do not tell the site manager, first thing in the morning, which three things must happen today and who owns each.
What you get instead
The facts inside your signed forms, kept as records that answer back
Crew and tickets
Know who is cleared before the ute pulls up
Every worker and subcontractor sits on one list with their inductions and certifications, current and past, so the check happens before the job, not at the gate.
- check Certifications expiring in the next sixty days, listed by name and site
- check Anyone working without a current site induction flagged on the daily list
- check A lapsed ticket shown beside every incident that person was involved in
- check Pricing that does not move when you add subcontractors for a busy season
Before the work
Pre-start hazards that carry into the register
The hazards your crews name on a SWMS or JSEA become entries in one risk register, scored on a five by five matrix, rather than lines on a signed page.
- check A high-risk hazard cannot be added without controls written against it
- check Controls that rely only on PPE stay flagged until something stronger is in place
- check Each hazard lists every incident it has led to, across every site
- check Inspections book their next round when they close, and findings become owned actions
When it goes wrong
An incident record that refuses to be quietly closed
Log the event and the system decides whether the regulator has to be told. If it does, the record stays open until the date of that notification is on it.
- check An unreported notifiable event tops the morning list until someone deals with it
- check No investigation closes without a corrective action or a written reason
- check The written notification drafted from the facts, for a person to check and send
- check Near-miss counts per site over twelve months, so silence reads as a warning
Yours to keep
Years of site history in a database you control
Your workers, hazards, events, inspections and training sit in plain records your business owns. Nobody sets a deadline for when you can take them away.
- check Your SiteDocs form exports mapped and loaded, with a test run before anything lands
- check Imported events that should have been reported and were not go straight to the top
- check Branded incident documents produced from the records
- check A phone form for crews in the field built into your version if you need one
Make it yours
Design your own SiteDocs replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from SiteDocs. 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 SiteDocs data across and run it for you.
Switching
How to switch from SiteDocs
The move involves exporting the records you want to keep, matching your SiteDocs fields to the new records, checking a test import and reviewing anything that needs attention before you switch over.
- 1
Export your SiteDocs records
SiteDocs says form data can be exported to CSV, individual forms can be downloaded as PDF, and forms can be mass exported to Dropbox. Export the records you want to keep, including relevant worker and certification records if your account allows. Export options can vary, so check with SiteDocs about what your account can provide and how long you have to collect your data.
- 2
Run a test import
Start with the import test run before loading anything. The import does not take SiteDocs forms as they are. Each business has its own forms and columns, so the records need to be matched to the right places in the new database. On the free version, you can ask Claude Code to handle that mapping. Enterprise DNA does this setup when they run the system for you.
- 3
Review the import findings
Check what the test run flags before you load the records. The import is also a first audit, so it can surface gaps in the history you brought across. For example, an imported notifiable event without a regulator-notified date goes to the top of the attention list after import. Decide which flagged gaps need correcting and whether any history should be added or left behind.
- 4
Run both systems briefly
Keep SiteDocs available while you start using the new database. Use this short overlap to check that the records you need are there and that new safety information is being recorded in the right place. The new system has no web front end, so the person keeping the records works with it through Claude Code in plain language. Make sure the people responsible know which system to use.
- 5
Switch off SiteDocs
Once you have checked the imported records and are ready to keep new records in the new system, stop using SiteDocs for ongoing safety records. Before you close the account, confirm you have collected the history you want to keep. SiteDocs says businesses that leave have two years to remove their data, and signed forms cannot be deleted while they are in SiteDocs.
Where the real effort goes
The real work is usually matching your own SiteDocs fields and forms to the new records, then deciding how much history to bring across. Export availability can affect what you can include, especially for worker and certification records. If you have Enterprise DNA run the system, they handle the field mapping and import setup, and you see a test run before records are loaded.
Not ready for a call?
Get your SiteDocs switch plan by email
We will send you the step-by-step plan for moving your business off SiteDocs, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your SiteDocs switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways in
Try the free version, or have Enterprise DNA build yours
Open source
Do it yourself
Free
- 1 Download the free version from GitHub
- 2 Run npm run demo, then open the folder in Claude Code
- 3 Type /attention to see what needs a decision today
- 4 Ask Claude Code to map your SiteDocs CSV exports into the import
Omni by Enterprise DNA
Have Enterprise DNA build and run it
One setup fee, then a monthly retainer
- check We take your SiteDocs form exports and worker records, map them across and check the result against what you had
- check Your SWMS, JSEA and pre-start templates rebuilt as documents produced from your own records
- check Rules set for where you work, so Australian sites check against their own work health and safety laws
- check Run for you inside Omni, our managed Command Center, alongside the rest of your business
Questions
Instead of SiteDocs, answered
Our crews fill in SiteDocs on their phones. What do they use instead? expand_more
The free version is run by whoever keeps the safety records, by asking in plain language. For crews who report from the field, Enterprise DNA builds a phone form or message flow into your version, and every pre-start or incident lands in the same database.
Can we get our history out of SiteDocs? expand_more
SiteDocs says form data exports to CSV, single forms download as PDF and forms can be mass exported to Dropbox. We start from those exports, plus your worker and certification records, and you see a test run before anything is loaded.
Will a SiteDocs export load straight in? expand_more
Not as it comes. Every business builds its own SiteDocs forms, so the columns differ from one company to the next. Matching them to the right records is part of the setup Enterprise DNA does, or you can ask Claude Code to do it on the free version.
We work in Australia and live by SWMS. Does it know our rules? expand_more
The free version's rule book is written to New Zealand law, with each rule citing its source. In your version Enterprise DNA rewrites those checks for the states you work in, sources kept beside each one. None of it is legal advice.
SiteDocs keeps signed forms that cannot be deleted. Do we lose that? expand_more
No. Your version keeps the full history of your records for as long as you choose, in a database your business owns. The difference is that nobody else decides how long you have to collect it.
Keep the safety program, drop the renewal conversation
Thirty minutes with Sam. We look at what your SiteDocs forms actually capture, what your sites need from them each day, and what your own version would look like. If it fits, we build 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 SiteDocs?
Get your version built