SpheraCloud HSE Incident Management Configuration Training Course

Course overview

HSE teams depend on incident data to identify recurring hazards, meet reporting obligations, and prevent serious events. Yet many organisations operate SpheraCloud Incident Management with inconsistent classifications, poorly routed workflows, incomplete investigation records, and action registers that do not provide reliable assurance of closure. This course addresses the practical configuration decisions behind a usable incident-management process: what users see, what data they must provide, who reviews each case, and how information becomes dependable management reporting.

Participants configure the SpheraCloud Incident Management environment around a defined HSE process. They work with incident types, taxonomies, forms, conditional fields, severity and risk classifications, workflow stages, notifications, security roles, investigation methods, corrective and preventive actions, dashboards, and reports. The course also examines how configuration choices support ISO 45001 incident investigation requirements and OSHA recordkeeping needs, while preserving clear ownership, audit trails, and data quality.

Delivery combines instructor-led demonstrations with guided configuration in a training environment and case-based workshops. Participants progressively configure an incident process for a realistic operational scenario, from initial notification through investigation, action assignment, verification, and trend reporting. They leave with a documented SpheraCloud configuration workbook containing field definitions, workflow rules, role permissions, notification logic, taxonomy decisions, test cases, and a deployment-readiness checklist that can be adapted for their organisation.

The course is designed for HSE systems administrators, process owners, business analysts, and HSE professionals responsible for improving or governing incident reporting. It is equally valuable for project teams preparing an implementation, redesign, migration, or controlled expansion of an existing SpheraCloud Incident Management deployment.

Course objectives

By the end of this course, participants will be able to:

• Configure incident types, classifications, severity scales, and location taxonomies in SpheraCloud Incident Management
• Build incident forms with mandatory fields, conditional logic, validation rules, and role-relevant data capture
• Design workflow stages, approval routes, escalation paths, and automated notifications for incident processing
• Set up security roles and permissions that control access to cases, investigations, actions, and reports
• Configure investigation records using root-cause methods, evidence capture, and corrective-action linkage
• Create corrective and preventive action workflows with owners, due dates, verification steps, and overdue escalation
• Produce dashboards and reports for incident trends, action status, severity patterns, and management review
• Develop a configuration workbook and test script for controlled deployment of an incident-management process

Benefits of attending

Target competencies

Who should attend

• HSE Systems Administrators — who configure and maintain SpheraCloud Incident Management for business users
• HSE Managers — who need reliable incident workflows, investigation evidence, and performance reporting
• EHS Business Analysts — who translate operational reporting requirements into fields, rules, and workflows
• Incident Management Process Owners — who define governance for notification, investigation, action closure, and assurance
• HSE Data and Reporting Analysts — who need consistent classifications and reportable incident data
• Implementation Project Team Members — who support SpheraCloud rollout, redesign, testing, or migration activities

Requirements and prerequisites

Participants should understand their organisation’s current incident-reporting and investigation process, including basic concepts such as near misses, recordable events, corrective actions, root-cause analysis, escalation, and action closure. Familiarity with HSE terminology and experience using web-based business systems are expected. Access to a SpheraCloud training tenant or sandbox is useful for practice; where this is provided, no prior SpheraCloud configuration experience is required. Programming, database administration, API development, and advanced system-integration knowledge are not required. Complete beginners should expect to spend time learning both the incident-management process model and the SpheraCloud configuration interface.

Training methodology

The instructor uses a SpheraCloud training scenario based on a multi-site operational incident process. Short demonstrations introduce each configuration area, followed by guided hands-on work in the training environment. Participants analyse incomplete incident records, configure fields and workflow logic, test user roles, and review report outputs against HSE management requirements. Small-group workshops compare design choices for escalation, investigation, and action verification. On the final day, each participant refines a configuration workbook and deployment plan using peer review and instructor feedback.

Course outline

Day 1: Incident process design and SpheraCloud foundations

• SpheraCloud Incident Management navigation and configuration architecture
• Incident lifecycle mapping from notification to closure
• Incident types, event categories, and reporting boundaries
• HSE taxonomies for locations, activities, hazards, and consequences
• Severity classification and risk-rating design principles
• ISO 45001 incident and nonconformity process considerations
• Configuration governance, change control, and design documentation

Workshop: Participants map a target incident lifecycle and produce a configuration decision log covering types, statuses, classifications, and owners.

Day 2: Forms, data quality, and security configuration

• Incident form layout and section design
• Mandatory fields, default values, and validation rules
• Conditional fields and context-sensitive data capture
• People, asset, contractor, and location reference data
• Recordable-event data requirements and OSHA 29 CFR 1904 considerations
• Security roles, access scopes, and segregation of duties
• User acceptance criteria for incident data capture

Workshop: Participants configure an initial incident-report form with conditional fields, validation rules, and role-based visibility, then run a data-quality test.

Day 3: Workflow, investigation, and notification design

• Workflow states, transitions, and ownership rules
• Triage, review, approval, and closure-stage configuration
• Automated notifications, reminders, and escalation triggers
• Investigation record design and evidence capture
• Root-cause analysis methods including 5 Whys and causal-factor analysis
• Linking incidents to corrective and preventive actions
• Workflow testing with exception and reassignment scenarios

Workshop: Participants configure and test a workflow for a high-potential incident, including escalation, investigation assignment, and management approval.

Day 4: Actions, assurance, reporting, and analytics

• Corrective action fields, ownership, due dates, and priority rules
• Action verification, effectiveness review, and closure evidence
• Overdue action monitoring and escalation design
• Incident trend measures for frequency, severity, and recurrence
• Dashboard design for operational leaders and HSE managers
• Report filters, groupings, drill-downs, and scheduled distribution
• Data-quality checks for duplicate, incomplete, and misclassified records

Workshop: Participants build an action-assurance view and a management incident-trend dashboard using the configured scenario data.

Day 5: Deployment readiness and configuration governance

• Configuration workbook structure and traceability
• Unit testing, workflow testing, and user acceptance testing
• Test cases for permissions, notifications, forms, and reports
• Migration and data-cleansing considerations for legacy incident records
• Training and adoption planning for reporters, investigators, and approvers
• Release management, configuration change control, and audit evidence
• Post-deployment measures for adoption, timeliness, and data quality

Workshop: Participants complete a deployment-ready configuration workbook, test script, and 90-day improvement plan for their incident-management process.

Tools & standards covered

SpheraCloud Incident Management, SpheraCloud Platform, ISO 45001:2018, OSHA 29 CFR 1904

A typical training day

Live online deliveries follow the same structure in the East Africa Time zone, with shorter screen blocks and longer breaks.

What the fee includes

How you can take this course

Certification

Participants who complete the full five days receive the Skillset Development Certificate of Completion, stating the course title, course code, dates and delivery format — suitable for professional-development records and employer reimbursement.

Frequently asked questions