To ensure that all affected parties are fully aware of a change, a change form passes through a series of lifecycle states between originating and completing the workflow. Although there are other possible paths, this is the principal workflow.

1. The change form is made, or Originated. The originator is typically responsible for the clarity and completeness of the change form's technical content. The originator attaches the affected items and provides more information to help the reviewers evaluate the change form's effects. SeeOriginate a new change form.

2. The originator may submit the change form to an analyst for review. The analyst checks that the change form's content meets an accepted standard. This typically includes (a) review of the change form's purpose, priority, and costs; (b) validation of the Affected items list; and (c) verification that the appropriate reviewing groups have been included. See Analyze a submitted change.

3. The change form is routed to reviewers for their approval. On behalf of their group, each reviewer can approve ordisapprove the change. The reviewer can also hold the change form while the originator or analyst answer a question about the change form. Based on their responses, the reviewer can approve or disapprove it. See Review a routed change.

4. At the end of the review:

   • If any one required reviewer disapproves the change form, then it isCanceled and removed by the analyst. SeeRemove a canceled change.

   • If all required reviewers approve the change form, then it isAccepted and forwarded to (a) the analyst for further review or (b) the system to beReleased. See Use a released change.

5. After the instructions contained in the change form have been implemented, the status can be set toCompleted. See View a completed change.

In most lifecycle states, an analyst can cancel the change form, or return it to Submittedor Originated status.

1099