Manage changes and effective revisions
Understand the impact before activating a new definition or procedure.
Start with a proposal
Describe the change and why it is needed. Compare it with the effective revision, including fields, rules, instructions, limits, relationships, and allowed actions. Give reviewers enough context to assess the operational effect.
Review the affected work
| Area | Question to answer |
|---|---|
| Existing records | Will earlier records remain interpretable? Is a migration needed? |
| In-flight work | Which source revision continues to govern each execution? |
| People | Who needs review, training, or acknowledgment? |
| Integrations | Does a mapping, consumer, or event contract need updating? |
| Assurance | Which requirements and tests need renewed evidence? |
Make activation explicit
- Complete the required reviews and resolve blocking findings.
- Verify the changed behavior with representative and exceptional cases.
- Agree the effective date and treatment of in-flight work.
- Activate through the configured approval path.
- Inspect the first affected executions and retain the verification evidence.