Compliance Glossary for Confluence

What can a Confluence board compliance posture report show?

A board posture report can summarize recorded glossary governance, requirement coverage, page-scan evidence, gaps, and follow-up work. Use Dashboard for term status, Requirements Mapper for mapped-term readiness, and Audit Evidence Package for scoped evidence. Report the period and limits with every number. These operational signals support oversight. They do not certify compliance or replace management judgment.

Last verified against production v6 · 26 September 2026

At a glance

InputApp actionBoard-ready outputLimit
Current term statusesCounts approved terms against all stored termsGlossary Compliance Score, Total Terms, Approved, In Review, Draft, and DeprecatedThe percentage is an approval ratio, not a compliance outcome
Approval review datesFlags approved terms with no review in 6+ monthsStale Approvals requiring governance attentionThe visible list contains no more than 100 terms
A regulation or custom catalog and optional Consumer SpaceMaps required terms to governed glossary recordsReadiness, Approved Required, Needs Approval, Missing Terms, and Cross-Regulation ConflictsReadiness measures approved required terms; it is not legal compliance
Evidence scope, Period from, and Period toCollects supported stored recordsAudit Evidence Package with page status, scan history, and finding resolutionsSpace, period, record cap, and retained data bound the result
Retained scan snapshotsPreserves recorded scan states over timeScan history for period comparisonIt shows recorded states, not future performance

How it works

  1. Open Dashboard. Record the reporting date and each visible term-status count.
  2. Record Stale Approvals as governance work, not as a certification failure.
  3. Open Requirements Mapper. Select the relevant Regulation and Consumer Space (optional).
  4. Record Readiness, Needs Approval, Missing Terms, and Cross-Regulation Conflicts.
  5. Open Audit Evidence Export. Set Evidence scope, Period from, and Period to.
  6. Select Generate Evidence Package, then Open Print-Ready Package when a printable view is needed.
  7. Lead the board summary with scope, current gaps, owners, due dates, and the next decision. Keep the supporting package available for review.

Example

A quarterly report states that 90 of 120 terms are approved. Glossary Compliance Score is therefore 75%. Eight approvals are stale. The selected mapping shows 12 of 15 required terms approved, two needing approval, and one missing. The scoped evidence package supplies page status, scan history, and resolution records. Management then assigns owners and dates outside the metric itself.

What this does not mean

Compliance Glossary does not issue a board conclusion, certification, assurance opinion, legal opinion, or enterprise risk rating. Glossary Compliance Score and Readiness are narrow operational ratios. The application produces views and evidence records. Your organization writes the board narrative, validates scope, explains gaps, and owns each decision.

Related questions

Next step

Build the next board update from one dated Dashboard snapshot, one scoped mapping, and one Audit Evidence Package.

View on Atlassian Marketplace
Verification basis: production v6 code, tests, manifest, and operations guidance. Verified 26 September 2026.