Your obligations, written as rules that watch your records.
The obligation engine raises a duty when a rule says it is time, with the source of the rule on the duty. Ready-made rules cover the places we work in, the legal register lists what applies to you, and dashboards and scheduled reports show where you stand, backed by a trail that shows any change.
Works on its ownCompliance and obligations works on its own, so if it is all you need it is all you buy, and every other part of Obliwise stays optional.
What compliance and obligations includes
Everything below comes with it, ready on the first day and yours to change. 17 capabilities
Obligation engine
Your requirements are written as rules and duties appear where people work when they fall due.
Ready-made regulatory rules
Rules written against the legislation where you operate come ready to switch on, each citing its source.
Compliance at a glance
A posture view, a graph of what depends on what, and a point-in-time view show where you stand.
Tamper-evident audit trail
The audit trail is chained so any tampering is detectable.
Standards and frameworks
ISO standards, cyber, privacy, quality and environmental frameworks install as rule sets alongside safety.
Rules kept current
When legislation changes, updated rules arrive for you to accept, defer or decline.
Legal register
The laws, codes and standards that apply to you are listed with what each requires.
US recordkeeping
OSHA 300, 301 and 300A records are kept, certified and filed, with posting and filing dates chased.
US health risk packs
Health risk packs written against OSHA standards for US workplaces.
History you can undo
Every change shows before and after, and reversible changes can be undone as a new, recorded step.
Reports and dashboards
Reports and dashboards are built from any module and shared by role.
Dashboards in every module
Every module has its own dashboard your admins can rearrange.
Scheduled reports
Reports are sent to the right people on a schedule.
Record-keeping duties for notified events
Statutory record-keeping periods for notified events are applied as retention rules.
Installed packs kept up to date
Updates to installed pack content arrive for you to accept, defer or reject.
Ask questions of your data
Ask a question in plain language and get an answer drawn only from data you are allowed to see.
Reports across linked records
Reports and summaries join records across more than one link.
Worked example: a licence rule raises a duty
A forklift licence is two months from expiry.
Step 1: The rule watches the record
The licence rule reads the licence class and expiry on each operator's record.
Step 2: A duty is raised at the point you set
Sixty days out, a duty to renew is raised for the operator's supervisor with the regulation it comes from.
Step 3: The work is flagged
Any permit that names the operator after the expiry date is flagged until the licence is renewed.
Step 4: The trail is kept
The renewal, the new expiry and who recorded it are kept in the history, ready for an auditor.
Read more
Industries that use it
Start with compliance and obligations on its own.
Tell us how many people and locations you have. We will set it up with you, using your own forms and terms, and you add anything else only if you want it.