Quick summary
- A checklist puts tasks, like signing off a policy, on the staff portal of everyone in the groups and roles you pick.
- When staff sign off a policy on a checklist, Assuric records which version each person confirmed, and when.
- You can’t change a checklist’s audience, Staff or Administrative, once you’ve created it.
What a checklist is made of
A checklist is a set of items assigned to groups and roles. Each item has one of these types:
The portal counts items as “tasks completed”, but they’re not the tasks in Tasks. An item can be done once, or come back on a schedule with its Refresh setting.
Resources items: signing off a policy
Auditors often ask you to show that you gave staff a policy and that each of them confirmed they’d read and understood it. A Resources item does both.- What staff see: each document or file with a link to open it, and an I have read and understood the above resources button that completes the item.
- What you add: an Assuric document or an evidence file. A document is added at its latest approved version, never the working draft, so staff only read a version you’ve approved.
- What’s recorded: each person’s History keeps the version they confirmed and when, which is your evidence. See Show an auditor who has signed off a policy.
When the document changes
A Resources item stays on the version you added. When you approve a new version, Republish options lists each checklist item that uses the document under Update references to past versions → Checklists, in the Approve version dialog or, for a controlled document, Send for review and approval.Who a checklist is for
Once published, a checklist goes to everyone in its Assigned Groups / Roles, so someone in 2 groups gets both groups’ checklists. You choose its Audience when you create it, and can’t change it later:Related articles
Manage and customise your staff portal
Where your published checklists show up for staff.
Roles and groups
How checklists reach the right people.