can you draft me an overview of what salus does so that I can share it with my field staff?

Salus, as a field-focused safety management platform, can be understood as a digital system for organizing and executing core safety management activities in one place for supervisors, workers, and administrators. For field staff, its practical value is in turning safety programs, onboarding, inspections, hazard assessments, incident reporting, and compliance records into accessible, trackable workflows that support day-to-day worksite control. This aligns with recognized safety management practices that emphasize program development, hazard prevention and control, worksite inspections, and employee training, as well as a systematic approach that considers procedures, training, emergency preparedness, and other elements affecting safety performance. [8] [16]

• Health and safety program management: centralize company policies, site-specific plans, safe work procedures, toolbox talk records, corrective actions, and assigned responsibilities so field teams can work from current requirements.
• Worker onboarding and training: deliver new-hire orientation, site-specific orientation, job-specific training, refresher training, and documented safety meetings; track completion and maintain records at the project level.
• Digital forms and inspections: replace paper forms with mobile checklists for daily inspections, equipment checks, audits, permits, and pre-task reviews; capture findings, assign actions, and document closure.
• Hazard assessments: support pre-job and ongoing hazard identification, including task-based assessments and changing-site-condition reviews, so crews can identify hazards and controls before work starts and as conditions change.
• Incident and near-miss reporting: allow workers and supervisors to report incidents quickly from the field, gather facts, document witnesses, investigate causes, and track preventive actions to closure.
• Compliance documentation: maintain accessible records for training, inspections, audits, incident investigations, corrective actions, permits, SDS access, and other documents needed to demonstrate implementation of the safety program.
• Field safety communication: distribute alerts, procedure updates, emergency information, and toolbox talk content to workers in real time, while documenting who received and acknowledged critical information.

[1] [4] [2] For field staff, health and safety program management should be operational rather than administrative. A platform like Salus is most useful when it gives crews access to the current safety program, site rules, emergency procedures, and task controls at the point of work. It should also help supervisors demonstrate active oversight through frequent inspections, documented meetings, and corrective-action follow-up. This is especially important in construction and other dynamic environments where hazards and crews change frequently and continuous management involvement is necessary. [9] [7] [14]

Worker onboarding and training functionality should cover the full worker lifecycle: new-hire orientation, site-specific orientation, task-specific instruction, emergency procedures, hazard communication, and periodic toolbox talks. The platform should make training assignments role-based, record attendance and competency, and preserve records for verification. For field use, the strongest systems also support multilingual communication and rapid retraining when site conditions, procedures, or hazards change. [1] [6] [13]

Digital forms and inspections are a major field function because they standardize how safety checks are performed and documented. Effective functionality includes configurable checklists, photo capture, timestamps, signatures, offline capability, and automatic routing of deficiencies to responsible persons. From a compliance perspective, digital forms are valuable when they do more than collect data: they should verify requirements, trigger corrective actions, and preserve documentation showing that inspections, audits, and reviews actually occurred. [5] [5] [18]

Hazard assessment functionality should support both planned and ongoing risk review. In practice, that means pre-task hazard assessments, job hazard analyses, phase-based assessments, and updates when conditions change. The platform should help crews identify hazards, assign controls, communicate them before work begins, and retain the assessment as part of the project record. Strong hazard assessment workflows also support design and planning decisions by identifying hazards early and reducing reliance on reactive controls. [10] [4] [4]

Incident reporting functionality should cover injuries, illnesses, property damage, environmental events, and near misses. For field staff, the key benefit is immediate reporting from the jobsite, followed by structured investigation, root-cause review, witness documentation, and corrective-action tracking. A mature system should also support learning from events by sharing findings with affected employees and using trends to prevent recurrence. [2] [2] [3]

Compliance documentation in a platform like Salus should function as a controlled record system. Field staff need quick access to current procedures, permits, SDS-related information, emergency contacts, inspection histories, training records, and proof of completed corrective actions. Administratively, the platform should preserve revision history, approvals, and accessibility of records so that supervisors, auditors, and workers can verify what requirements applied, what actions were taken, and whether deficiencies were closed. [2] [12] [14]

On regulatory requirements, a platform does not replace legal compliance expertise, but it can help employers operationalize requirements from OSHA and related standards by assigning responsibilities, documenting training, maintaining inspection and audit records, supporting hazard communication, and preserving evidence of employee involvement. The source documents consistently show that compliance depends on documented implementation, competent personnel, and ongoing verification rather than simply having written policies. [16] [5] [19]

Field safety communication is one of the most important practical functions. A strong platform should support toolbox talks, safety alerts, emergency notifications, procedure changes, and two-way communication between workers, supervisors, and managers. Communication should be timely, site-specific, understandable to the workforce, and documented. This is particularly important when workers move between tasks or locations, when conditions change, or when incidents and audit findings need to be shared quickly with affected personnel. [11] [17] [6]

• For workers: complete onboarding, review site hazards, submit forms, report hazards and incidents, receive alerts, and participate in toolbox talks from a phone or tablet.
• For supervisors: assign training, conduct inspections, approve forms, review hazard assessments, investigate incidents, and track corrective actions.
• For safety managers: maintain programs, monitor compliance status, analyze trends, prepare for audits, and verify documentation across projects.
• For contractors and subcontractors: submit required documents, verify qualifications, receive site rules, and coordinate work authorization and communication.

[15] [15] [6] In summary, the core functionality expected from a platform like Salus for field staff is to make safety management visible, usable, and documented in real time: manage programs, onboard workers, deliver and record training, complete inspections and forms, assess hazards, report incidents, maintain compliance records, and communicate safety information across the field organization. The strongest value is not digitization alone, but better consistency, accountability, and faster corrective action in environments where hazards change quickly and documentation matters. [8] [9] [4]