
For compliance-heavy businesses
Having the right policy is half the job. Wikidoc connects each policy to the training behind it, the checks that show it was followed, and the records an auditor asks for, so the evidence builds up as the work gets done.
Each policy has an owner, the current file and a review date, with a reminder on the owner's Home page well before the policy goes stale.
They learn the current procedure, pass the quiz and sign that they have read it. The record shows which version they signed, and when.
A cash-handling checklist with required items and manager sign-off. It can't be submitted until every required item is ticked.
Read-only access through a portal, plus exported records of training, signatures and checks, instead of a week of preparation.
Example
A small business has a cash-handling procedure that needs training, a daily check and a manager's sign-off. The policy owner keeps it in Registers with a yearly review date. Staff take a short module and sign that they have read it. Every evening a closing checklist records the count and the variance, and the manager approves it. When the auditor visits, the month's evidence is already there.
We won't claim it satisfies any specific body; that depends on your obligations. What Wikidoc produces is the evidence they ask for: approved current procedures, version history, training records and a timestamped record of who did and checked what.
Checklist events go into an append-only log that is never edited or deleted, and each run keeps a copy of the checklist version it was run against.
You can share procedures and training through a portal, where guests sign in with their email and never take a seat. You can also export training, signatures and checklist records.
No. Keep the systems you rely on for HR records or incident reporting. Wikidoc covers the procedures, the training and the routine checks around them.