Approving RFCs

Discuss and debate ITIL Change Management issues
Post Reply

Is it a best practice for a technical RFC to be reviewed and approved by a technical person who has relevant skills and experience in the topic RFC is about?

No votes
Total votes: 3
User avatar
Posts: 1
Joined: Sun Dec 03, 2017 7:00 pm

Mon Dec 04, 2017 4:54 pm

Hi All,

I have a question regarding RFC approval.

Our organization is following ITIL.

In our organization RFCs are sent for approval to selected 2nd line, 3rd line and solution architects.

RFCs I often write are about specific technical products, for example, AppSense, that no one from RFC approving team has no skills nor experience in. So for them its a grey area.

My understanding is that a techical RFC should be reviewed and approved by someone who has relevant technical skills and experience in the topic RFC is about so that they could provide a second opinion and correct RFC and/or identify potential issues that it can cause.

My first manager says that approving RFC doesn't mean having technical knowledge, it is just about checking that all RFC fields are accurate.

My second manager says that I should assign RFC to approvers then teach them AppSense so that they could learn as they go and approve my RFCs on the same time.

I say that teaching someone in order to review and approve my work is a bit ridiculous and offensive for me and I expect my work to be reviewed by a relevant professional who has at least the same level of knowledge as I do so that they could review my work.

Could you please advise what ITIL guide says about this? Is it a best practice for RFC approvers to have relevant skills and knowledge in the topic RFC is about or it is not required?


Post Reply