We're excited to introduce Incident Management V3! This release features a new customisable Incident Management master form and a permission-driven framework for creating and managing incidents. Here's a quick look at the exciting highlights and improvements in this release:

Default Incident v3 Template: A master Incident v3 template is provided as a starting point. Users with proper permissions can clone and customise it.
Configurable Templates: Organisations can customise v3 forms with the new drag-and-drop editor.
New Incident Dashboard: New dashboard sorts incidents by status (like In Progress or Pending Review) and works for both personal and location-based tasks.
Improved Workflow & Statuses: Incidents follow a clear progression (e.g., In Progress → Pending Review → Incident Review → Outcomes), ensuring teams can collaborate efficiently.
Role-Based Permissions: Granular permissions determine user actions—view, create, edit, archive, publish—across incidents and templates.

New features

Incident form management

Activation and access

Toggle in Application Settings: A new Incident Form Management toggle is available under the Admin → Application Settings page. Once switched on, authorised users can activate or deactivate the feature in the Features Dashboard.
Permissions:
- IncidentFormManagement permissions let administrators fine-tune who can view, create, edit, archive, and publish templates.
- Permissions are inclusive; for example, granting ViewCreateEditArchivePublishIncidentTemplate includes all lower-level actions (view, create, edit, archive).

Manage templates

Template List: Access the Incident Form Management subsection within Admin → Incidents→ Incident Form Management to see all form templates—default and custom—sorted by last update date.
Template Actions: Depending on a user’s permission level and the template’s status (Draft, Published, Archived, Read Only), actions such as View, Edit, Create New From This, Archive, Unarchive, and Publish become available.
Archive/Unarchive: Users with the relevant permission can archive templates (rendering them unavailable to new incident forms) and restore them from an archived state.
Publish: Publishing a template makes it live for associated locations. At least one location must be linked before you can publish.

Create and edit templates

Drag-and-Drop Builder: Quickly add new fields or entire panels using an intuitive editor. Fields inherited from the master template can be duplicated—but not edited—ensuring critical data remains intact.

Draft and Publish: Work on changes in a Draft state, then publish once everything is ready. Published templates increment their version automatically when further edits occur.
Versioning: Each time a published template is edited, a new version is created, allowing administrators to track changes over time.

Incident Management V3

Enhanced permissions

Admin Control: A separate IncidentReportV3 permission set (under End User roles) enables or restricts key actions (creating, viewing, or editing incidents at various statuses).
Location-Based Permissions: Users can be granted rights specifically for incidents in the locations they oversee, ensuring the right people can access or manage relevant incident data.

User dashboard

Centralized Overview: The Incident V3 Management Dashboard provides visibility into incident reports, filtering by status, severity, date, and more.
Notifications: Each incident lists associated notifications. Users can view these in a modal window, with options to open attached files.
Report Filters & Download: Quickly locate incidents matching specific criteria and export them for offline review or recordkeeping.

Incident workflow & statuses

In Progress: Basic incident details and immediate actions.
Pending Review: Additional evaluation required.
Incident Review: Deeper investigative sections become available (e.g., external notifications, root cause analysis).
Outcomes: Capture lessons learned, final updates, and close out the incident.

Each status changes the available sections and the form’s required fields. Users can “skip” certain optional sections (Actions, Comments), then re-enable them later.

Create a new incident

Location & Primary Person: Begin by selecting the home (location) where the incident took place and identifying the primary person involved (Resident, Staff, or Neither).

Section-Based Data Entry: Based on the selected incident type (e.g., Health & Safety, Behavior of Concern, Data Breach), the system presents the appropriate subsections for users to complete.

Delete incidents

Delete: A permanent removal of an incident, also restricted to specific permissions (MyLocations_CanArchiveIncident). Prompts a confirmation modal before finalizing.

PDF export & history log

PDF Export: Generate a comprehensive PDF version of the incident report at any time from the Incident Screen Page.
Audit Trail: The History Log captures every modification—field updates, status changes, comment additions, or document uploads—along with timestamps and the user making the change.

Improvements

Email triggers (Incident V3)

Automated notifications

Configurable Triggers: Administrators can define when emails are automatically sent (e.g., upon incident creation, status change).
Multiple Recipients & CCs: Notifications can be directed to relevant roles, specific email addresses, or both.
Editable Content: Customize email subjects and messages to align with organizational policies.
Default Trigger Set: A default set of triggers is provided for quick configuration, but administrators can add and remove triggers as needed.

Benefits & impact

Increased Efficiency: Streamlined, customizable incident forms reduce time spent on irrelevant data entry and unify reporting processes.
Enhanced Visibility: The Incident Dashboard gives a clear, role-based overview of all open and closed incidents, improving collaboration and follow-up.
Improved Compliance & Traceability: Comprehensive logs and PDF exports ensure all changes are captured, supporting audits and compliance reviews.
Tailored Email Notifications: Automatic, targeted email triggers ensure the right stakeholders are notified at the right time.