A Change Order coordinates the work needed to implement a change. It connects the change context and implementation information to affected records and the activities needed to carry out the work.
When to use it
- Use it when change implementation needs a common coordination record.
- Use it to organize the scope, target dates, and related change activities.
Key information
- Identity and purpose: change order ID, name, description, reason, and summary.
- Implementation: target date, phases, deployment notes, and rollback plan where relevant.
- Tracking: priority, owner, state, due date, and completion percentage.
Common relationships
- Change Request – Change Order connects the proposal to this implementation record.
- Change Order – Change Task identifies the individual change activities.
- Affected Item identifies records within the change scope.
Working with this record
Confirm the intended scope and connect the work needed to implement it. Track the change tasks and affected revisions, and check the resulting product information. Follow the relevant lifecycle or workflow before recording implementation as complete.
Example
Seal Redesign Implementation is a Change Order connected to the seal Change Request. It contains Change Tasks to update the drawing and prepare the revised item information. The team tracks the target date and reviews the resulting definitions.
Choosing the right type
Choose Change Order for coordinated implementation. Choose Change Request for the proposal and Implementation Plan for an explicit description of the approach. The Change Order can coordinate work without replacing the engineering records being changed.
