From documents to obligations
Most tools generate plans. Obliwise also tracks the legal obligations behind them -- which Acts, Regulations and Codes apply to each project, who owns them, and whether they are covered.
The right obligations, by jurisdiction and risk
Obliwise holds a library of legal obligations tagged by jurisdiction, activity and risk. For each project it scopes the obligations that actually apply -- the WHS Act and Regulation for the project's state, the Codes of Practice for its activities, the Standards its risks invoke.
- Acts, Regulations, Codes of Practice and Standards
- Jurisdiction-aware, per project
- Each obligation carries an owner, evidence and a mandatory flag
Links you can stand behind
An AI linker proposes connections between your content and the obligation library, scored by relevance. An admin reviews, accepts or rejects each one. Nothing enters a register on the AI's say-so alone -- the mapping reflects a decision a person made.
- Proposed mappings with a confidence score
- Admin approval queue; rejections stay rejected on re-scan
Coverage at a glance, and a register that builds itself
See which obligations are covered for a project and which are gaps, before you are on site. The legal and obligations registers generate straight from the same data, and stale-document detection flags the plans to revisit when an obligation or its legislation changes.
- Per-project covered / uncovered view
- Live legal and obligations registers
- Legislation change flags the plans to revisit
See your obligations on a real project
Book a walkthrough and we will map a sample project to the obligations that apply, live.
Book a demo