For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Read RoPA readiness and pressure measures correctly, recognise the limits of the historical comparison and identify source records that need attention.
Before you start
Select the organisation and confirm access to RoPA Analytics, which is a beta surface in the recorded feature baseline. Understand the records included in the portfolio before drawing conclusions from a percentage.
This is a guide to interpreting the product's measures, not a legal compliance assessment. A readiness score is not certification that every processing activity is lawful or complete.
Read the current position
- Open the RoPA intelligence Analytics page.
- Wait for the current data or the explicit unavailable state.
- Review each current measure's label and value.
- Check the number of processing records measured and the status distribution beneath it.
- Note the evaluation version and latest capture information shown on the page.
- Use Refresh if you need the current fetched position, then check the displayed freshness again.
A measure based on a small or incomplete register should not be presented as the posture of every activity the organisation performs.
Compare history carefully
Read Monthly readiness and pressure history. The page distinguishes finding counts, which are portfolio totals, from percentage measures, which are portfolio averages.
Each historical point comes from captured snapshots. If History is accumulating appears, there may be current readiness data without a historical trend yet. Do not substitute zeroes for missing periods or assume refresh creates a new historical snapshot.
When a measure changes, compare the record population, measurement definition and capture timing before describing improvement or deterioration. More recorded activities can change a portfolio measure without any existing record becoming worse.
Follow up at the source
Return to the RoPA register or relevant source workspace and open the records associated with the issue. Inspect their actual completeness, findings and evidence before creating a task or changing a record.
Keep the metric, period and source-record references with the follow-up so someone else can reproduce the observation.
Check it worked
Your summary distinguishes current position from history, totals from averages, and unavailable data from zero. Any proposed action is based on inspected source records rather than the chart colour alone.
If something goes wrong
| Problem | Next action |
|---|---|
| Historical analytics are unavailable | Report the displayed limitation; do not invent a trend |
| History is empty | Allow snapshots to accumulate and use the current measures carefully |
| A percentage looks surprising | Check population, status distribution and measurement version |
| Dashboard and record differ | Compare capture times and report reproducible references |
Human judgement matters
Metrics help choose where to look. The accountable reviewer still decides what the evidence means and which corrective action is appropriate.
What next?
For the wider context, see Manage privacy records and assessments. Assign source-level follow-up and revisit the same measures after the evidence or records change.
Get help
Ask your Organisation Administrator about access or the task owner about the content. For a platform error, include this guide reference, the affected page and a sanitised message. Never share passwords, session details or confidential evidence in an open support request.