Costs
Part of A practical reference for building operational checklists that hold up
Choosing operational checklists software vs sticking with paper lists
Operational checklist software judged against paper: evidence, offline use, versioned records, the response loop, and a seven-step trial in the real place.
A checklist on paper costs nothing, cannot crash, and works with wet hands. That is the benchmark any tool has to beat, and most demonstrations never mention it.
There are real reasons to put checklists in software: many sites, evidence that a list was run, and finding out that one is being skipped. This page is how to judge whether a tool earns its place. What the lists should contain is in the operational checklists overview.
Named tools include SafetyCulture iAuditor, Microsoft Lists, GoCanvas, Jotform, Smartsheet, Procore, Intelex, Cority, VelocityEHS, and EHS Insight.
What to take away
- The benchmark is paper. A tool has to beat it on evidence, distribution, or scale, or it is a cost.
- Test it in the real place, on the real device, with the real hands.
- If a completed list produces no visible response, no tool will make the practice stick.
What a tool can genuinely add
Worth paying for when
- Evidence a list was run
- Someone outside asks, or an incident review needs it
- Distribution of a new version
- Several sites, and paper copies would linger
- Skipped-list visibility
- You suspect lists are not being run
- Photographs or readings attached
- The evidence is a state, not a tick
- Trend across many runs
- Enough runs for a pattern to mean something
Test
- Evidence a list was run
- Complete one and produce the record a month later
- Distribution of a new version
- Publish a change and see how the old version disappears
- Skipped-list visibility
- Deliberately miss one and see what surfaces
- Photographs or readings attached
- Attach one on the actual device
- Trend across many runs
- Export the data and look at it elsewhere
Nothing else on a demonstration matters much, and the first row is where most of the value sits.
What checklist software can add
Capability
- Evidence a list was run
- Outside party asks
- Distribution of new version
- Several sites
- Skipped-list visibility
- Suspect lists not run
- Photos or readings
- Evidence is a state
- Trend across many runs
- Enough runs for pattern
Worth paying when
- Evidence a list was run
- Produce record a month later
- Distribution of new version
- Old version disappears
- Skipped-list visibility
- Miss one, see what surfaces
- Photos or readings
- Attach on actual device
- Trend across many runs
- Export and look elsewhere
Test
- Evidence a list was run
- Distribution of new version
- Skipped-list visibility
- Photos or readings
- Trend across many runs
Named tools group into three families. Mobile inspection and form tools include SafetyCulture iAuditor, GoCanvas, and Jotform. General list tools include Microsoft Lists and Smartsheet. Enterprise EHS suites include Intelex, Cority, VelocityEHS, and EHS Insight. Construction project tools include Procore.
| Tool | Provider | Best fit | What to verify |
|---|---|---|---|
| SafetyCulture iAuditor | SafetyCulture | Inspections, actions, offline mobile | Offline sync, versioning, action routing |
| Microsoft Lists | Microsoft | Simple lists inside Microsoft 365 | Version history, offline mobile, alerts |
| GoCanvas | GoCanvas | Mobile forms, PDF output | Offline use, record retention, API |
| Jotform | Jotform | Cheap forms, simple checklists | Offline app, versioning, audit trail |
| Smartsheet | Smartsheet | Spreadsheet-style workflows | Row history, mobile offline, role alerts |
| Procore | Procore | Construction project checklists | Quality and safety modules, offline, versioning |
| Intelex | Intelex | Enterprise EHS, audits | Audit trail, retention, version retrieval |
| Cority | Cority | Enterprise EHS, compliance | Configurability, offline, record retention |
| VelocityEHS | VelocityEHS | Enterprise EHS, ergonomics, audits | Audit trail, versioning, mobile offline |
| EHS Insight | EHS Insight | EHS teams, inspections | Offline, action routing, version history |
Public list prices for small-team tools typically fall between $0 and $50 per user per month, depending on plan and billing. Enterprise EHS suites are usually quoted annually and can exceed $100,000 per year. Implementation for a single site typically takes 2 to 6 weeks. These are typical ranges, not quotes.
Test it where it is used
This is the step people skip and the reason tools get abandoned.
Take the tool to the actual place. Bad signal, gloves, cold hands, a screen in direct sun, a person holding something else. Run a whole list.
If it takes twice as long as paper, it will not be used, and the ticks you eventually see will have been entered afterwards from memory, which is worse than no record at all.
Ask specifically what happens with no connection. A list that cannot be completed offline and synchronised later is unusable in most of the places checklists matter.
Structure, not free text
The question that separates a checklist tool from a notes app: is an item an object with a state, or a line of text?
Items need a completed state, a time, and a person. Lists need a version, so a completed record says which version was run. Without that, an audit trail records that somebody ticked something, and nobody can say what.
Retention is the other half of the same question. Decide it in advance rather than discover it later, which is the approach the National Archives sets out in its notes on records management policy. Ask two further things. Does a completed record survive the list being edited afterwards?
In the US, OSHA 29 CFR 1904 requires keeping OSHA 300 logs for 5 years.
And can you retrieve the version of the list that was in force on a past date? The second question is the one vendors are least ready for, and it is the same question that governs choosing procedure software.
The response loop
A completed checklist that produces no response teaches everyone that the exercise is theater, and no feature fixes that.
What to look for:
A route for "not right". Every list needs somewhere to record a problem, and the tool has to make that route obvious rather than buried behind the completion button.
Notification to a role, not a person. People leave, and an alert routed to a departed employee is worse than no alert.
Evidence that something happened. Whether the tool closes the loop, or at least shows the item as open until someone acts.
Where an item has a safety consequence, the expectations are set outside your organization, and published material such as the UK regulator's risk assessment templates is a better guide to what a record should show than any vendor's compliance page.
What to ignore
- Template libraries. The items have to match your equipment and your own failures, and a supplied list contains neither. The shapes worth copying are in operational checklists template.
- Completion-rate dashboards presented as safety or quality. They measure ticking.
- Photo requirements on every item, which turn a thirty-second list into a five-minute one.
- Scores, badges, and anything that makes ticking feel like an achievement. It already is being ticked; that was never the problem.
Print and paper, still
Whatever you choose, ask how it produces a paper version. There will be a place with no signal, a device that is flat, and a day when it matters. A tool that cannot produce a clean printed list with a visible version number has not thought about the work.
The layout of that printed version is not a small matter, and the same constraints that shape a wall-mounted procedure apply, as set out in SOP format.
A trial worth an afternoon
- Build one list from your own written items.
- Run it in the real place, on the real device, timed against paper.
- Complete it with no connection, then reconnect.
- Record a problem and see where it goes.
- Publish a new version and check what happens to a run in progress.
- Retrieve last week's completed record and confirm it names the version used.
- Export everything and open it elsewhere.
Steps two, three, and six decide it.
When paper wins
One site, one shift, a handful of lists, and a manager who reads them. Paper is faster, cheaper, and more reliable, and completed sheets in a folder are a perfectly good record.
The case for a tool begins with several sites, an outside party asking for evidence, or a real suspicion that lists are signed rather than run.
