What Are the Implications of Changing Information in Assurance

In this article, you will learn about:

• Changing the Risk Matrix Setup
• Changing Fields in Forms and Registers Templates
• Changing the Due Date on a Task or Checklist
• Changing the Business Unit Hierarchy

Changing the Risk Matrix Setup

If you change specific details on the front tab of the Risk Matrix Set up once a Risk Register is in Assurance, you will need to re-rate all your risks in your Risk Registers for the change to take effect. Your reports will reflect incorrect information until the risks are re-rated. The specific details are:

• Changing the Risk Matrix Type
• Changing a Square on the Risk Matrix
• Adding, Removing or Rearranging the Consequence, Likelihood, Control Rating, Inherent Risk, Residual Risk and Risk Rating

The following changes will not require re-rating of your risks:

• Changing the Titles or Definitions of Consequence, Likelihood, Control Rating, Inherent Risk, Residual Risk, Risk Rating and Target Risk.
• Changing the Colours of an Inherent Risk Rating, Residual Risk Rating or Risk Rating.

Changing Fields in Forms and Registers Templates

Change a type of field once data is against it, you will need to archive the old field (make inactive) and create new one. Please read this guide for implications to consider when changing fields in Assurance. Often the change you make will result in pre-existing data not being visible on your forms anymore and only through the History tab.

Changing the Due Date on a Task or Checklist

Moving a due date on a repeated task or checklist after the date has been triggered (the task assigned) or it has been answered, will delete the pre-existing data on the assignment. Instead, you must raise a new assignment and retire the previous.

Adjusting when a repeated assignment ends cannot be done in retrospect once the assignment has been created. A new assignment should be created and retire the previous. See this article for more information.

Changing the Business Unit Hierarchy

Aiming to get as close from the start to what the structure will be is important. For example, if you answer a task from Business unit A, but in the future the tasks will be answered from a new child business unit, then you need to make a note of the change for reporting purposes.