Explanation of change management statuses

Status	Description	Time frame
New	Change initiator has entered a request.
Added to backlog	Change request has been added to the backlog of Technology Services and will be evaluated based on priority.
Researching	Collecting requirements and defining scope. Ultimately determining that if what is wanted by the change initiator can be accomplished.
Evaluating	Proof-of-concept (POC), scope, and requirements have been defined enough that change coordinator has everything they need to develop a plan and/or options.
Awaiting approval	Change advisory board (CAB), stakeholder group, or service owner needs to approve the change.
Scheduling	Determining time for work to be accomplished and released to end user.
Assigned release	Release/version has been established, but work still needs to be started.
Implementing	Development, testing, and documentation is being completed.
Awaiting deployment	Work has been completed and tested, but waiting for deployment to production system.
Closed	Performance targets have been met and change initiator has accepted the change.
Waiting for customer	Request is waiting on the response from a customer.
Waiting for support	Request is waiting for support through the Service Desk.
No response	The customer does not respond with 60 hours of the issue (following the same calendar as the SSD Technology Department) then an issue will move into a No response status.	60 hrs.
Pending closure	The customer does not respond with 30 hours of the issue (following the same calendar as the SSD Technology Department) then an issue will move into a Pending Closure status.	30 hrs.