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; an administrator sees who is overdue.
- Authors
Write and submit
Upload a PDF or Word file. 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, the step and the time stay on the record of that 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, and the one account we name. Adds everyone else, decides what each may do, names the administrators, and answers for who has access. Enters a Google Authenticator code at every sign-in.
Details that matter in a survey or an audit
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.
Decisions have names
Every approval decision records who, at which step, 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.
Easy to retrieve
Approval, review, version and acknowledgement records sit with the policy, so they are quick to find when an auditor, surveyor or accreditation reviewer asks for them.
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 reviewer 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.
- From then on
The loop runs on its own. Review dates come round and owners are emailed 90, 60 and 30 days ahead. Each new version asks its readers again. The overdue lists are the two screens an administrator opens.