At a glance
| Evidence | Recorded data | Auditor use | Limit |
|---|---|---|---|
| Scanner finding | Page, term or candidate identifier, finding type, message, and context | Explain what the scanner found | Source page body text is not included in the evidence export |
| Acknowledge | Status plus optional owner, due date, and severity | Show that remediation has been accepted | Acknowledgement does not fix the page or term |
| Justify | Human-entered Justification... | Explain why the current usage is accepted | A non-empty justification is required |
| Close | Human-entered Closure evidence... | Record the evidence used to close the work | Closure evidence is required; closing does not execute the remediation |
| Resolution save | Page ID, term ID, canonical term name when available, status, actor, and time | Identify who recorded the current disposition and when | The same finding key stores the latest resolution state, not every resolution transition |
| Follow-up scan | Page status, finding count, scan time, page version, and glossary revision | Show the terminology state observed after the response | A scan proves its recorded point in time only |
| Download Evidence Package CSV | finding_resolution, page_status, and scan_history rows | Correlate records by page and term identifiers | Rows are separate; the app does not write an auditor narrative |
| Open Print-Ready Package | Page scan status and a Finding Resolutions table | Present a readable evidence summary | The printable resolution table omits page and term IDs; use CSV for identifier-level correlation |
How it works
- Open Compliance Scanner and locate the page-level finding.
- Record Owner..., due date, and Severity.
- Select Acknowledge when the work is accepted.
- If the usage is an accepted exception, enter Justification... and select Justify.
- If the issue is remediated, enter Closure evidence... and select Close.
- Select Scan Space after the page or glossary change.
- Open Audit Evidence Export.
- Set Evidence scope, Period from, and Period to.
- Select Generate Evidence Package, then Download Evidence Package CSV.
- Correlate the finding_resolution row with page_status and scan_history by Page ID. Use Term ID for the governed term record.
Example
A scan flags “AE” as a non-preferred synonym on page p1. The QA lead records high severity and a due date, then selects Acknowledge. The page is updated to “Adverse Event.” The lead enters the approved change record under Closure evidence... and selects Close. A follow-up scan records the current page version. The CSV contains the resolution, actor, time, page ID, term ID, and separate scan evidence.
What this does not mean
A resolution is a human-recorded disposition. It does not edit Confluence content, approve a term, or certify compliance. The stored record reflects the latest resolution state for that finding key. Scan history is separate evidence. Correlate it by page and time. Keep the exported CSV when page and term identifiers are required; the print-ready package is a summary.
Related questions
Next step
Record one complete disposition, run the follow-up scan, and export the scoped CSV before the auditor review.
View on Atlassian Marketplace