The IG said that petitioner DIG Mian Farooq Nadeem could not have been appointed to the post of IG merely on the basis of seniority. He said the appointment is made on merit; the fitness of the civil servant is considered first and the seniority later.
The IG submitted that proceedings were initiated against the petitioner in 1999 on charges of mismanagement. He said Nadeem was also suspended from service for nine months and eleven days from June 11, 2002 to March 22, 2003 after a prisoner murdered another condemned prisoner on his watch.
The IG added that when the petitioner DIG attended the 93rd National Management Course the dean of the College wrote in his course report that he had little exposure, passable analytical skills, lacked leadership qualities and was sometimes tempted to indulge in self projection. The IG said his peers rated him low as a leader and a professional and only slightly higher as a friend. According to the IG, the dean considered Nadeem suitable for appointment to less challenging assignments within his service group.
Mian Farooq Nadeem, the petitioner DIG, had said that after the retirement of former IG Punjab prisons Sarfraz Ahmad Mufti, he (petitioner) was given the additional charge of the vacant post. He said his case for promotion against the vacant post was also forwarded to the provincial selection board by the Home Department. However, in February 2009 he was directed to relinquish the additional charge.
Later, the respondent Faisalabad DIG, Kokab Nadeem Warraich, was posted to the vacant post.
Nadeem had prayed that the appointment of the respondent be declared null and void and without lawful authority. He also sought the court’s directions for the government to consider him (petitioner) for appointment against the vacant post in the light of Punjab Civil Servants Rules 1974. The next date of hearing is November 25.
Published in The Express Tribune, November 5th, 2011.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ