Release highlights

This update introduces a dedicated space for structured incident analysis, adds a new export option for the Audit Log, and gives organisations more control over how their organisational units are structured and displayed. Language coverage has also been extended.

  • New Incident–Event Analysis section for collecting structured incident attributes directly in a case
  • Audit Log export to Microsoft Excel (.xlsx)
  • Hierarchical tree structure for organisational units
  • Custom ordering of units in dropdown lists
  • 5 new languages added to the whistleblowing portal


What’s new in this release

1. Incident–Event Analysis

Cases now include a dedicated Incident–Event Analysis section for collecting structured information about the incident itself.

Previously, this kind of data could only be gathered through the registration form, which came with practical limitations: attributes could not be edited after registration, and they could not be reused across cases. The new section removes those constraints.

  • Incident attributes can be added to any case, at any stage
  • Attributes remain editable after case registration
  • Data is standardised across cases, improving comparability and traceability

The result is a more consistent basis for incident analysis and a stronger audit trail, and it lays the groundwork for deeper linkage between cases and analytical reporting.

2. Audit Log export to Excel

The Audit Log can now be exported directly to Microsoft Excel (.xlsx) for easier analysis, filtering, and sharing with stakeholders.

Exported reports now also include a clear report heading, making the output easier to read and easier to circulate outside the system.

To use it, open the Audit Log page and select the Excel export option to download your report.


Improvements

Tree structure for organisational units

Organisational units now support parent–child relationships, so your unit list can mirror the real structure of your organisation.

Parent units can be assigned either through the interface or via settings files. Unit dropdowns display the resulting hierarchy as a tree, making it faster to find and select the right unit in larger structures.


Custom unit order in dropdowns

A new reorder mode in Admin > Units lets you define the exact sequence in which units appear in dropdown lists.

A dedicated Order column has been added to the units interface, and the configuration is stored in the settings file so the chosen order is applied consistently across the system.


Expanded language support

Five new locales have been added to the whistleblowing portal interface:

  • Bahasa Indonesia
  • Bislama
  • Burmese (Myanmar)
  • Fijian (iTaukei)
  • Solomon Islands Pijin

This continues our work on making the reporting channel accessible to as broad an audience as possible, with particular focus in this release on Southeast Asia and the Pacific.


Bug fixes

  • No bug fixes were included in this release.


Why this release matters

This release focuses on structure and evidence. The Incident–Event Analysis section makes incident data consistent and reusable rather than locked into the moment of registration. The unit hierarchy and custom ordering let larger organisations represent themselves accurately in the system, which reduces misrouted reports. Excel export makes audit data easier to work with outside the platform.



Recommended next steps

  1. Review your organisational unit list and consider whether a parent–child structure or a custom display order would make report intake easier for your users.
  2. Assess whether the Incident–Event Analysis section should become a standard part of your case handling process.
  3. Confirm whether any of the newly added languages are relevant to your reporting audience and enable them in your intake channels.