Questions we hear before a rollout.

Most teams have a working template within one to two weeks. We start from your existing hazard categories and scoring matrix if you have one, or build one with you if you don’t. Either way, it’s configured to your standard before anyone runs a live assessment.

A short session, usually under an hour, covers the app and your specific template. Because the layout follows the same logic as a paper walk-through, most assessors are comfortable within their first live inspection.

Yes. We typically import from spreadsheets or exports from your previous system as part of rollout, so your risk history stays visible alongside new assessments rather than starting from zero.

Nothing changes for the assessor. The assessment, photos and notes are all stored on the device as they go, and the app queues the sync automatically. It uploads on its own the next time the device has a connection, with no manual export step.

Each assessment is tied to the assessor who opened it, so two people don’t overwrite the same record. If a conflict does arise on sync, for example an asset edited from two devices, SAS flags it for a site lead to resolve rather than silently picking one version.

Yes. 5-Why and fishbone are built in, but the RCA step can be configured to follow your organisation’s own methodology if you use something different.

That’s configurable per action type. Typically the action owner marks work complete, and a site lead or EHS manager verifies before the CAPA record closes, so nothing self-closes without a second set of eyes.

Access can be scoped down to individual sites, buildings or business units, and layered with role. A regional manager sees every site in their region, while an assessor only sees the assessments assigned to them, all within the same permission model.

Risk scores on the dashboard update as assessors submit hazard entries during the walk-through, not after the full report is finalised. In practice that means a site lead can see a hazard appear within moments of it being logged, connection permitting.

Both. The dashboard rolls up from an individual building, to a site, to a region, to the full portfolio. Access permissions determine which level a given user lands on by default.