At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Shared regulated terminology | Govern meanings and lifecycle | Reusable approved definitions | The app does not author policy conclusions |
| Confluence documentation | Scan and capture selected evidence | Findings, usages, revisions, and hashes | Page approval remains outside the app |
| Requirement and artifact links | Preserve approved trace evidence | Impact and provenance paths | Missing links can leave coverage gaps |
| Completed baseline | Verify and export | Release or audit evidence package | No certification or signature execution |
How it works
- Define the governed terminology scope.
- Create and approve the required terms.
- Scan the documentation space.
- Resolve terminology findings.
- Freeze the required evidence scope.
- Verify and hand off evidence to the owning control process.
Example
A team maintains a regulatory procedure in Confluence. The app controls the meanings used across that procedure, records scanner evidence, and freezes the exact revision used for a release. The QMS still controls approval and issuance.
What this does not mean
The app supports evidence around documentation. It does not replace authors, legal review, document control, page approval, a QMS, or an audit function.
Related questions
Next step
Use the app where terminology and evidence consistency create the largest documentation risk.
View on Atlassian Marketplace