Connects change work to a Risk that should be considered with it.
When to use it
The Change Cockpit is the main UI for managing change types and their relationships. Use Change – Risk when a risk should be considered while evaluating or implementing a change.
Records and direction
- Relationship type: Non-structure. Associates the records without creating a parent-child hierarchy.
- From: Change Request, Change Order, Change Task.
- To: Risk.
How to use it
- Create the relation with drag and drop in a Structure widget: drag the intended Risk onto the Change Order it relates to. Select Change – Risk, review the source, target, and any offered values, then confirm.
- Alternatively, use Connect from the source record and choose the target and Change – Risk relationship from the available options.
- Review the resulting connection in the structure or related information. Check the selected records, their versions where applicable, and the relationship filters if the link is not visible.
Example
Implement Seal Redesign is connected to Prototype Delay. The Change Order provides the implementation context for reviewing that uncertainty.
What to check
The change record identifies relevant risk information. Review likelihood, consequences, and response information in the linked Risk.
Choosing the relationship
Choose Change – Risk for change-specific uncertainty. Change – Impact associates an assessment of consequences, while Risk associates broader product or work context with a risk.
