Platform
Every obligation you carry, with a name against it
One register of what you are required to do, per jurisdiction, with an owner and the evidence you are actually doing it - instead of a matrix in Excel that went stale the day it was finished.
What is a compliance obligations register, and why do spreadsheets fail at it?
It is the list of what the law, your licences and your contracts require you to do, each with the jurisdiction it comes from, who owns it and how often it has to happen. Spreadsheets hold that list well and prove it badly. They cannot tell you whether the obligation was met last quarter, they do not link to the evidence, and the moment you operate in more than one jurisdiction the matrix becomes columns nobody maintains. Frontline holds obligations as records with owners, review frequencies and evidence attached, so 'are we meeting this' is a state on the register rather than a research project.
- Obligations carry the jurisdiction they come from
- Every one has an owner and a review frequency
- Evidence attaches to the obligation, not a folder beside it
- Overdue is visible on the register, before an audit finds it
- 1
- register across every state and country you operate in
- 0
- obligations without a named owner
- 24h
- from your matrix to a live register
- 100%
- of obligations carry a review date
The problem
The matrix was right the day it was written
Most groups have an obligations matrix. It is usually excellent, and usually a year old.
It gets built properly once, often by someone who has since left, and then the business changes around it. A new state, a new licence condition, a venue that opened under a different regulator. Nothing in a spreadsheet notices, so the register quietly stops describing the company.
The deeper problem is proof. A matrix tells you what you are required to do. It does not tell you whether you did it, which is the only question a regulator or an auditor is actually asking.
- Obligations that carry their jurisdiction, so a new site inherits the right ones
- A review frequency on every obligation, and a state when it lapses
- The evidence attached to the obligation it proves
What it does
What you must do, who owns it, and what proves it
Import the matrix you have
Send the spreadsheet. We keep your obligation IDs and your structure, so existing references still resolve and nobody has to relearn a register they wrote.
Jurisdiction as structure
An obligation belongs to a jurisdiction, not a tab. Sites inherit what applies where they are, which makes expanding into a new state a configuration rather than a rebuild.
Owners and frequencies
Every obligation has a person accountable and a cycle. Overdue is a state on the record, not something discovered when someone opens the file in March.
Evidence bound to the obligation
The inspection, the certificate, the training record or the return that proves it, attached to the obligation itself rather than filed near it.
Rules that resolve
Where obligations depend on role, site type or licence, they resolve rather than being copied per site. One customer's training matrix became 924 rules the system applies per person.
The audit view
What we must do, who owns it, when it was last done and what proves it, as one view. That is most of what an audit asks for.
How it works
From your matrix to a live register
Send the matrix
Excel, Word, or a policy document. Multi-tab and multi-jurisdiction is the normal case, not the hard one.
We map obligations to jurisdictions and owners
Your structure, your IDs, your wording. The register should still read like yours when we hand it back.
The gaps surface
Obligations with no owner, no review date, or no evidence behind them. That list is usually uncomfortable and always useful.
It stays current
New sites inherit the obligations for where they are, and evidence lands on the obligation as the work happens rather than at audit time.
Included
What you get on day one
- Your obligations matrix imported, with your IDs kept
- Jurisdiction on every obligation
- A named owner and a review frequency
- Evidence linked to the obligation it proves
- Overdue and approaching states on the register
- Site inheritance by jurisdiction
- Full change history
- An audit view answering what, who, when and proof
Questions we get asked
We operate in Australia, New Zealand and the US. Does one register cover that?
Yes, and that is usually why people move off the spreadsheet. Obligations carry their jurisdiction and sites inherit what applies where they are, so a new country means new obligations rather than a new file.
Do you provide the obligations, or do we?
You do, and we import them. We do not sell a legal content library, and we would not want you relying on one you had not reviewed. If you already subscribe to a service that provides obligation content, it imports the same way.
How is this different from a compliance calendar?
A calendar tells you something is due. A register tells you what you are required to do, who owns it, whether it happened and what proves it. The due dates fall out of the register rather than being the whole of it.
What happens when an obligation is missed?
It shows as overdue against its owner, with the history of when it was last met. That is a state you can act on, rather than a gap an auditor points at later.
See your own obligations, live.
Send the matrix you keep now. When your spot comes up we show you which obligations have no owner and no evidence.
- We take a few teams at a time
- Your IDs and structure kept
- Multi-jurisdiction from day one