Before You Launch EHS Software: Prepare the Data and People

Choose a first workflow with a clear beginning and end

Start with a recurring process that matters to your operation and has an identifiable owner. An action register can be a useful example: a concern is recorded, reviewed, assigned, acted on and checked. Write down the stages your team actually needs before configuring a tool or importing data.

Explain who can create an item, who determines the next step and who confirms completion. Identify exceptions, such as a concern requiring urgent attention or specialist input. The software should support an agreed process; it should not become the place where people first discover that the process has no owner.

• Define the corrective-action process before configuring it →

Prepare five things before the pilot

Use this checklist as an implementation discussion, not as evidence that a particular product provides every capability. Confirm the selected platform's actual functions and the agreed service scope separately. Some requirements may need a different configuration, integration, supporting process or product.

Scroll sideways to see every column →

Translate the meaning of the spreadsheet, not just its columns

Review the records with the people who maintain them. Short labels often conceal different interpretations. An owner column might identify the person coordinating updates rather than the person implementing the action. A completed date might mean a document was uploaded, even though a field check remains open.

The mapping below is illustrative. The destination fields are proposed meanings to evaluate, not a list of confirmed PreventX product features. Keep a record of mapping decisions so later users understand how historical entries were interpreted.

Scroll sideways to see every column →

Clean the data without losing its history

Identify duplicate records, missing owners, inconsistent dates and broken evidence links before importing them into a live workflow. Decide which records are active, which belong in a retained archive and which need review. Keep uncertain items visible rather than making assumptions to complete the import.

An old action marked closed should not automatically gain evidence it never had. A missing target date should not silently become today's date. Record those exceptions and decide how they will be handled. The aim is to give the receiving team information it can interpret, not simply produce a spreadsheet with no blank cells.

Involve the people who will report and act

Invite a small mix of actual users to review the proposed workflow: someone who raises a concern, someone who receives an action and someone who reviews progress. Ask them to explain the stages in their own words and show where an instruction or label is unclear.

OSHA's worker participation guidance supports involving workers in the safety and health program. For a software rollout, that is a useful reason to test the process with its intended users. Agree appropriate access for different information and roles, especially where records could contain personal or sensitive details.

Sources: OSHA worker participation guidance

Test the whole workflow with representative cases

Use fictional or appropriately sanitized records when evaluating a product. Ask the supplier to demonstrate how the proposed workflow handles the cases below, and have intended users try the relevant steps. Record what works, what needs explanation and what is outside the product or agreed scope.

These are evaluation criteria, not claims that PreventX currently offers every function described. The public PreventX demonstration is an illustrative workflow; it should not be used to store real customer records or personal injury information.

• An imported action retains the correct concern, site and responsible person.
• Supporting evidence remains connected and accessible to an authorized user.
• An overdue item is identifiable and has a clear follow-up process.
• An incorrect entry can be corrected through an agreed method while preserving needed context.
• An authorized person can retrieve or export the records required for ongoing work and an eventual handover.

• Explore the illustrative PreventX workflow →

Check regulated record requirements separately

If a system will hold OSHA injury and illness records, assess those requirements specifically. OSHA 1904.29 permits computer recordkeeping when the required equivalent forms can be produced. Its equivalent-form criteria concern the information, readability and instructions used; a generic incident dashboard does not establish that a system satisfies them.

OSHA's April 29, 2025 interpretation discusses software-generated equivalent forms and access to copies. Use the applicable requirements to evaluate that intended use, separately from ordinary action tracking. Do not assume a platform handles official recordkeeping forms simply because it has an incident or document feature.

Sources: OSHA 1904.29: Forms · OSHA interpretation on software-generated equivalent forms

Use the pilot to decide what happens next

Review whether users can perform the agreed steps, whether records retain their meaning and whether the responsible people can obtain the information they need. Resolve important problems before expanding to another site or workflow. Keep a clear decision about which system is authoritative during the transition so users do not update conflicting lists indefinitely.

OSHA's program evaluation guidance encourages assessing implementation and using findings to improve the program. Apply that idea to the rollout: use the pilot's observations to change instructions, responsibilities or configuration, then repeat the relevant check. A launch date alone does not demonstrate that the process is ready.

Sources: OSHA program evaluation and improvement

Bring one real workflow to the platform discussion

Describe the workflow, people, records and decisions you need to connect. Bring a sanitized example of your current register and the parts that cause confusion. A platform discussion can then focus on how the proposed setup would support your operation and what must be confirmed.

If the larger gap is deciding priorities, coordinating follow-up or supplying professional support, consider Managed EHS or the hybrid option alongside software. Define the service and product responsibilities explicitly so your team knows who will do the work after implementation.

• Review the EHS Management Platform →
• Explore the platform with professional support →
• Review Managed EHS when the process needs ongoing support →

Questions employers ask