How this connects: from a risk, a deadline and a score back to their source

Steps

1. 1

   Start from a risk in the register

   Open Risk Register. The risk that begins Data breach, HIGH, was not typed by anyone. Its Source column carries the red label Data Breach, which tells you which module it came from. Its score, sixteen, was worked out from the breach's severity.

   • Select Collapse section list
   • Select Hide insights panel
2. 2

   Open the breach it came from

   In the left menu, under Legal and Privacy, choose Data Protection, then Breach Log. Here is the source: the breach Courier handheld lost with customer delivery list, logged by the Data Protection Officer with the severity High and still open. The risk's description repeats this breach's status, the number of records affected and whether the regulator must be told.

3. 3

   Know what closes the risk

   The link runs one way, from the breach to the risk. When the Data Protection Officer closes this breach, the next sync, by the Sync Modules button or overnight, sets the risk to CLOSED and adds a note that the source issue was resolved. The same holds for the other sources: an approved impact assessment, an ended contract, a cleared sanctions screening or a regulatory alert marked as read. Changing the risk in the register never changes the breach.

4. 4

   Now start from a deadline

   Open Calendar and select VAT Return Filing, 2026-07-01 to 2026-09-30, in Upcoming Deadlines. Its detail box carries the label VAT and the button View Source. The title names the tax period, so you know exactly which return this deadline belongs to.

5. 5

   Select View Source

   Select View Source. Tax Intelligence opens, the module that owns the return. The return for July to September was prepared there by the tax manager, under Returns, and that is where it is reviewed and filed. When it is filed, or its filing is recorded in the Filing Tracker, the deadline in the calendar becomes Completed, and a later sync does not reopen it.

   • Select View Source

   

6. 6

   See a compliance check read another module

   Open Frameworks and select Tasks. Scroll to UAE Data Protection. Under Automated Checks, Data Subject Requests Within SLA reads Record Found. Nobody typed that. The check looked in Data Protection, found the request logged there and saw that it is still within its deadline. Every automated check reads a module in this way: the tax registration number from the entity's profile, returns from Tax, staff records from Workforce.

   • Select Tasks51 (51)
7. 7

   Read the entity's score on its dashboard

   Now the scores. Choose Dashboard in the left menu. The entity's compliance score is here, with the line Based on a number of modules. Each module works out its own score from its own records, and the entity's score is the average of the modules in use. The health score beside it lists each module in use with its own score. Which modules count, and the bands for each risk level, are chosen in the Modules and risk levels window, which the Getting started course walks through.

8. 8

   Find the same score in the group view

   Choose Group Compliance. The same entity is listed with the same overall score, the same line, Based on a number of modules, and the same module scores beside it. The group score at the top is the average of the entities shown. So the chain is: a record in a module moves that module's score, the module's score moves the entity's score, and the entity's score moves the group's.

9. 9

   Carry the chain back to the work

   Top Risk Areas closes the loop. It names the entity and the module with the lowest scores. Open that module for that entity, deal with what it flags, and the improvement travels back up: the module score, the entity score, the group score, and at the next sync the risk register and the calendar. That is the whole of this course in one sentence: these pages show you where to look, and the modules are where the work is done.