Change Manager Filters Requests

[svien]

Change Manager Filters Requests is the one step in the Change management process that I am having a hard time understanding.
Is he/she basing this first filter on the impact/priority of the incident/Request ? (I know that it is categorized after allocating initall priority)
I cant see how the change manager will have enough technical ability to reject the RFC at this first juncture.
Does anyone have a detailed description of the Filter Request Step ?
Thanks in advance

[UKVIKING]

The filter can be used as the following

Is there enough information

plans
description
justification
etc

is it a change ?

It all depends on how your changes are raised
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[Globis]

To go a little further with John's reply, the first filter can be implemented simply enough in your tooling by ensuring that a change cannot be submitted until all the required fields in the (e.g. HTML) form are completed.

It is a simple as that (hopefully - people seem to delight in making change processes complicated - I'm not sure why).

As computers are not great at interpreting detail, you would have a second stage filter that simply reviews each request and then puts it forward to the CAB, refers it back to the requestor, or possibly redirects it somewhere else.

If you have multiple services, the 2nd filter is probably the change manager for that service anyway, which effectively means you are at the assessment stage proper.

[svien]

Thanks for the info guys.
For the next step in the process 'Allocates initial Priority' I have the same question again. the requester priority is subjective, what logic is the change manager using to allocate the priority ?

[svien]

One more thing. Categorizing the CR is ssessed on the basis of the impact of the problem and the urgency of the remedy.
Are they predefined impact and Urgency scales ?