'221 K-P court employees defrauded BISP'

Peshawar High Court issues show-cause notices


Yasir Ali April 23, 2020
Representational image. PHOTO: REUTERS

PESHAWAR: Over 200 employees of the high court and its subordinate courts in the districts have benefited from the Benazir Income Support Programme (BISP), stated a report submitted to the high court.

The Peshawar High Court (PHC) said in a statement on Wednesday that at least 221 employees in the establishment, district benches, anti-terrorism courts, district courts and labour courts were found to be receiving payments under the social welfare programme.

The BISP is now known as the Ehsaas Programme.

The high court expressed its strong displeasure over the fact that several court employees had benefited from BISP.

It maintained that no one will be spared and that strong action will be taken against culprits.

It subsequently issued show-cause notices to at least 22 of its employees named in the report.

The PHC further directed subordinate courts to take strict action against those employees who were benefiting from the programme - which is meant to provide financial assistance to those who are living below the poverty line.

New court timings

With the advent of the holy month of Ramazan, the PHC on Wednesday issued new timings for the courts. The PHC additional registrar in a statement said that from Monday to Friday, all PHC benches and lower courts will now open at 8am and close at 1pm. On Saturday, the courts will stop working at 12pm.

Meanwhile, the PHC has decided to appoint additional and sessions judges on the 26 vacant posts of BPS-20 in different districts and has called upon eligible candidates to submit their documents by May 30.

Any candidate– between 33 to 45-years-old–  with a bachelor of laws (LLB) degree and eight years of law experience can apply for these posts.

Published in The Express Tribune, April 23rd, 2020.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ