v2024.16

Release Highlights | 20th August | Version 2024.16

As part of our optional QUOODA® Building Safety Act (BSA) pack, our August release introduces a new Mandatory Occurrence Reporting Module, allowing users to ensure that details of reportable occurrences are captured and available within QUOODA®.

The Building Safety Act legislation is specific to Higher Risk buildings where the buildings falling within the scope of the act require mandatory registration with the Building Safety Regulator.   

If you have not yet taken advantage of our Building Safety Act (BSA) pack and would like to obtain more information, then please contact your dedicated account manager. 

Mandatory Occurrence Reporting Module

Mandatory Occurrence reporting is required following certain occurrences.  When it is necessary to submit a Mandatory Occurrence notice, QUOODA® now allows you to internally approve and then capture the notice and submission process.

The new module links to our existing Adverse Events module where incidents or reportable conditions are captured, investigated, and reported seamlessly.

Security

Mandatory Occurrence security options have been added to allow system administrators to manage role access to this new module either at basic Mandatory Occurrence user or at Mandatory Occurrence Manager level:

The table below outlines necessary permissions required within Settings – Security for each action against Mandatory Occurrence. 

MO = Mandatory Occurrence

MOM = Mandatory Occurrence Management

Module visibility

Given the user has a minimum of Mandatory Occurrence – Read permissions via Settings – Security, they will be able to see the Mandatory Occurrence Module on their menu, as well as the Mandatory Occurrence tab on all saved Incident and Adverse Event forms:

Mandatory Occurrence Tab on Adverse Events Module

Users with Mandatory Occurrence – Edit permission will see a new tab on all Adverse Events forms, allowing them to request that the relevant Adverse Event record is considered for potential notice with the Building Safety Regulator:

Users must have access to Mandatory Occurrence – Edit permissions to add a new Mandatory Occurrence record*:

*Please note that a single incident can only have 1 active Mandatory Occurrence at a time.

Mandatory Occurrence Management

When Mandatory Occurrence requests are raised, users with relevant property access and Mandatory Occurrence Management – Edit permission will receive an automated email notification of the request.

Users with Mandatory Occurrence – Read permissions will only be able to view MOs for their buildings on the MO grid:

Only users with Mandatory Occurrence Management – Read permissions will be able to view the details of the submitted MO. Users with Mandatory Occurrence Management – Edit permissions will be able to decide on whether the MO should be Accepted or Rejected: 

Guidance is provided at every stage of the MO:

Once Rejected, MO will be closed, and users can raise a new Mandatory Occurrence for the same incident. 

Once Accepted, MO can be marked as Notified – users will need to input the Occurrence Notice Reference number provided by the regulator:

Once MO has been Marked as Notified, it can be marked as Report Submitted – we encourage users to attach the report submitted as well as any supported documents within the Documents section of the form: 

Once MO is marked as Report Submitted, the form is complete, however, additional documents can still be attached. 

Throughout the entire process, the latest status of the MO will be displayed on the Incident/Adverse Events form:

If you are not yet a BSA pack user, then please contact your dedicated Account Manager to enable the BSA module or any Mandatory Occurrence related guidance.