I am a newcomer to Change Management but I know the principles of what is required. I am trying to bring Change Control to an IT department and I have begun to use a paper based RFC until my e-RFC is online. My difficulty is, trying to get the IT staff to understand the importance of completing the document, in FULL and with as much detail as possible that is relevant to the change they are requesting. It is very frustrating to have to return 9 out of 10 RFCs due to lack of care in filling out the fields.

I have guys who think that the answer to the question :

Impact and risk of change failure? is Minimal.

Does anyone have a typical RFC doc that they could share with me as I would like to see the type of questions that should be on there and what type of answers should be expected.

I've seen this type of response before when implementing change control, the answer is really simple: Training. All systems i've worked with were web based so i don't really have a template i can send/link for you and relatively most forms/questions really are the same, with the exception of those one off's that may be specific to your organization. I'm not sure of your technical ability, but what you can do for example is create your own change and fill it out as you would like to see it. Ideally if you have one particular group whom is really not the greatest at documentation, have a mock change created for an area that they are not familiar with at all and create two versions: 1) One filled out like they do 2) one Filled out as how it should be. See which they would prefer to be receiving/reviewing. Just a little bit to scratch the surface and allow them to see the light Just remember they are not doing it wrong, you're just helping them do it better _________________Adam
Practitioner - Release and Control
Blue Badge

"Not every change is an improvement, but every improvement requires a change"