IncidentLog vs. SALUS Safety: A Field-Tested Comparison
SALUS users report that field-filled incident forms don't automatically populate the incident tab, forcing supervisors to retype summaries back at the office, and that admin functions are limited on mobile, requiring a return to a desktop. IncidentLog's QR-based intake writes directly into the same record a supervisor reviews — no retyping — and the admin dashboard is fully usable from a phone.
Where the two approaches actually differ
This is drawn from verified G2 and Capterra reviews and field reports about SALUS Safety, compared against how IncidentLog actually behaves — not a feature checklist written by a marketing team.
| Feature | IncidentLog | SALUS Safety (per field reports) |
|---|---|---|
| Worker signup required | No — scan the QR code, fill it out, done | Field reports describe an app download and account setup for workers |
| Field-to-office re-entry | None — the field submission is the record; it auto-compiles into OSHA 300/300A/301 | Field forms reportedly don't populate the incident tab — supervisors retype summaries at the office |
| Mobile admin functions | Full dashboard — add sites, manage team, review reports, all from a phone | Admin functions reported limited on mobile; a desktop is needed for full functionality |
| Bilingual field intake | English/Spanish, switchable in one tap | Not documented in the reports reviewed |
The duplicate-entry problem, specifically
The most consistent complaint in field reports about SALUS is that a form filled out on-site doesn't automatically become the record a supervisor works from — it has to be reviewed and manually retyped into the incident tab back at the office. For an OSHA 300 log, that's a second point of failure: the retyped summary has to match the original, on top of everything else that has to happen within the 7-calendar-day recordkeeping window. IncidentLog skips that step entirely — the field submission a worker files is already the locked, hashed record; nothing downstream re-creates it.
Why field workers resist adopting safety apps
An app download and a new account are real friction for a subcontractor crew that moves between job sites and employers — it's one more login to remember for a tool they didn't choose. That friction is exactly why near misses and minor incidents go unreported in practice: the easier path is saying nothing. IncidentLog's job-site QR poster removes the step entirely — scanning it opens a mobile web form directly in the browser, in English or Spanish, with nothing to install and no account to create.
Frequently asked questions
Do subcontractors need an account to file an OSHA incident report?
Not with IncidentLog — a subcontractor or field worker scans the job-site QR code and files the report directly in their phone's browser, no account or app install. Some competing platforms, including SALUS per field reports, require workers to install an app and create a login before they can file anything, which is exactly the adoption friction that causes reports to not get filed in the moment.
How do you avoid duplicate incident data entry for OSHA logs?
The field submission is the record — nothing gets retyped. Once a worker files a report, it's locked, hashed, and rolls up automatically into the OSHA 300 log and 300A summary. This directly addresses the duplicate-entry problem reported by SALUS users, where a field-filled form doesn't automatically appear in the incident tab and has to be manually re-entered back at the office.
Can I manage sites and review incidents from my phone, or do I need a computer?
The full admin dashboard — adding job sites, managing your team, reviewing and classifying incidents — works from a phone. This is a specific area where SALUS users report a gap: admin functions are described as limited on mobile, forcing a return to a desktop for tasks a site supervisor would otherwise handle on-site.
Is IncidentLog a good SALUS Safety alternative for a small construction company?
It's built specifically for that profile — a construction or trade business filing incident reports across one or more job sites, with a bilingual, often part-subcontractor crew. The core difference from SALUS, per the field friction described above, is that nothing requires a worker-side app or account, and nothing needs re-entry once it's filed.
Keep reading
Try the exact worker-facing form yourself
No signup, no install — see what your crew sees when they scan the job-site QR code. Plans start at $49/mo per site, unlimited workers and subcontractors.