Can you please help me create a form template that can be uploaded into Salus from a form that is attached

To create a safety form template in Salus from an attached form, structure the template so it captures document control, required data fields, workflow approvals, and retention requirements while preserving all information needed for incident, hazard, inspection, and PPE/risk-assessment processes. If you are using an existing paper/PDF form as the source, convert each prompt, checkbox, signature, and date field into a discrete Salus field, and make mandatory any field needed for legal recordkeeping, corrective action tracking, or internal accountability. For recordable injury/illness forms, an equivalent electronic form must contain all instructions and information requested on the source form. [8] [14]

Recommended template sections and field requirements:

• Document control: form title, unique form ID/number, revision number, effective date, review date, owner/department, approval status, and superseded-version control.
• Compliance metadata: project/site/location, employer/company name, department, job title, supervisor, assessor/investigator/completed-by name, and dates/times of submission and event.
• Incident reporting fields: employee name, incident date, time of incident, normal schedule/overtime status, day of week, exact location, whether it occurred on employer premises, action taken by company, detailed incident description, body part affected, type of incident, PPE in use, witnesses, medical treatment, workers' compensation status, whether employee left work, and supervisor comments.
• Hazard reporting and risk assessment fields: task/step, identified hazard, who may be affected, consequences/harm, risk level, priority, hazard controls, additional notes, assessor signature, committee/representative signature, and completion date.
• Inspection/PPE assessment fields: work area, job/task/equipment, exposure categories, whether hazards can be eliminated without PPE, selected PPE by body area, and verification that controls are implemented and understood by workers.
• Corrective action and closure fields: unsafe condition identified, corrective action required, responsible person, target date, completion date, verification of effectiveness, and closeout approval.
• Approval workflow: employee/worker signature where applicable, supervisor signature, completed-by/investigator signature, title, date, and management or safety approval for final closure.
• Recordkeeping and confidentiality: confidentiality flag for employee health information, retention period, case/log number linkage, and restricted access permissions for medical or injury data.

[2] [3] [6] For document control in Salus, build the form so every uploaded template has a controlled lifecycle. At minimum, include the form name, revision number, effective date, review date, and approver. Lock obsolete versions from use, and require users to complete only the current approved version. This is especially important where the form supports regulatory reporting, because the electronic version must remain equivalent to the required source form and preserve all required prompts and instructions. [8] [16]

For incident reporting templates, include enough detail to support internal investigation and OSHA/MIOSHA/Cal/OSHA-style recordkeeping. Required fields should capture what the employee was doing before the event, what happened, the injury or illness, and the object or substance that directly harmed the employee. Also include case number linkage, treatment details, hospitalization/emergency room questions, and death information if applicable. Configure date/time fields and narrative fields separately so reports can be searched and trended in Salus. [8] [8] [8] [8]

Your incident template should also preserve the practical investigation elements shown in standard accident forms: witnesses, supervisor comments, prevention measures, whether unsafe conditions were corrected, and what still needs to be done if they were not corrected. These fields are critical for corrective action tracking and closure in Salus. [3] [3] [3]

For hazard reporting and risk assessment templates, use a structured table format in Salus that lets users document the step or task, hazard, consequences or harm, risk level, priority, and hazard controls. Include a risk-ranking method such as a matrix and require documentation of how decisions were reached. The form should support the hierarchy of controls and allow reassessment after controls are implemented. [5] [6] [13]

A strong Salus hazard form should mirror the risk assessment process: identify hazards, assess and rank risk, determine controls, implement controls, measure effectiveness, and improve continuously. Add fields for responsible person, due date, verification date, and effectiveness review so the form functions as both an assessment and a corrective-action tracker. [13] [13] [13]

For PPE hazard assessment or inspection templates, organize fields by body area and exposure type. Include work area/location, assessor, date, job/task, exposure sources, whether the hazard can be eliminated without PPE, and the selected PPE. This supports defensible PPE selection and makes the form easier to configure in Salus using conditional logic: if the user selects "No" for hazard elimination, then the PPE selection fields become required. [7] [7] [15]

Include detailed PPE options only where they support the work being assessed. Typical selectable fields include eye/face protection, hand protection, foot protection, respiratory protection, hearing protection, and body protection, with exposure prompts tied to the task. This makes the template usable for inspections and hazard assessments without forcing irrelevant fields on every user. [7] [11] [10] [12]

For approvals and signatures, configure Salus to capture electronic signatures, printed name, title/role, and date for each required approver. At minimum, include the person completing the form and the supervisor or employer representative; for investigations or assessments, also include assessor/investigator and committee or safety representative signoff where required by your process. [1] [3] [4]

For training/compliance acknowledgment fields, if the form is used to document worker understanding of hazards or controls, include employee acknowledgment, trainer name, training date, and topics covered. This is useful when the uploaded form is intended to support hazard communication, orientation, or control verification in Salus. [9] [9] [16]

For regulatory and recordkeeping requirements, configure the template and workflow so recordable injury/illness reports can be completed within 7 calendar days of learning of the case, retained for 5 years following the year to which they pertain, and protected for confidentiality because they contain employee health information. Add restricted permissions in Salus for medical details and case records, and include a field for the log case number so the form can be tied to the injury/illness log. [8] [8] [8]

Practical Salus build guidance:

1. Map every field from the attached form into a Salus field type: text, date, time, dropdown, checkbox, signature, photo/sketch upload, or long narrative.
2. Use conditional logic so follow-up questions appear only when triggered, such as medical treatment, workers' compensation filing, hazard not eliminated, corrective action incomplete, or hospitalization.
3. Make legally significant fields mandatory: event date/time, employee/worker identity where applicable, location, description, injury/illness details, corrective actions, signatures, and dates.
4. Use standardized dropdowns for incident type, body part, injury type, risk rating, and status to improve reporting and analytics.
5. Add attachment capability for sketches, photos, witness statements, and supporting documents; this is especially useful where the source form includes an illustration area.
6. Include workflow statuses such as Draft, Submitted, Under Review, Corrective Action Open, Closed, and Archived.
7. Assign permissions by role so supervisors can review, safety can investigate and close, and sensitive medical details are restricted.
8. Set retention and archive rules consistent with applicable injury/illness recordkeeping requirements and your internal document control procedure.

[1] [3] [2]