An Enterprise Change Assessment records the effects of a proposed change or problem. It helps the team describe consequences for product information and related work before deciding how to proceed.
When to use it
- Use it when the effects of a change or problem need their own assessment record.
- Use it to make the scope and severity of the consequences understandable during review.
Key information
- Assessment identity: assessment ID, name, description, and impact type.
- Assessment context: impact severity, instructions, and comments.
- Review tracking: owner, state, due date, and estimated dates.
Common relationships
- Change – Impact connects a change proposal or implementation record to the assessment.
- Impact connects a Project, Issue, Problem Report, or other eligible record to the assessment.
- Risk – Impact associates a Risk with the assessment.
Working with this record
Describe the consequences and the information reviewed to reach the assessment. Keep its scope clear so reviewers know which product or work context it covers. Update it when the proposal or investigation changes materially.
Example
An Enterprise Change Assessment for the seal redesign describes the effect on the pump drawing and review work. It is linked to the Change Request so reviewers can consider these consequences together with the proposed modification.
Choosing the right type
Choose Enterprise Change Assessment for the effects being evaluated. Choose Risk for an uncertain event and Change Request for the proposed action. The assessment supports a decision; it does not itself implement the change.
