A Change Task is an individual work activity undertaken as part of a change. It gives that activity a managed identity and lets the team track its responsibility, progress, scope, and outcome.
When to use it
- Use it to identify a specific piece of change implementation work.
- Use it when the activity should remain connected to the change and the records it affects.
Key information
- Activity identity: change task ID, name, description, and instructions.
- Change context: reason, summary, priority, and scope.
- Work tracking: due date, estimated dates, completion percentage, and work log.
Common relationships
- Change Order – Change Task connects the activity to its implementation coordination record.
- Assignee identifies the responsibility expected to perform the work.
- Affected Item identifies the engineering or information records involved in the activity.
Working with this record
Describe a specific outcome, identify the affected records, and assign responsibility. Save the activity’s progress and work information. Follow its available completion or lifecycle action and check that the engineering outcome has been achieved.
Example
Update Seal Drawing is a Change Task under the seal Change Order. It identifies the drawing to update and the intended outcome. The assigned reviewer can track the work and confirm that the drawing information matches the agreed change.
Choosing the right type
Choose Change Task for a defined activity within change work. Choose Task for general work and Change Order for the coordination of several change activities. A Change Task is a distinct change record, rather than simply a renamed general Task.
