Multi-site operations

How Safety / Incident Reporting is set up for you

Organizations with several operating units need a consistent way to place an incident in its local context. Business Units carry a name, code, contact and address. An assessment names the organization and operating unit for a defined period, while the investigation records the site where the event occurred. That distinction helps a central Safety Manager compare work without losing the local account.

A central team may work across sites, but it still needs to know which operating unit owns a risk. For example, a vehicle movement near miss at one site can be recorded beside that unit's control test and finding. A similar hazard elsewhere can use a separate assessment and control owner. Compare the accounts through their dates, status and severity rather than assuming every site has the same exposure.

Start with one organization and one active operating unit. Set its contact, address and team members, then define a period assessment. Add a risk and active control that the local team understands. Rehearse an incident account, a test with an exception, an action and an independent retest. Once the handoff is clear, add the next unit using the same naming and evidence conventions.

Keep the evidence visibility choice deliberate when sharing material across teams. A Shared attachment should be chosen by the responsible uploader; an Internal attachment stays within its intended review context. Review how the central manager sees unresolved findings in Operations Overview and whether each one has a named owner.