2. RFC Classification

After an RFC is created, it moves to the Classification Queue state, where it is assigned to a change manager. The change management team members selected when the RFC is created remain secondary owners, and can take ownership of the item if the change manager cannot complete the work.

You can use the Reassign transition in applicable states to assign the RFC to another change manager as needed.

Next, a preliminary assessment needs to be made of the RFC's importance. This occurs in the Classification state.

All fields are available for editing when you act on an item in the Classification state. This allows the change manager to modify the proposed values for the Priority, Urgency, and Change Category fields. The change manager can provide or update information that is critical for an accurate impact analysis of the RFC. In particular, the change manager can modify the values in the Primary CI and Affected CIs fields and the estimated Implementation Start Date and Implementation End Date.

The change manager must determine the type of RFC change. The Change Type value controls the path the change follows through the workflow.
From the Classification state, the change manager can choose from a variety of options, depending on the Change Type value:
Note: If the RFC was not submitted with linked items, the Linked Items tab does not appear on the Classification state form. The change manager must click Update to add linked items such as problems and incidents.