Why we are building it
Every EHS professional we have spoken to describes the same afternoon: an inspector, an auditor or a lawyer asks a simple question, and answering it means assembling evidence from systems that were never designed to be joined. The control existed. The training happened. The permit was authorised. Proving all three, in order, with dates, is the hard part.
So TrackSHEQ is organised around the record rather than around the form. One organisation, one set of sites and people, and every module writing to the same audit trail — so a permit, an incident and a competency point at each other instead of living in three tools with three exports.
It is also built multi-tenant the expensive way. A database, a storage bucket and an identity organisation per customer costs us more to run than one shared database with a customer column. We think that is the correct trade for records that matter this much.
How we intend to behave
Say what is built
This site marks which modules are live and which are rolling out. We would rather lose a deal than win one on a feature that does not exist yet.
Isolation is not negotiable
It is the one architectural decision we will not trade away for margin. Your records stay in your database.
Your data is yours
Exportable, and no dark patterns on the way out. Software should be kept because it is good.
Plain pricing, plain answers
One rate, published. No tiers engineered so that the feature you need sits one band above you.