Know what happened, and where it came from.
How it works
A record that builds as work happens.
Nobody has to write anything down. The history is kept as obligations and reminders change.
01Source
An obligation records where it came from: a document, an asset or a policy.
02Evidence
Obligations from documents keep the page and the original wording.
03Change
Owners, dates and states are changed by people on your team.
04Record
Each change is added to the obligation’s activity with who and when.
05Review
Open an obligation to see its history, or the workspace Activity page for reminders.
06Attach
Attach files to a reminder, such as a certificate or a policy document.
Source evidence
The requirement, at its source.
See which document, asset or policy an obligation came from. For documents, the page and the original wording are kept next to it, with how confident the analysis was.
Source evidence means provenance
It shows where a requirement came from. It is not proof that the work was completed.
Activity
Who changed what, and when.
Each obligation shows its activity history. The workspace Activity page lists what has happened across your reminders.
Reminder attachments
Keep the relevant file with the reminder.
Attach a file to a reminder, such as a certificate or a policy, so it is at hand when the reminder is.
Used for
Compliance Management
Turn policies, regulations and internal requirements into accountable, trackable obligations.
Policy Obligation Management
Turn policy requirements into owned work with reminders and an activity history.
Employee Credentials
Monitor professional licenses, certifications and required employee documentation.
Important deadlines shouldn’t live in someone’s head.
Give every obligation an owner, deadline and plan.
No credit card required.