The platform
A measuring instrument, not a filing cabinet.
Every register in one system, checked continuously against the standards you hold — and honest about the requirements it cannot evidence for you.
58
automated checks, on ISO 9001, 14001 and 45001
80
requirements mapped across 12 standards
11
of the 80 cannot be evidenced by software — a person has to be there
What is in it
Ten registers, one engine.
They are not ten products bolted together. Every register is configuration over the same engine, which is why a new one does not mean a new release.
Risk and hazard
Incidents and nonconformance
Corrective actions
Competency and tickets
Plant and equipment
Suppliers and contractors
Internal audits
Management review
Standards and requirements
How it behaves
The parts that matter are the refusals.
Anything can store a document. What decides whether an audit goes well is what the system declines to record.
01
It checks itself
Fifty-eight checks run against your own register and report what a certification body would find — an expired ticket, a procedure pointing at a withdrawn document, a nonconformance closed without anyone verifying the fix.
02
It refuses to record a lie
A nonconformance cannot be closed while its corrective action is unverified. A document cannot be approved without the file behind it. The system will not let you write something you would have to defend later.
03
Your data stays yours
Your own database, in your own account, in Australia. Not a tenant in a shared system. Leaving means we hand it over, not that you export what we allow.
04
Bring what you already have
Your document register, your training matrix, your plant list — imported from the spreadsheets you already keep. Nothing reaches the register until you have seen exactly what will change.
05
Built for an auditor
Give an auditor read-only access for the window of the audit. Everything they open is logged and you can read it. When the window closes, access stops on its own.
06
Unlimited users
Priced by site, not by seat. Put your whole workforce on it — the supervisor who logs in twice a month costs nothing extra.
What no software can evidence
Eleven of the eighty cannot be evidenced by software.
Not by this system, and not by any of them — a person has to be there. This is a limit of the category rather than a gap in the product, so no future release closes it, and counting these as covered would be dishonest in the direction that flatters us.
| How it is evidenced | Requirements | What that means |
|---|---|---|
| Held in the system | 69 | The record is the evidence, and it is there before it is asked for. |
| Somebody on site | 7 | Someone has to physically stand in front of it and look. |
| Witnessed on a call | 4 | A person still has to watch it happen, but not from the same room. |
11 of 80 need a person — 7 on site, 4 on a video call. The system names every one of them and reports them separately, and it will not pretend to have covered them.
Why this instead
The real competition is a shared drive.
Not other software. Most contractors already have a system — it is folders, spreadsheets and one person who knows where everything lives.
How it works now
- Nobody is certain which revision is current
- Expired tickets are found during the audit
- Corrective actions are closed by saying they are closed
- The week before an audit is spent assembling evidence
- It all depends on one person still working there
How it works here
- One current revision, and the history behind it
- Expiries reported weeks out, on the page you already open
- Closure refused until somebody verifies the fix worked
- Evidence is assembled continuously, not the week before
- The system holds the knowledge, not a person
See it running
Four minutes, no sign-up.
Not recorded yetThe walkthrough is filmed against the demo system once its dataset is finished — four minutes, no sign-up, a real system with real records in it.
Not shipping yet
What is built but not in the product.
Listed because a roadmap presented as a feature list is the same defect as a requirement counted as covered.
In testingThe Studio is built and being tested. It is not part of the shipped product, it is not installed on any client instance, and nothing you are quoted for depends on it.
Everything the platform does today is deterministic. The fifty-eight checks are database rules that produce the same answer every time they run, and nothing in the product calls a language model.
Automation
System automation — the paperwork, not the plant.
Alongside the system we automate the admin around it. To a civil contractor “automation” means robot arms and a production line; this is the data entry, the reporting, the forms and the chasing. We map it before we build anything, and deliver it in pieces you can use rather than one system at the end.
What it takes off the week
Assembling evidence before an auditSystems
Chasing expired tickets and competenciesSystems
Typing the same data into three placesSystems
Building the monthly report from scratchSystems
See it with your own register in it.
Send a sample of what you keep today and we will show you the same information running in the system.