Who is this article for?

Administrators who want to learn how to use queued master Risks.

Administrator permissions are required.

Efficient risk management often involves reviewing and incorporating new risks or updates from various projects into a centralised master risk register. This article explores the concept of queued master risks in Lucidity Risk, guiding you through the process of evaluating, accepting, or discarding proposed changes to ensure your master risk register remains comprehensive and up-to-date.

1. Queued Master Risks
2. Queued Master Risks menu
3. Review Forwarded Risks
   1. Reviewing a new Risk
4. Accepting or discarding recommended changes
   1. Accepting changes
   2. Discarding changes
5. Filtering to view processed Queued Master Risks
6. Reporting from Queued Master Risks
7. Further reading

1. Queued Master Risks

Project managers can recommend new risks or changes to existing risks be added to the master risks for system administrators to review. Once this occurs, the recommendation will be listed on the Queued Master Risks page. It is now the system administrators task to review them for possible inclusion into the master risk register and templates. This allows for continual improvement on managing risks throughout the business.

2. Queued Master Risks menu

The Queued Master Risks menu provides a list of the queued master risks that have been recommended by project managers or administrators.

In the Queued Master Risks page, administrators can:

• Review forwarded risks for inclusion in the master risk register.
• Accept or discard recommended changes to new and edited risks.

The Queue Type field identifies if a queued risk is a newly created risk or an updated/ edited risk.

3. Review forwarded Risks

To review a forwarded new or edited risk, from the Queued Master Risks page:

1. Use filters to locate the risk to be reviewed.
2. Click Review on the far right of the risk.

3. All suggested changes will be clearly highlighted with the existing value displayed next to the recommended change. Review the recommendation, and either.

4. Click Accept Change? or Ignore the suggested change and continue to the next suggestion.

5. Repeat until all recommendations have been reviewed and then either

   • Click Accept if all or some changes are to be accepted.
   • Click Discard if no changes are to be accepted.

4. Accepting or discarding recommended changes

4.1. Accepting changes

Accepting one or more of the recommended changes will:

• Update the master risk in the master risk register.
• Update any templates where the risk is included.
• Do not update any project risk registers where the risk is included. Each project risk register that. includes the risk will need to be updated manually if the changes are required.
• Change the status of the queued master risk to Accepted.

4.2. Discarding changes

Discarding the recommended changes will:

• Have no impact on the master risk in the master risk register.
• Have no impact on any templates where the risk is included.
• Have no impact on any project risk registers where the risk is included.
• Change the status of the queued master risk to Rejected.

5. Filtering to view processed Queued Master Risks

Once processed, queued master risks will not be visible by default. Use the Queue State to view processed queued master risks.

6. Reporting from Queued Master Risks

To generate a report for a specific group of queued master risks, from the Queued Master Risks page:

1. Click Show Filters.
2. Select the relevant filters.
3. Click Filter.
4. All results will be displayed at the bottom of the screen.
5. Click Excel Export to generate this report into Excel.

7. Further reading

• Adding, editing and deleting Master Risks
• Using critical risk controls
• Forwarding Risks and generating a project Risk register report