Removing Authority Need Not Be the Appointing Authority, But Cannot Be Subordinate in Rank: Supreme Court on Article 311

The Supreme Court has clarified the scope of the constitutional protection under Article 311(1) of the Constitution of India, holding that a government employee need not necessarily be dismissed or removed by the very same authority that appointed him. The constitutional requirement is that the authority ordering dismissal or removal must not be subordinate in rank to the authority that actually made the appointment.

In Union of India & Ors. v. Ramdhani Prasad, 2026 INSC 1047, the Court examined whether the removal of a Rakshak of the Railway Protection Special Force (RPSF) by an Adjutant violated Article 311(1). The dispute required the Court to identify the employee’s actual appointing authority from the contemporaneous appointment documents and then compare its hierarchical position with that of the removing authority.

Background of the Case

The respondent, Ramdhani Prasad, was initially enlisted as a recruit for the post of Rakshak in the Railway Protection Special Force. A call letter dated May 3, 1979, issued by the Commandant required him to report for initial training. Importantly, the appointment contemplated in the letter was subject to his successful completion of the prescribed training.

After successfully completing the initial training, a Battalion Order dated December 4, 1979 was issued by the Assistant Commandant, 2nd Battalion, RPSF, Gorakhpur. It recorded that the recruits concerned were appointed as Rakshaks with effect from December 4, 1979 and posted them to their respective battalions. Ramdhani Prasad was allotted personal number 2612 and posted to the 7th Battalion.

While in service, the respondent was granted 15 days’ casual leave along with permission leave from May 9 to May 26, 1982. He was required to resume duty on May 27 but remained absent until August 6, 1982—a period of 72 days—without intimation to the competent authority. A charge-sheet dated October 1, 1982 was thereafter issued alleging gross negligence and breach of discipline.

The departmental enquiry ultimately proceeded ex parte. The Enquiry Officer found the charges proved and, following a show-cause notice proposing removal from service, the Adjutant passed an order dated March 18, 1983 removing the respondent from service. His departmental appeal to the Commandant was subsequently rejected.

Proceedings Before the Courts Below

The respondent instituted a civil suit challenging the removal order as illegal and contrary to the principles of natural justice and Article 311 of the Constitution.

The Trial Court dismissed the suit. It found that the respondent had been validly appointed by the Assistant Commandant and that the Adjutant who ordered his removal was an officer not below the rank of Assistant Commandant. Consequently, it found no constitutional defect in the removal.

The First Appellate Court, however, reversed the decision. It treated the Commandant/Chief Security Officer as the appointing authority and concluded that the Adjutant who ordered the respondent’s removal was subordinate to that authority. It therefore held the removal contrary to Article 311(1).

The Allahabad High Court affirmed this conclusion on January 12, 2023. It similarly proceeded on the basis that the respondent had been appointed by the Chief Security Officer/Commandant and removed by an officer subordinate to the appointing authority. The Union of India consequently approached the Supreme Court.

Issue Before the Supreme Court

The principal question before the Supreme Court was:

Whether the respondent had been appointed as a Rakshak by the Commandant/Chief Security Officer through the call letter dated May 3, 1979, or by the Assistant Commandant/Assistant Security Officer through the Battalion Order dated December 4, 1979.

This determination was crucial because Article 311(1) protects a person holding a civil post under the Union or a State from dismissal or removal by an authority subordinate to the authority by which that person was appointed.

Call Letter Was Not the Operative Appointment Order

The Supreme Court closely examined the two documents.The May 3, 1979 call letter issued by the Commandant directed the selected candidates to report for initial training. The proposed appointment was expressly conditional upon successful completion of that training. Failure to qualify could result in discharge, while failure to report could result in cancellation of candidature.

The December 4, 1979 Battalion Order was materially different. After successful completion of training, it expressly recorded that the recruits were “appointed as RK” with effect from December 4, 1979. It also specified their grade and postings. The order was signed by the Assistant Commandant.

The Court held that this distinction was decisive. The earlier call letter did not contain an unconditional declaration that the respondent stood appointed as a regular Rakshak. Rather, it referred to an offer and candidature and made regular appointment dependent upon successful completion of training.

By contrast, the December 4 order expressly effected the appointment after the respondent successfully completed training.

The Court also rejected the argument that the December 4 order was merely a posting order. Relying upon Ramanand Singh v. State of Bihar, it observed that the same order may validly operate both as an appointment order and as a posting order.

A subsequent Battalion Order dated February 25, 1980 further supported this interpretation because it recorded that appointment orders as Rakshaks had already been issued with effect from December 4, 1979.

How Is the Appointing Authority Determined Under Article 311(1)?

The judgment lays down an important approach for determining the appointing authority. The Supreme Court held that, for the purposes of Article 311(1), a court must ascertain which authority actually made the appointment, having regard to:

  1. the operative order of appointment; and
  2. the statutory or regulatory framework governing the appointment.

Once the appointing authority is identified, the next inquiry is into the hierarchical position of the authority that subsequently passed the order of dismissal or removal.

Thus, the inquiry is not answered merely by identifying the highest authority that possesses overall control over appointments. What matters is the authority that in fact made the particular employee’s appointment, provided it was competent under the governing law.

Article 311(1): Rank, Not Identity of Authority, Is Crucial

The Court referred to its earlier decision in Krishna Kumar v. Divisional Assistant Electrical Engineer, Central Railway, (1979) 4 SCC 289.

That decision makes clear that Article 311(1) is violated where an employee is removed by an authority subordinate in rank to the authority that appointed him. It also establishes that merely delegating appointment powers to a subordinate officer does not elevate that officer’s hierarchical rank.

This produces an important distinction. Article 311(1) does not require dismissal or removal to be ordered by the identical officer or authority that made the appointment. It prohibits dismissal or removal by an authority that is subordinate in rank to the appointing authority.

Therefore, an authority of equivalent or higher rank may validly order removal, provided it is otherwise competent under the applicable statutory framework.

Statutory Scheme Under the RPF Act and Rules

The Supreme Court then examined the Railway Protection Force Act, 1957 and the applicable Railway Protection Force Rules, 1959.

Section 6 of the RPF Act provided that appointment of members of the Force would rest with the Chief Security Officer, but its proviso expressly contemplated exercise of appointment powers by other superior officers specified for that purpose. The Court therefore held that the Chief Security Officer was not the exclusive authority capable of making appointments.

Rule 20, read with Schedule I of the Rules, expressly empowered an Assistant Security Officer to appoint Senior Rakshaks and Rakshaks. The statutory framework therefore recognised the Assistant Security Officer as a competent appointing authority for the respondent’s post.

The disciplinary framework was equally significant.

Rule 43 provided that the disciplinary authority for imposing a particular penalty would be the authority specified in Schedule II under whose administrative control the member was serving, including an authority superior to it. Schedule II specifically authorised an Assistant Security Officer to impose the penalty of removal upon Senior Rakshaks and Rakshaks.

Section 9 of the RPF Act also made the disciplinary powers of superior officers expressly subject to Article 311 and the Rules.

Reading these provisions together, the Supreme Court concluded that although overall control in appointments rested with the Chief Security Officer, the statutory scheme permitted other competent superior officers to make appointments. In particular, the Assistant Security Officer could both appoint a Rakshak and impose the penalty of removal upon a Rakshak.

Removing Authority Was Not Subordinate to the Appointing Authority

Having identified the Assistant Commandant/Assistant Security Officer as the authority that appointed Ramdhani Prasad, the Court considered whether the Adjutant who removed him was subordinate in rank.

The material placed before the Court showed that the Adjutant, Shri I.J. Singh, was of the same rank as the Assistant Commandant/Assistant Security Officer who had made the appointment. The Trial Court had also recorded that the Adjutant was not lower in rank, and the respondent had produced nothing establishing that the Adjutant was subordinate to the Assistant Commandant.

The Supreme Court then stated the controlling constitutional principle: the prohibition under Article 311(1) is attracted only where the dismissal or removal is ordered by an authority subordinate in rank to the authority by which the employee was appointed. That essential requirement was absent in the present case.

Accordingly, the Court held that the respondent had been appointed as a regular Rakshak by the Assistant Commandant through the December 4, 1979 Battalion Order. The May 3 call letter was merely a communication requiring selected candidates to undergo prescribed training and was not the operative appointment order.

Since the removal order was passed by an authority not subordinate in rank to the appointing authority, and that authority was competent under Schedule II to impose removal, the order could not be invalidated under Article 311(1).

Ex Parte Departmental Enquiry and Natural Justice

The respondent separately argued that the departmental proceedings were invalid because the enquiry had proceeded ex parte while he was ill.

The Supreme Court did not accept this contention. The record showed that the respondent had acknowledged the charge-sheet dated October 1, 1982 and submitted his response. He was thereafter informed that the enquiry had been fixed for January 1, 1983 but failed to appear. The Enquiry Officer consequently proceeded ex parte. A show-cause notice proposing removal was later issued, but the respondent did not submit a representation.

While reiterating that natural justice requires a reasonable opportunity of defence, the Court found that the respondent had been made aware of the disciplinary proceedings and had been afforded an opportunity to participate. On the particular facts, the enquiry could not be treated as vitiated merely because it proceeded ex parte.

Supreme Court’s Decision

The Supreme Court allowed the Union of India’s appeal and set aside the January 12, 2023 judgment of the Allahabad High Court as well as the decision of the First Appellate Court.

It restored the Trial Court’s dismissal of the respondent’s suit and consequently restored the order dated March 18, 1983 removing the respondent from service.

Click Here to Read the Official Judgment

Significance of the Judgment

The decision provides a useful clarification on the operation of Article 311(1). The constitutional provision does not create a rule that the employee can be removed only by the very authority or officer who signed the appointment order. Rather, it establishes a minimum hierarchical safeguard: the removing authority cannot be lower in rank than the authority that actually appointed the employee.

The judgment also shows why identifying the operative appointment order is critical. A selection letter, offer, training call or preliminary communication cannot automatically be treated as the appointment order merely because it emanates from a higher authority. Courts must examine the language and legal effect of the relevant documents along with the governing statutory rules.

At the same time, statutory competence and constitutional hierarchy remain distinct considerations. An officer may possess disciplinary powers under service rules, but Article 311(1) must still be satisfied. Conversely, where the removing authority is not subordinate to the actual appointing authority and is independently empowered under the applicable rules to impose removal, Article 311(1) does not invalidate the action merely because the removing authority is different from the appointing authority.

The ruling in Union of India & Ors. v. Ramdhani Prasad thus reinforces a precise formulation of the protection: the identity of the appointing and removing authorities need not be the same; what Article 311(1) prohibits is removal or dismissal by an authority subordinate in rank to the authority that actually made the appointment.

Important Link

Law Library: Notes and Study Material for LLB, LLM, Judiciary, and Entrance Exams

Read More