Requires Compliance Operations
Make recurring compliance work clear and accountable.
A checklist is a group of tasks. Both show up on the same page, and a checklist always reads as a checklist rather than as loose work that happens to share a due date. An administrator opens Tasks to see what the pharmacy owes; a technician opens it to see what they owe today.
Step-level completion
Checking a box should mean the thing actually happened.
Steps that need evidence ask for it. Steps that depend on an acknowledgment check the acknowledgment. A step that says a policy was acknowledged will not close until the acknowledgment is on file, because a checklist that can be honestly completed without doing the work is worse than no checklist.
- Recurring or event-triggered checklists, and one-off tasks.
- Assignment by role, by individual, or by location.
- Proof uploads on the steps that need them, inspected before they are stored.
- Waiving, with a reason, and only by an administrator or chain staff.
- Completion status visible to managers and administrators without asking anyone.
Opening checklist
Daily · assigned to the pharmacist on duty
- Record refrigerator temperatures2 of 2 units
- Check will-call for expired fills
- Photograph the C-II count sheetProof required
- Acknowledge: Immunization protocol v4Acknowledgment must be on file to close
- Confirm the alarm is set
Where it gets used
The work that currently lives in somebody’s head.
Onboarding
A new technician's first two weeks as one list rather than four departments each holding a piece. CPR card, license, system access, policy acknowledgments, with the pharmacy able to see what is still open.
Recurring operations
Opening and closing routines, cold chain logs, C-II counts, seasonal work. Built once as a checklist, recurring on the cadence you set, appearing as one occurrence per period.
Location audits
A store audit and the corrective work that follows it, tracked in the same place, with the completion status visible to managers and administrators without asking anyone.
Where tasks come from
Some of them raise themselves.
Publishing a policy that asks for a signature raises the acknowledgment tasks. A policy reaching its review date raises a review task, assigned to whoever wrote it if they are still there. A locked policy arriving from a chain with blanks still in it raises a task to fill them, rather than an acknowledgment nobody could honestly sign.
A policy review closes in one of two ways, and either restarts the clock: publishing a new version, or ticking off the review task because the policy still says the right thing. Without the second path, the only way to close a review would be to publish a version that changes nothing.
Connected capabilities
Everything here shares one record.
Show us your opening checklist.
Whatever form it takes today: a laminated card, a clipboard, a shared note. We will show you what it looks like with completion attached to it.