Risk Management Platform Ideas

When generating an OSHA 300A by selecting the child site from the main platform site selection and then going to Incident Track>Reports>OSHA Reports>OSHA300A and completing the inforamtiona and then downloading the OSHA300A the report doe...

The Severity dropdown on the Additional Information tab of WR incidents has no function other than to hide or expose the Timeline control depending on the value selected. This behavior is confusing and makes the timeline more difficult to find. Su...

NV requires a signature on the C3

The mandatory fields by location each change with the exception of the NAICS. The industry description can change from location to location and all other data except the NAICS. Please correct so the NAICS changes by location as well.

Client would like to be able to differentiate between a quick report and regular incident email in the email log. Suggested to have a different subject line

Identifying shift allows us to better trend incidents

I have two clients that are merging. Both have used the RMC but they want a fresh start with it. Each have 40 sites that we are going forward with as locations instead. Doing the exports for all the incidents for each site is very labor intensive.

So our clients can put multiple NAICS codes in Succeed for the OSHA logs.

When an Inicident history is imported, there are times when the employee supervisor was different then it is today, and this will create a duplicate record. The incident import should not create employees, only use existing.

A client of mine said that the graphs look like they are from the 90s and would like them to be updated