“Every demo looks good. They all have checklists, incidents and a dashboard.”
That is the problem with comparing health and safety management software from a feature list. Almost every platform ticks the same boxes, so the list cannot tell you which one will work in your business. What separates them is what happens when your real work hits the system: a worker in a yard, a new starter on day one, a job that has to be found again in a year, a licence about to lapse. The most useful thing a buyer can do is stop asking “does it have X” and start asking the vendor to show it, using your own scenarios.
Here are five tests, drawn from what the AREESA team sees go right and wrong across implementations.
A quick distinction first
Software does not make a business safe, and it does not make it compliant. What good software does is give you a reliable, verified record of what your people did and when, and make the right thing the easy thing for the people doing the work. Be wary of any pitch that promises more.
The five tests
Test 1: can someone with no login report a problem?
Most platforms assume everyone who touches the system has an account. In practice some of the most useful reports come from people who do not: a customer who notices a fault on a hire vehicle, a visitor who spots a hazard, a member of the public reporting a damaged asset.
Ask the vendor to show: a person without an account reporting a problem against a specific asset, without being able to see anything else, and that report landing in the same place as staff checks. In AREESA that is a public asset; the hire fleet article walks through it.
Test 2: what happens to your existing records?
If you are moving from paper, spreadsheets or another platform, your history is evidence and you will want it.
Ask the vendor to show: which records come across, who does the work, and what they do with the data that is messy. In AREESA, projects, assets and sites come in through CSV import, and for businesses leaving Verizon Connect Work the AREESA team runs its own migration tool; the Verizon Connect Work article covers it. A login and an import template is not a migration.
Test 3: does a whole job live in one place?
Pre-start, risk assessment, SWMS, photos, completion sign-off. On most platforms each is a separate form, and someone reassembles the job at the end.
Ask the vendor to show: one of your typical jobs, from the pre-start to the completion sign-off, as a single record you can open a year later. In AREESA that record is the project, and the JSA and SWMS article shows what sits against it.
Test 4: how long does it take the person in the field?
Safety managers choose software. Workers on site decide whether it gets used. If a JSA takes twenty minutes on a phone, it will be copied from yesterday. If a SWMS is signed by one person for the crew, the record is weak.
Ask the vendor to show: a worker opening a JSA with the job details already filled in, signing a SWMS on their own phone, and the supervisor seeing both against the project. Time it.
Test 5: can you prove a licence, today, in seconds?
Many platforms offer expiry alerts. Fewer make the evidence easy to collect and easy to produce when a client or a site asks for it.
Ask the vendor to show: a worker uploading their own licence, the reminder before expiry reaching both the worker and the admin, and the licence visible on the worker’s profile beside their inductions. The licence register article covers how AREESA does it.
What to look for in the answers
| Signal | Good sign | Warning sign |
|---|---|---|
| Configuration | Built around how you work | “Everyone uses the standard template” |
| Implementation | A defined run of sessions: requirements, configuration, migration, training | A login and a help centre |
| Verification | Who, when, which asset or job, on every record | A form exists, with no clear attribution |
| Field use | Fast on a phone, prefilled where it can be | Long forms, desktop first |
| Hosting | Clear about where data is stored | Vague answers |
| Scale | Works across sites and crews | Designed for one office |
Documented versus verified
Every test above comes back to the same line. Documented means a form exists somewhere that says something happened. Verified means you can show, on demand, who did it, when, against which asset or job, and that it is the current version. Ask every vendor which one they deliver.
Why AREESA
AREESA is built around that line. It is configured to how your business operates, implemented by the AREESA team through a run of working sessions, hosted in AWS Sydney and built for businesses with more than one site. We would rather you ran these five tests on us than took a feature list on trust.
