Skip to main content

Incidents 2.0 & More

We’ve released a major update to Incidents, with new ways to capture incidents, manage them, review them, and keep better records over time.

Written by Sarah May

Incidents can now start from Forms. In the Form Builder, you can mark a form as an incident form, then map form answers into incident fields such as title, description, date reported, priority, category, reported by, assigned to, location, and custom attributes. Once set up, these forms appear directly in the Incidents sidebar under Incident Forms.

You can also choose to create an incident report form form the Template Center, where you will be able to map System and Custom Attributes which will create the fields in the form based off those (easiest option).

These forms can be used internally or publicly, depending on how the form is published. From the Incidents sidebar, you can open the form, copy the link, and use it as a simple incident intake process for staff, teams, or external reporting where needed.

We’ve also added a new Board view for incidents. Instead of only working from a table, incidents can now be reviewed in a board-style layout, making it easier to see what is in triage, open, resolving, on hold, resolved, not an incident, or archived. The board can also support different groupings, including priority, severity, category, assigned staff, and reported by, giving teams more ways to manage their incident workload.

Custom Views have also been added to Incidents. You can now create saved views from filters, give them a name and icon, and access them from the Incidents sidebar. This is useful for teams that regularly check the same group of incidents, such as high-priority incidents, incidents assigned to a team member, or incidents in a specific category.

Incident profiles have also been improved. When an incident is created from an AI shift caution, the incident detail page can now show the linked caution details and appointment information. This includes details such as severity, client, appointment title, appointment type, shift start and end times, appointment address, shift notes, and the AI-generated category. This gives managers more context without needing to jump between the roster, notes, and incident record.

A new Pulse tab has been added to incident profiles. Pulse shows how long an incident has spent in each status, along with activity history for changes made to the record. This helps teams understand how an incident moved through the process, who changed what, and when key updates happened. This information is also included in the incident PDF export, so downloaded summaries now carry more of the incident’s history.

We’ve also made smaller improvements across the incident detail page, including better activity tracking, improved incident sidebar behaviour, stronger status history handling, and cleaner PDF output.

Bug Fixes & Improvements

A number of fixes and quality improvements were also included in this release:

  • Adding a List from a client profile now shows immediately without needing to refresh.

  • The Notify user button now appears correctly when creating shifts.

  • Timesheets no longer show staff rows with 0 hrs where they should not appear.

  • Prospect profiles now correctly show the prospect stage.

  • Prospects can now be deleted directly from the Prospects table.

  • Prospect note writing is alot smoother with less restrictions

  • Sites now support Split Count, allowing shared charges or billables to be split by a set number even when the actual number of clients on the shift is different.

  • Cancelled appointments are now removed from view correctly after cancellation.

  • Invoice descriptions now indicate when a billable entry came from a group shift.

  • Form PDF titles no longer add an unwanted space between title text.

  • Form submissions now show per form layout

  • Form builder paste control improvement

  • Updating or adding secondary task charges now updates without requiring a page refresh.

  • On mobile, the create-shift dialog now allows client and staff selector areas to scroll properly.

  • Other day-to-day fixes and improvements have been made in other areas to ensure Imploy functions the way it was meant to.

Did this answer your question?