The obligation engine
The requirements you must meet, written down and watched for
Legislation, standards, client contracts and your own policies can all be written as rules. The platform watches your records and raises the duty, the review or the action when a rule says it is due.
How a rule works
Three parts, and nothing hidden in any of them: what is required, what the platform looks at, and what it does when the two meet.
Write the requirement down as a rule
A rule says what has to happen, what it applies to, and what makes it due. It can come from legislation, from a standard your organisation works to, from a commitment in a client contract, or from your own internal policy.
The platform watches the records
Rules read the records your people already keep: inspections and their findings, risk ratings, training and licences, contractor documents, permits, measurements, and anything your team has built.
The duty is raised where the work is
When a rule is met, the platform raises the duty, the review or the action, gives it an owner and a due date, and tracks it like any other piece of work. It appears in the same lists and reports as everything else.
What this looks like in practice
The same rule shapes cover most of what an organisation has to keep on top of. These are ordinary examples, not special cases.
A licence falling due
A high risk work licence or a certificate reaches the point you set ahead of its expiry, and the duty to renew it is raised before the work that depends on it is affected.
An inspection finding that fails
A checklist item fails, and the finding becomes a non-conformance with an owner and a due date instead of a note in a completed form.
A risk rating that rises
A reassessment moves a risk into a higher band, and the review that your standard requires at that band is raised without anyone chasing it.
A contractor document expiring
An insurance policy or a worker qualification reaches its expiry date, and the duty to obtain a current one is raised before that contractor is engaged again.
Staying in control of it
Telling an organisation what it is required to do is a serious thing to automate. These are the limits the engine works inside.
Every rule cites its source
A rule carries where it came from: the regulation and the provision where the law sets the requirement, or your own standard, contract or policy where you do. The citation stays with every duty the rule raises, so the reason it exists is attached to it.
Rules arrive switched off
Nothing starts deciding on its own. A rule installs turned off, and somebody in your organisation reads it and turns it on. You can turn it off again. Changing a rule creates a new version, and duties already raised keep the version that raised them.
You remain the duty-holder
The platform raises a duty for a person to deal with. It does not decide that an obligation has been met, and it does not close one for you. Your organisation remains responsible for meeting its obligations, and that is stated with every duty the platform raises.
What is already written for you
Obligation packs cover every Australian state and territory, the Commonwealth, New Zealand and the United Kingdom, across nine hazard families, each citing its source. Anything else your organisation must comply with is encoded with the same rules.
Occupational hygiene is one of the families covered this way. It is not the whole of it, and the engine is not limited to health and safety: a rule can just as easily carry a commitment from a contract, an environmental licence condition or an internal standard.See what is covered.
See a rule written for your own requirements.
Bring a requirement your organisation has to meet. We write it as a rule with you, turn it on in a test workspace, and show the duty being raised against a record.