Controlled documents.Controlled evidence.
Three named people sign every manual into force — reviewer, approver, publisher — and the route locks the moment signing starts. Tell the platform who must read a revision and watch who has. A finding can cite the exact version, and that citation still resolves years later. Bring your existing PDFs in as they are.
Reviewer. Approver.
Publisher.
Every controlled document moves through three named people in a fixed order. No one person can wave a manual into force, and the moment signing starts the route locks — the people and the order can no longer change.
Checks the draft is right and signs to send it forward.
Accepts the content. Cannot be the same person who reviewed it.
Publishes the approved revision and scopes who must read it.
Require a read
when you publish.
In the same step you publish a revision, tell the platform which roles must read it. Each person’s confirmation is recorded against that exact version — so you can see who has read it and who has not, by name, right now.
Your PDF manuals,
brought under control.
You do not have to rebuild your manual library to get control. Upload the PDFs you already have and they ride the same signing route, the same read-acknowledgment and the same review rhythm as a document authored in the platform.
Drop an existing PDF manual straight in. No re-typing, no re-authoring — the file you signed off stays the file.
The uploaded PDF rides the identical reviewer-approver-publisher route, the same read-acknowledgment, the same review cadence as a document written in the platform.
A 50 MB ceiling and a file-type check guard every upload, and downloads come through a private signed link — not a file lying loose in a shared drive.
No document
ages out silently.
A controlled document that is never reviewed is a finding waiting to happen. Every document carries a review rhythm, the owner is reminded ahead of the date, and publishing a fresh revision starts the clock again.
Every controlled document carries a review rhythm — every 12 months, every 24, or a date you choose. The clock lives on the record, not in someone’s head.
The owner is reminded 90 days before the review falls due — once per cycle, automatically. No document quietly ages past its date.
Publish a fresh revision and the review rhythm starts over. Let one lapse and it escalates to the manager — no silent expiry.
The citation
still resolves.
A document is not a file in a folder — it is a record linked to your findings, requirements and training. A finding can cite Ops Manual Part A · Section 5 v3, and that link still resolves after v3 is archived. Four connections that matter on Monday morning.
Sign it. Lock it.
Publish it.
Walk a manual through the four-eyes route, require a read, and watch the citation hold after it is archived — on your data shape, with the founder, in 30 minutes.