SALUS

SALUS is built on the view that a safety program is only as good as the records crews actually create. A written hot work procedure means little if the permit is signed in the trailer and the fire watch is logged after the fact. So SALUS puts the effort into capture at the point of work: QR codes at a panel or space entrance, voice and photo input, offline forms, and multiple languages. Every record ties back to the worker, their certificates and training, the equipment, and the location, which is what makes it useful later.

The main users are trade contractors: safety managers who own the program, foremen who complete JHAs and pre-task plans every morning, and project managers who need proof when an owner or insurer asks. The permit-to-work module shows how the pieces connect. A hot work request checks that the worker's fire watch training is current and flags another open permit in the same zone, such as a confined space entry, before anyone approves it. Rosie, the embedded AI assistant, drafts JHAs and toolbox talks from the company's own programs, fills forms from a voice note, and answers questions like which crews had the most near misses last quarter.

When evaluating SALUS, test the field experience with a real crew, since adoption is the whole point, and check how your existing forms map into the builder. Confirm how the Procore integration handles your observations and daily logs, and review how Rosie's drafts are approved, because the contractor remains responsible for the final safety record.