Why Does the Indian Army Still Reflect Caste and Colonial Labels
Every Republic Day, India sees the Army march in perfect rhythm. The uniforms, drill, music and regimental pride are treated as symbols of national unity. Less visible is the question behind many of those names: why do some units still carry labels such as Jat, Rajput, Sikh, Maratha, Garhwal and Dogra?
The issue is not whether soldiers from these units have served with courage. They have, across wars, insurgencies and disaster relief. The harder question is institutional. Why does a republican army still preserve a structure shaped in part by colonial ideas of “martial” and “non-martial” communities? Why is caste data inside the force so limited in public view? Why do courts and governments treat military organisation as a special case, even when equality claims arise?
This is a policy analysis, not legal advice. It looks at caste-based regiments, President's Bodyguard recruitment, AFSPA accountability and military reform India through one lens: public institutions earn trust not only through service, but through scrutiny.
The Army’s regimental system carries a colonial inheritance
The Indian Army’s regimental system did not begin as a neutral administrative choice. Under British rule, recruitment patterns hardened around the “martial races” theory. Colonial authorities claimed that some communities and regions were naturally suited for soldiering, while others were not. This was not science. It was an imperial sorting system, shaped by the needs of control, loyalty and recruitment after the 1857 revolt.
The labels varied across time, but the logic stayed familiar. Certain castes, tribes, religious groups and regions were treated as especially “martial”. Others were pushed to the margins of recruitment. The colonial state linked physical stamina, loyalty and fighting ability to community identity. It then built units around those categories.
Independent India inherited that structure.
Some regiments were reorganised. The Army expanded. Recruitment opened wider across many arms and services. Yet several infantry regiments still carry community or regional names. Examples include:
Jat Regiment
Rajput Regiment
Sikh Regiment
Maratha Light Infantry
Garhwal Rifles
Dogra Regiment
Gorkha Rifles
These names do not prove present-day discrimination by themselves. Regimental names also carry battle honours, traditions, songs, memorials and a sense of belonging. For soldiers, these histories are not abstract. They can shape morale.
The concern is different. A democratic republic must ask whether inherited categories still affect opportunity, representation and internal culture. That question cannot be answered only through pride or tradition.
The government has defended the status quo before courts. In 2013, it told the Supreme Court that regimental names had historical reasons and did not amount to discrimination. That position reflects the official distinction between legacy naming and unequal treatment.
Yet the line between the two deserves evidence. If a unit carries a community label, who gets recruited into it? If recruitment is open in law, how does it work in practice? If public representation data is absent, how can the claim of non-discrimination be tested?
A modern Army may keep traditions. But tradition cannot be the only answer when the tradition began under a system that ranked Indian communities by supposed martial worth.
The President’s Bodyguard case shows why recruitment rules matter
The debate sharpened in 2018 when a petition in the Delhi High Court questioned recruitment to the President’s Bodyguard. The petition asked why applications were invited only from Jats, Rajputs and Jat Sikhs.
The President’s Bodyguard is a ceremonial unit with a long history. It has a visible role at Rashtrapati Bhavan and national events. For that reason, its recruitment policy attracts wider public attention than an ordinary unit might.
Army sources reportedly responded that the policy had been reviewed by four committees since 1947. That answer matters, but it does not end the discussion. A review can validate a policy, but it can also preserve an old norm if the review itself is not made public in enough detail.
The controversy raises three separate questions.
The first question is legal. Can a state institution restrict recruitment to specific communities if the role is publicly funded and nationally symbolic? Article 14 guarantees equality before the law. Article 15 bars discrimination on grounds such as religion, race, caste, sex or place of birth. Article 16 deals with equality of opportunity in public employment. Military service has special rules, but those rules still sit inside the constitutional framework.
The second question is operational. Does the role require a specific community composition? If the stated reason is height, riding skill, body type, ceremonial tradition or cohesion, the policy should be judged by those criteria directly. Community identity is a blunt proxy.
The third question is democratic. A unit that stands behind the President of India carries symbolic meaning. If its recruitment pool is restricted by caste-linked categories, the burden of explanation should be high.
This is why the President’s Bodyguard recruitment issue matters beyond one unit. It forces a larger question: when does military tradition become a public employment barrier?
The answer cannot rest on slogans. It needs documents, review findings, recruitment data and transparent reasoning. If committees have studied the issue, summaries of their reasoning should be available unless a specific security concern prevents disclosure.
The military often argues, with some force, that public debate should not undermine morale. But secrecy about selection principles can also harm trust. A confident institution can explain why a policy exists, what evidence supports it and how often it is reviewed.
Open recruitment claims need caste-aware data
The Defence Ministry has told Parliament that recruitment into the armed forces is open to all citizens who meet eligibility conditions. It has also said that operational needs rule out reservations for Scheduled Castes, Scheduled Tribes and Other Backward Classes in the Army.
This is the core official position: the Army recruits individuals by merit, fitness and service requirement, not by caste quota.
That claim needs careful handling. The armed forces are not the same as civilian departments. Combat efficiency, unit cohesion, deployability and command structure are real concerns. Parliament and courts have long allowed special rules for the military.
At the same time, India’s equality framework depends on measurement. If the state does not publish caste-aware data about recruitment, postings, promotions, complaints and exits, then claims of openness cannot be assessed properly.
A parliamentary committee has asked for separate data on SC and ST personnel. That request reflects a basic principle of public policy:
What is not counted cannot be measured, and what cannot be measured is difficult to reform.
This principle does not automatically require reservations in combat units. It does require the state to know, and disclose at least in aggregated form, how different groups are represented.
A useful data framework could separate several issues:
Question | Why it matters | What aggregated data could show |
Who applies? | Unequal access may begin before selection | Applications by state, district, education level and social category |
Who gets selected? | Formal openness may not produce equal outcomes | Selection rates across categories after eligibility filters |
Where are soldiers posted? | Representation may vary by arm or regiment | Distribution across infantry, services, technical branches and support roles |
Who gets promoted? | Bias can appear later in service | Promotion rates and time taken by cohort |
Who complains? | Silence may hide pressure | Anonymous complaint patterns, disposal time and outcomes |
Who leaves early? | Attrition can signal stress or exclusion | Discharge and resignation trends by cohort |
The argument for such data is not anti-Army. It is pro-governance. Police forces, universities, courts, public sector units and civil services all face demands for representation data. The Army may need different disclosure rules because of security, but a total absence of public caste-aware information is not a permanent answer.
The lack of data also weakens complaints about discrimination. Accounts of caste slights inside units remain largely anecdotal. Some former personnel have spoken about informal hierarchies, mess practices, language, jokes or exclusion. But without a safe reporting channel and published patterns, official institutions can dismiss these claims as isolated.
Anecdotes are not enough to prove a system-wide problem. They are also not enough to prove that no problem exists. That is exactly why data matters.
Courts give the military wide space, but not unlimited space
The armed forces occupy a special place in Indian constitutional law. Article 33 allows Parliament to restrict or modify the fundamental rights of members of the armed forces, police and intelligence organisations. The purpose is to ensure discipline and proper discharge of duties.
That provision is powerful. It recognises that a soldier cannot exercise rights in the same way as a civilian employee. A military unit depends on obedience, hierarchy and speed. A commander cannot run a battlefield by committee.
Indian courts have usually treated the military as a special case. They are often cautious when asked to interfere in recruitment, postings, discipline or operational decisions. This caution has a logic. Judges do not command troops. They do not plan deployments. They lack the institutional competence to second-guess every service decision.
But deference is not the same as abdication.
Article 33 does not erase the Constitution. It allows restrictions by law, for defined purposes. It does not create a zone where equality, dignity and accountability vanish. A service rule may deserve weight because it protects discipline. It should still be open to examination when it appears to classify people by caste, community or region.
The hard part is drawing the line.
Some policies may be defensible because they serve a direct military function. For example, physical standards, medical standards, training requirements and discipline rules are central to service. Other policies may be harder to defend if they rely on inherited identity categories without a clear present-day need.
This distinction is vital for caste-based units. A regimental name may be ceremonial and historical. Recruitment into that regiment may be administrative. Internal culture may be informal. Each layer needs a different kind of scrutiny.
A court may accept that the Army needs cohesion. Still, the state should explain what cohesion means in measurable terms. Does it mean shared language? Shared diet? Shared terrain experience? Shared training? Or does it mean community homogeneity inherited from colonial practice?
These are not hostile questions. They are governance questions.
Cohesion is sometimes treated as a self-evident defence of old recruitment patterns. Yet modern militaries across the world have integrated personnel across region, race, class and gender over time. Integration can create friction, but it can also widen the talent pool and strengthen national legitimacy.
India’s own Army is not one uniform model. It has “class” regiments, “mixed” regiments, all-India all-class recruitment in several arms, technical branches and services with different patterns. The existence of different models within the same Army suggests that tradition is not the only workable path.
If mixed composition works in some parts of the force, the state should be able to explain why it cannot work in others, or why any transition would harm operational readiness.
AFSPA shows the accountability gap in its sharpest form
The debate over caste and regimental identity is about internal equality. The debate over the Armed Forces Special Powers Act, or AFSPA, is about external accountability. Both raise the same institutional question: who can question military power, and through what process?
AFSPA applies in areas declared “disturbed” under the law. It gives armed forces special powers, including powers related to search, arrest and use of force in specified conditions. Section 6 is central to the accountability debate. It bars prosecution, suit or other legal proceedings against personnel acting under the Act without prior sanction from the Central Government.
The sanction requirement is meant to protect soldiers from vexatious litigation in conflict zones. That concern is not imaginary. Counter-insurgency operations are dangerous, fast-moving and politically complex. Soldiers may face ambushes, poor intelligence and split-second decisions. A legal system that treats every operational error as a crime could paralyse action.
Yet the same protection can block accountability in serious cases.
The December 2021 killings in Nagaland show the problem clearly. Thirteen civilians were killed in an Army operation and its aftermath in Mon district. An investigation later named 30 soldiers. In 2023, the Centre declined sanction for prosecution. In September 2024, the Supreme Court closed the FIRs while leaving room for revival if sanction is ever granted.
This sequence sends a stark message. Even when civilians die, even when an investigation names soldiers, the path to prosecution can end at the sanction stage.
That does not prove guilt. A trial is the place to test evidence. But refusing sanction prevents that test in a civilian court. The public sees an investigation without prosecution, allegations without adjudication and closure without a full public reckoning.
This is why AFSPA accountability remains one of India’s most contested civil-military issues.
The choice is often framed as Army morale versus human rights. That frame is too narrow. Accountability can protect soldiers as well as civilians. Clear processes help distinguish lawful action from misconduct. They reduce rumours. They give commanders better incentives. They prevent an entire institution from carrying the burden of unresolved cases.
A better system would not mean automatic prosecution in every complaint. It could include:
Time-bound sanction decisions with written reasons
Independent review in cases involving civilian deaths
Public disclosure of aggregate sanction data
Protection for operationally sensitive information during trial
Clear separation between good-faith operational action and unlawful conduct
India has lived with insurgency, border conflict and internal security threats for decades. The armed forces need legal protection in the field. But protection should not become a permanent shield against examination.
AFSPA also connects to internal military culture. If junior soldiers see that complaints, whether from civilians or from within the ranks, disappear into opaque processes, silence becomes normal. That is unhealthy for discipline. Discipline should mean lawful command and responsible obedience, not fear of reporting wrongdoing.
The missing forum for junior soldiers is a reform problem
The most difficult part of the caste debate is not the presence of old regimental names. It is the absence of trusted mechanisms to surface problems early.
A junior soldier who faces caste-based insult, exclusion or retaliation has limited realistic options. Formal complaint channels exist in the military, but hierarchy shapes how usable they feel. A soldier depends on superiors for postings, reports, leave, duties and career growth. Reporting discrimination inside a tight unit can carry social and professional risks.
The problem becomes sharper because many forms of caste discrimination are informal. They may not appear in orders or written rules. They may appear as jokes, nicknames, dining practices, social exclusion, assumptions about background, or biased assessments of “fit”.
These are hard to prove even in civilian workplaces. In a military setting, they are harder.
A dedicated forum need not weaken command. It could be designed to preserve discipline while improving trust. The key is independence, confidentiality and credible follow-up.
Possible reforms include:
An internal equality and dignity cell with trained officers and civilian oversight
Anonymous climate surveys across units, with aggregate results
Protected complaint routes outside the immediate chain of command
Annual reporting to Parliament in broad categories
Training for commanders on caste, region and religion-based harassment
Clear penalties for retaliation against complainants
Periodic review of recruitment categories by an independent commission
None of these reforms requires the Army to publish tactical information. They focus on personnel governance.
The armed forces already maintain detailed records on service, training, medical fitness, promotions and discipline. The question is whether equality-related information can be gathered in a way that protects privacy but allows public oversight.
There is also a need to separate three debates that often get mixed together.
The first is naming. Should regiments continue to carry community or regional names?
The second is recruitment composition. Who is eligible to enter different units?
The third is internal experience. Once inside, do soldiers face discrimination, exclusion or unequal treatment?
A government can defend one layer and still reform another. It can keep a historical name while widening recruitment. It can retain regimental culture while banning discriminatory practices. It can protect operational secrecy while publishing aggregate diversity data.
This is where reform becomes practical rather than symbolic.
The strongest defence of the current system deserves a serious answer
Supporters of the existing regimental system make several arguments. They should not be dismissed lightly.
They argue that regimental identity builds loyalty. A soldier fights not for an abstract chart, but for comrades, unit honour and lived belonging. They say the Army has tested these traditions in war, and the system has delivered. They warn that social engineering could damage cohesion. They also point out that the Army is not a civilian employer and cannot be governed by the same logic as other public institutions.
These arguments have weight.
India’s Army has fought wars, guarded borders, handled counter-insurgency operations and aided civilians during crises. Regimental pride can create discipline and sacrifice. Sudden, poorly planned changes could create confusion.
But the defence has limits.
First, the fact that a system has worked in battle does not prove every part of it is still justified. Many institutions carry outdated features alongside effective practices.
Second, cohesion can come from training, leadership, shared hardship and professionalism. It need not depend on caste or community similarity.
Third, public legitimacy is also a military asset. A force that reflects the Constitution strengthens public trust, especially among communities that historically faced exclusion.
Fourth, reform need not be reckless. It can be gradual, evidence-led and tested through pilots. Mixed recruitment models already exist in parts of the armed forces. Experience from those models can guide change.
The burden should not fall only on critics to prove discrimination. A public institution that uses inherited social categories should also show why they remain necessary, what safeguards exist and what data supports its position.
Honest scrutiny would strengthen the Army
The Indian Army is one of the country’s most respected institutions. That respect is precisely why difficult questions should be asked with care, not avoided.
A serious reform agenda would not begin by accusing every regiment or commander of bias. It would begin with evidence.
The government could take five steps without compromising national security:
Publish aggregated data on recruitment, selection, promotion and attrition by social category, with privacy safeguards.
Release summaries of post-1947 committee reviews on community-based recruitment, except operationally sensitive parts.
Review units with restricted recruitment pools, including ceremonial units.
Create protected complaint channels for caste, religion, region and tribe-based harassment.
Make sanction decisions under AFSPA more transparent, especially in cases involving civilian deaths.
These steps would not settle every dispute. They would move the debate from assertion to evidence.
The Army’s defenders often say civilians do not understand military life. That is partly true. Most citizens do not know what it means to serve in Siachen, patrol in an insurgency-hit area or obey orders under fire. But constitutional scrutiny does not require civilians to become soldiers. It requires the state to explain how public power is used.
Discipline and cohesion matter in war. So do equality, dignity and accountability in a republic. A system that cannot be examined may look stable from outside, but silence is not the same as strength.
India can honour its soldiers and still question inherited labels. It can respect military expertise and still ask for data. It can protect troops in dangerous areas and still demand fair processes when civilians die.
An institution this respected can afford honest questions. In fact, it should be strong enough to answer them.
