Skip to content

Run a checklist and review its history

Tick off a checklist or record its results when it's due, submit it for sign-off, and keep a timestamped record of every run.

Each time a checklist is due, everyone assigned to it gets their own copy, called a run, to tick off. When it’s done, they submit it, and an approver signs it off. Every run is kept with who ticked each task and when, so you can show that the work was done.

  1. Click Checklist in the sidebar. My checklists shows what’s due:

    • A yellow banner lists any checklist due today or overdue that you haven’t submitted.
    • Due now has each checklist due in its current day, week or month.
    • The calendar marks the days something is due. Click a day to see what was due, and start one you missed.
    • My runs lists everything you’ve started or submitted.
    My checklists: a banner saying 1 checklist needs attention, a calendar with the due days marked, Due now highlighted with Daily clinic opening and a Continue button, and My runs listing today's run In progress at 4/6 and earlier runs Approved at 6/6
    Due now is where you start today's checklist.
  2. Click Start next to the checklist, or Continue if you’ve already started it.

  3. Tick each task as you do it. Wikidoc records who ticked it and when. Tasks marked * are required.

    Some tasks ask for a result instead of a tick:

    • Pass, Fail and N/A buttons: click the result. To take it back, click it again.
    • A reading box: type the reading and press Enter, or click away, to save it. The acceptable range is shown next to it.
    Grace Kim's Weekly equipment safety check, In progress with 1 failed: the treatment tables and resistance bands checks marked Pass, the ultrasound unit marked N/A, each recorded by grace.kim with a time, and the hot pack heater reading of 152 °F shown in red as out of range, with her note
    Each result is recorded with who and when, like a tick.

    A Fail, or a reading outside the range, turns the task red and asks What was done about it? Say what you did, such as taking the equipment out of use or telling your manager. A reading shows Out of range as you type it, before it’s saved, so you can check it.

    The hot pack heater task, in red: a reading of 152 °F with Out of range (160–175 °F) highlighted, and under it What was done about it? Needed to submit, filled in with Took the hot packs out of use and asked Marcus to book a service
    A failed task needs a note before the run can be submitted.

    If a task asks for a photo, click Take photo under it. On a phone it opens the camera; on a computer, choose an image. Add up to five photos to a task, and click × on one to remove it. Tasks marked Photo required need at least one photo before you can submit. Location and other details are removed from each photo before it’s uploaded.

    If something stops you finishing a task, such as broken equipment, click Create a task next to it to hand the problem on as a task.

    On the Team plan, if something went wrong or was found wrong, such as a failed check or a reading out of range, click Report an issue next to the task. The issue records the checklist, run and task it came from, and its owner works out the fix. See Report an issue.

  4. When every required task is done and has its photos, and every failed task has a note, add a note for your reviewer if you want to, and click Submit for review. A failed task doesn’t stop you submitting: the run records what you found.

    A Daily clinic opening run, In progress: 4 of 6 tasks done with 2 required remaining, four tasks ticked with who checked them and when, two unticked tasks each with Create a task, and the Submit for review box saying 2 required tasks must be checked first
    Submit for review turns on once every required task is ticked.

Your approvers get an email and a notification. The run shows Pending review until one of them decides, and you can’t change it in the meantime.

On the Team plan, a task can be set to raise an issue when it fails. The task says A Compliance issue is raised for this when you submit. When you submit, the failed task is reported in Compliance as an issue from you, with what you recorded and your note, and your Admins and Managers are told so someone can take it on. It’s reported once, even if the run is sent back and you submit it again.

You can leave a run and come back to it. Ticks save as you go, so there’s nothing else to save.

If you’re an approver, submitted checklists wait for you in the Review queue tab, with a count next to it.

The Review queue tab, showing 1, with a Daily clinic opening run submitted by mia.lopez, 6/6 tasks, Pending review
The Review queue lists every run waiting for your sign-off.
  1. Click a run to open it, and check what was ticked and when. Failed tasks are red, with the note saying what was done.

  2. Under Review this checklist, add a note if you want to, then click Approve or Reject. When you reject a run, say in the note what needs fixing.

    Mia Lopez's run under review: every task ticked with a time, and the Review this checklist box with an optional note, Reject and Approve highlighted
    Approve signs the run off; Reject sends it back.

The person who filled it in is told either way. A rejected run goes back to them with your note, to fix and click Resubmit for review. You can’t approve a run you filled in yourself.

A run can be opened by the person who filled it in, the checklist’s approvers, owners and creator, and Managers and Admins. Any of them can add a comment under Comments, or reply to one. Click Resolve when a comment has been dealt with.

Audit trail, at the bottom of every run, lists everything that happened to it, in order: when it was started, each tick and result, the submission, the decision and the notes.

On the Templates tab, click ⋯ next to a checklist, then History. Every run is listed, newest first, with who filled it in, when it was submitted and its status. Click one to open it.

Run history for Daily clinic opening: runs by tom.fletcher and mia.lopez over several days, one In progress, one Pending review and the rest Approved at 6/6
The history is your record of the checklist being done, day by day.

To keep the history outside Wikidoc, for an inspection, click Export CSV above the list. See Export a checklist or its history.

A period no one submitted shows as missed on the checklist, and as Overdue on any obligation the checklist meets in Compliance. On the Team plan, an Admin or Manager can also have each missed period raise an issue: open the checklist in the editor and, under When a period is missed, choose Raise a Compliance issue, with its owner and how serious it is. It’s off unless you turn it on, and counts only periods from the current day, week or month on, never earlier ones. A run of missed periods goes on one issue while it’s open. See Fix an issue.

Submit for review is grayed out. Some required tasks aren’t done, need a photo, or failed and need a note. What’s left is shown next to the button.

“Enter the reading as a number.” Type only the number, such as 4.5, and leave out the unit. A comma works as the decimal point too.

I can’t untick a task or change a result. A run can’t change while it’s waiting for review or after it’s approved. If it’s rejected, you can change it again.

Nobody reviewed my checklist. It may have no approvers. Ask whoever manages the template to add one. See Build a checklist template.