Product
Built around the one thing every policy has to do: stay current.
A hospital does not need another document store. It needs the loop of approval, acknowledgement and review to run on its own, and a record that shows it did.
By role
Five kinds of people, each with only what is theirs.
- Staff
Read and acknowledge
Your tasks lists what needs you: policies to acknowledge with their due dates, nothing else. Open the document, confirm you have read it, done. Reminders come by email; a manager sees who is overdue.
- Authors
Write and submit
Upload a PDF or Word file, or write in the editor. File it by department, category and type. Send it for approval, see where it is, take it back for changes.
- Approvers
Decide, with a record
One inbox of what waits for you. Approve, request changes, or reject, with a reason. Your name, title and the time become the signature on the version.
- Administrators
Run the library
Staff and roles, workflows, taxonomy, overdue acknowledgements and reviews, the audit log, organization settings. Invite one person or two hundred from a spreadsheet.
- The System Admin
Own the system
The first person in. Adds everyone else, decides what each may do, sets up single sign-on, and keeps the emailed sign-in link as the way back in if the identity provider ever fails.
Details that matter in a survey
The record is the product.
Versions are kept
Publishing a revision keeps the old version readable and the acknowledgements tied to it. Staff never see a draft.
Signatures have names
Every approval decision records who, in what role, at what time, with what comment. It is the signature sheet, without the sheet.
Acknowledgement is per version
A new version asks again. The record says which version each person read and when.
Reviews cannot lapse quietly
Owners are reminded at 90, 60 and 30 days; the administrator sees what is overdue; the nightly job keeps the dates honest.
Audit log
Every change to a policy, a person or a setting, retained and exportable.
Uncontrolled copies
Print and download are allowed and marked. The library is the controlled copy.
Add-ons
Switched on per organization, when the office is ready for them.
Scope of Service
Each department’s scope, owned, approved and reviewed like a policy, because a surveyor reads it like one.
Forms & Attestations
Annual attestations, conflict-of-interest, training sign-offs: assigned, chased, recorded.
Competency & Training
Competencies by role, evidence uploaded by the person, verified by the manager, due dates that chase.
Exceptions & Variances
When practice must differ from policy, on record: what, why, approved by whom, until when.
Getting started
From the first conversation to staff reading policies.
- Same day
We create your organization and name your System Admin. They get an email, sign in with a link, and set up Google Authenticator. Your existing library can be imported from a spreadsheet and a zip of files before anyone else signs in.
- The first ten days
Your System Admin checks the departments, adds staff one at a time or from a spreadsheet, and loads policies with their filing and who must acknowledge them. A getting-started list ticks itself as the work is done.
- When IT is ready
Single sign-on with Microsoft Entra ID, turned on alongside the emailed link first, then required once everyone is through. We warn you a month before the secret expires.