Per-SOP renewal cadence.
Some SOPs renew quarterly, others annually, others never. Listor lets each one have its own interval.
SOP Acknowledgement Software. Nothing leaves your wiki.
SOPs tend to change more often than handbooks, so each one gets its own renewal interval rather than a company-wide annual date. The audit log has who acknowledged which Standard Operating Procedure, with the IP, the user-agent and the round on every entry, and exports as CSV or JSON. Your SOPs stay in Notion, Drive, or wherever they are now.
$2 / user / month. Free for 10 assigned people. No card.No SOP migration · Per-SOP cadence · Self-serve
A new tab for the procedure, and the confirmation waits here until you come back.
Every SOP on its own clock.
The three behaviors that matter for a policy matter for an SOP too, at whatever pace each one needs.
Force re-acknowledgement on change.
SOPs change between renewal windows. One click pushes everyone targeted into a fresh acknowledgement round, with the previous round preserved in the log.
Auditor-grade export.
Who acknowledged which SOP, when, from what IP, and in which round. CSV or JSON, filtered by date range and action type.
The alternatives
Desks or clipboards decides this one.
SOP-tracking tools split into safety / field-ops platforms (SafetyCulture, Connecteam) and link-only acknowledgement tools (Listor). Listor wins when your team works at desks; field tools win for clipboards on factory floors.
| Listor | SafetyCulture | Connecteam | Spreadsheet | |
|---|---|---|---|---|
| Doesn't host your SOPs | ✓ | - | - | ✓ |
| SOP-by-SOP renewal cadence | ✓ | ✓ | ✓ | - |
| IP + user-agent capture per acknowledgement | ✓ | ✓ | ✓ | - |
| Audit-log export (CSV + JSON) | ✓ | ✓ | ✓ | - |
| Built for office workers, not field crews | ✓ | - | - | ✓ |
| Self-serve, free for 10 assigned people | ✓ | - | - | ✓ |
| Force re-acknowledgement on SOP change | ✓ | ✓ | - | - |
Best fit
Ops teams with a wiki and an auditor.
The SOP-specific ones.
Is an SOP the same as a policy for tracking purposes?
From an acknowledgement standpoint, yes: both are documents you need a record that someone read. SOPs tend to update more often than handbooks, so per-document renewal cadences matter more.Where should we keep the actual SOPs?
Wherever you already keep them. Notion, Google Drive, Confluence, SharePoint, a dedicated SOP wiki. Listor stores the URL and the acknowledgement. Never the SOP itself.Can different SOPs have different renewal cadences?
Yes. Each SOP gets its own renewal interval (in months). Quarterly safety SOPs, annual quality SOPs, no-renewal reference SOPs: all coexist.What about field workers who don't sit at a desk?
Listor is web-only and assumes a browser. If your team has shift workers without easy email access, a tool like SafetyCulture or Connecteam is a better fit. Listor wins for office, hybrid, and remote teams.How do we re-acknowledge when the SOP changes?
Edit the SOP document inside Listor (just the title or URL; we never see the SOP contents), mark it changed, and trigger force-reattestation. Everyone targeted gets emailed; their previous acknowledgements stay on the record against the earlier round.Can the SOP renewal happen alongside ISO 9001 / 27001 review cycles?
Yes. Set each SOP's renewal to match your review cadence. The audit log gives the auditor the per-employee, per-round evidence they ask for.Can we see who's overdue without exporting?
Yes. The document detail page shows pending vs. completed at a glance, and the admin dashboard surfaces overdue acknowledgements in the weekly digest email.