At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Retained affected artifact | Create its glossary slice | Artifact-bound terminology evidence | Complete indexed usage evidence is required |
| Baseline and archive identities | Bind the handoff to frozen evidence | Verifiable source context | Invalid archive references are rejected |
| Change context | Record why reissue is required | Review context for the external owner | The app does not judge release readiness |
| Required external actions | List document-control work | External-only handoff | Execution and signatures remain outside the app |
How it works
- Calculate impact for the approved change.
- Select the affected retained artifact.
- Confirm its glossary slice can be generated.
- Select Download reissue handoff.
- Validate the handoff identity and hash.
- Complete reissue and approval in the external system.
Example
A term change affects a controlled procedure. The handoff includes that procedure's retained identity, the relevant frozen meanings, usage evidence, baseline and archive references, and required external actions. The document-control team completes revision, approval, issuance, and signatures in its qualified system.
What this does not mean
The handoff prepares evidence and scope. It does not replace document control, a QMS, release approval, or signature execution. External owners remain responsible for the controlled reissue process.
Related questions
Next step
Use a handoff when affected controlled artifacts require action outside Confluence.
View on Atlassian Marketplace