Gap analysis
Recording how far you are from being able to answer, so the work can be planned.
- Permission
- Read and write on the report to edit; read to view
Gap analysis is planning, not reporting. It records, per data point, how much of the data you already have and how much work it will take to get the rest. No AI is involved and nothing here appears in the published report.
Recording a gap on a data point
Open a data point and choose Gap analysis from its toolbar.
| Field | What it records |
|---|---|
| Data coverage | How much of the needed data you already have, 0 to 100 per cent in steps of ten. |
| Remaining effort | How much work is left: XL, L, M, S, or No work. |
| Automation level | How automatable that work is: XL, L, M, S. |
| Comment | Free text: where the data sits, who owns it, what is blocking. |
Every field saves as you change it. The fields are read-only when the report is not Active or you have read-only access.
The overview table
Gap analysis in the main navigation shows every recorded gap across a report in one sortable table: topic, disclosure, data point, coverage, remaining effort, automation level, responsible user, when it was last updated, and the comment. Coverage is colour-coded so the weak areas stand out.
Pick the report at the top of the page. Show on any row jumps straight to that data point's gap panel.
Using it
The table is the planning artefact. Sorted by responsible user it is a work list per person; sorted by coverage it shows where next year's data collection needs to improve; filtered mentally to high effort and high automation, it is the case for investing in a data pipeline.
Data points that have been switched off in a report do not appear.
