Change Submission involves thorough assessment of the proposed change and its various attributes - like its Impact, Risk involved, Urgency, Priority etc. – based on which the methodology needed for deploying the change (workflow and template) will be worked out.
First step in Change Submission is creating a Change Request using New Change form
But before accessing the change form, you have to plan the following:
Decide Change Template (see: Configuring Change Template for more info)
Decide Change Workflow (see: Configuring Change Workflow for more info)
Then, create the change request, by filling out the new change form
Changes are of two types: new and retrospective. New change(s) are implemented when organizations demand for an unexpected change in the environment which hasn't been dealt with previously. In this case, the procedure for handling the change is not known and therefore has to be worked out from scratch. Example: keeping IT organizations updated based on the technology changes (occurring in the industry) whose pattern cannot be predicted easily.
Changes which have been already implemented based on need/urgency by getting approvals through voice calls, mails etc. are known as retrospective changes. These changes will be recorded for tracking purpose.
For scenarios that demand the change to be implemented immediately without any delay, Emergency Change will suit them better. With a change workflow that skips the basic preliminaries (submission and planning), Emergency Change ensures change(s) get implemented immediately to meet the pressing deadline.