Set it up once and it runs on schedule
One template sets the job, how often, who does it and who signs off. Wikidoc handles the calendar.
Recurring checklists that record who did each item and when, and who approved it, in an audit trail that can't be edited.
Copying steps from SOPs, tracking who completed them, and figuring out what happened later takes hours. Wikidoc turns your procedures into recurring checklists that log themselves so you can focus on getting the work done right.
Start from scratch, a ready-made template or a spreadsheet, or let AI draft it for you.
Pick assignees, approvers, and cadence. Each period issues fresh runs automatically.
Assignees tick tasks, record pass or fail checks and readings, and submit when the required ones are done.
One template sets the job, how often, who does it and who signs off. Wikidoc handles the calendar.
Convert a spreadsheet, let AI pull items from an SOP, or start from a ready-made template.
Mark a check Pass, Fail or N/A, or record a reading such as a fridge temperature. A fail needs a note on what was done.
Each period brings a fresh run, or start one per job or new hire. Past runs stay untouched as audit records.
An append-only log: unticking adds a record, and comments are never deleted. Export it as a CSV for an inspection.
Assignees see what is due, approvers see what is waiting, and an email reminds them.
Studio open, close, and equipment rounds on a daily cadence, with reformer springs and cleaning signed at the time by whoever actually did them.
Daily opening and closing checklists per store, with refrigeration temps and cash counts timestamped, inspector-ready without a binder.
Month-end and engagement close-out lists with named approvers and self-approval blocked, so the review step stops being the thing that slips under deadline.
Generate the room-turnover checklist from the protocol document itself, so the list and the SOP can't drift apart every time the protocol changes.
Free to download as PDF or Word, or open in Wikidoc and assign it to your team.
Checklist
Security, equipment, amenities and cash at open and close.
PDF · Word · CSV
Checklist
Cleaning by station, after every service, weekly and monthly.
PDF · Word · CSV
Checklist
Hands, tools, linen and single-use items between every client.
PDF · Word · CSV
Checklist
Cut-off, reconciliations, accruals and reports, in the same order monthly.
PDF · Word · CSV
Every checklist is connected to documents, owners, process maps, and analytics.
The SOP your checklist was generated from - same source of truth.
See where each recurring check sits in the end-to-end process.
Completion and compliance rates across the whole org, in one dashboard.
A Wikidoc checklist is a recurring compliance record, not a task list. A template defines the items, cadence, assignees, and approvers; each period every assignee gets a fresh, unticked run. A checklist for one-off work, such as an inspection, a job or a new hire, runs when you start it instead, named and dated, with each task due on its day. Every tick, untick, submission, approval, and comment is recorded in an append-only event log with actor and timestamp - evidence the procedure was actually followed.
Five ways: describe your business and AI drafts several recurring checklists at once, for you to review and edit before they're created; pick a ready-made template from the template library, which sets up all its checklists at once, such as a clinic’s opening and closing checklists; build it manually in the template editor; upload an existing CSV or Excel checklist; or point AI at one of your SOP documents and it drafts the checklist items for you.
Yes. A task can be ticked, answered Pass, Fail or N/A, or record a reading with its unit and the range it should be in, such as a fridge at 2–8 °C. You set the range from your own plan or the rules where you work. A fail, or a reading outside its range, turns red and needs a note on what was done before the run can be submitted, so the record shows the problem and the response together. On the Team plan, a failed task can also raise an issue in Compliance for someone to follow up.
Every event: run creation, each item checked or unchecked and each result or reading recorded (with who and when), submission (including which approvers it went to), approval or rejection decisions with notes, reopening, and every comment, reply, and resolution. Events are append-only - unticking adds an event rather than erasing history, and comments cannot be deleted. For an inspection, export the run history as a CSV for any date range: one row per task per run, with who did it, any result or reading and its note, who submitted the run and who approved or rejected it, and why.
No. Self-approval is blocked. The decision maker must be a named approver or admin who is not the run's assignee. Rejected runs reopen so the assignee can fix and resubmit, with the full cycle recorded.
Nothing - each run snapshots the template items at creation, so past cycles remain exact audit artefacts even after the template is edited or archived. Templates keep their own version history too.