Skip to main content

Checklists overview

What it is used for​

Checklists help teams complete repeatable work. OpusHub separates the reusable template (the design) from the live active run (today's instance). Editing the template changes future runs; editing an active run changes only that one.

Who can access it​

Users can access a checklist when they have the right combination of organisation, group, user or per-checklist permission. Managers and admins usually see more actions.

How the Checklists page works​

  1. Select Checklists from the left navigation.
  2. Use the Active tab for live runs that need work today.
  3. Use the Templates tab for the reusable designs.
  4. Use search and filters to narrow the list by checklist name, group or department.
  5. Open a checklist card to view or work on it.

The page splits into My Checklists (your favourites) and All Checklists (everything you can access). Active checklists are sorted by created time. Templates are sorted alphabetically.

What a checklist contains​

  • Sections and tasks. Tasks can be grouped or left uncategorised.
  • Custom fields. Capture extra data per task on every run. See Custom fields.
  • Schedule. Frequency, start date and day-of-month settings decide when new runs open. See Scheduling.
  • Permissions. Public, private, plus user, group or role-based permissions. See Roles and permissions.
  • Close behaviour. Manual, automatic at a set time, or automatic before the next run.

Important notes​

  • A checklist can be public (visible to everyone in the org) or private (visible only to listed users, groups or roles).
  • Active runs show sync status. Offline edits are queued and synced when the device reconnects.
  • Closing an active run that still has incomplete tasks logs a "closed without completing" notification.

:::info Screenshot placeholder Add screenshot: Checklists page showing Active and Templates tabs, search, filters, and My Checklists vs All Checklists. :::