.png)
Create recurring compliance checklists with fresh runs, timestamped task completion, approval records, and an immutable audit trail.
From scratch, from your existing spreadsheet, or generated from an existing SOPs by AI.
Pick assignees, approvers, and cadence. Each period issues fresh runs automatically.
Assignees work through timestamped items and submit when the required ones are done.
One template describes the recurring job: what must be done, how often, by whom, and who signs off. Wikidoc handles the calendar.
Daily, weekly, or monthly cadence with timezone-aware period boundaries
Required vs. optional items, grouped into sections
Named assignees and approvers who review each cycle
Most teams already have checklists in spreadsheets, in SOPs, in someone's head. Wikidoc meets them where they are.
Manual editor for new procedures
Convert the spreadsheet you run today into a governed template
Let AI turn existing SOPs into the checklist items instantly
Each period, each assignee gets a new, unticked run. Past runs are never reset, never overwritten - each one is a self-contained audit artifact that snapshots the items as they were.
Timestamped ticks - who checked what, exactly when
Submit for review once required items are done
Approve or reject with a note. Rejected runs reopen for fixing
The event log is append-only. Unticking an item adds a record, it doesn't delete one. Comments can be resolved but never removed. That's what tamper-evident means.
Every event recorded - ticks, unticks, submissions
Actor + timestamp on every entry
Comments are permanent. No delete button by design
Assignees see what's due; approvers see what's waiting. Nobody chases anybody down a hallway.
My runs: every checklist assigned to you, current and past, with status
Review queue: submitted runs waiting on you, with a live count badge
Email notifications when a run is submitted to you or decided on yours
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.
Michael
Small Business Owner
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. 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.
Three ways: 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.
Every event: run creation, each item checked or unchecked (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.
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 artifacts even after the template is edited or archived. Templates keep their own version history too.
