The Indian Army’s decision to induct 59 Zorawar light tanks in two different configurations should be viewed less as a triumph of flexibility and more as a warning sign that requirement inflation is once again threatening to undermine an indigenous armoured vehicle project.
The first 18 tanks are expected to enter service with a lower level of protection. The remaining 41 vehicles will reportedly incorporate enhanced protection measures, pushing the later variant closer to 30 tons.
That immediately raises an uncomfortable question.
If the Army was not satisfied with the protection level of the original design, why was the requirement not frozen before development progressed this far?
This pattern has become all too familiar across multiple Indian Army procurement programs. A platform is conceived to meet a clearly defined operational requirement. Industry develops a solution around those parameters. Trials are conducted successfully.
Then the requirements begin to expand:
More protection is demanded. More firepower is requested. Additional equipment is added. Weight limits become negotiable. Mobility requirements remain unchanged. Cost ceilings remain intact. Delivery schedules remain ambitious.
The result is often a contradictory wish list rather than a coherent operational requirement. Zorawar was never intended to be a miniature main battle tank. Its primary purpose was to provide a highly mobile armoured capability optimised for high-altitude operations, rapid deployment and difficult terrain. Demanding ever-higher protection levels risks defeating the very rationale behind the platform.
A light tank that continuously gains weight eventually ceases to be a light tank. India has seen this story before. The Arjun tank program remains the most prominent example.
Originally conceived as an indigenous main battle tank, the platform was subjected to years of evolving qualitative requirements and repeated requests for enhancements. Weight increased substantially over time as additional capabilities were incorporated, ultimately creating concerns regarding mobility, bridge-crossing limitations and transportability. Even after the platform matured, order quantities failed to match the scale originally envisaged, undermining economies of scale and increasing per-unit costs.
The Future Infantry Combat Vehicle project became another illustration of requirement paralysis.
For years, the Army struggled to finalise precisely what it wanted from the replacement for the BMP-2 fleet. Continually expanding expectations regarding protection, firepower, mobility, network-centric capabilities and amphibious performance repeatedly complicated progress, contributing to years of delay before meaningful movement could occur.
The long-running search for a mounted artillery gun system followed a similar pattern.
Successive procurement efforts often became trapped between competing expectations, changing priorities and revised technical criteria. Indigenous industry and foreign partners alike found themselves responding to shifting procurement landscapes rather than stable requirements. Even the infantry modernisation effort suffered from the same tendency.
The Army's Future Infantry Soldier as a System initiative generated ambitious expectations covering weapons, communications, sensors, protection systems and battlefield networking. Yet the sheer breadth of requirements made implementation extraordinarily difficult, resulting in years of stagnation before elements were eventually pursued separately.
The underlying problem extends beyond any single project. There is a recurring tendency within the procurement process to seek the perfect solution rather than the deployable solution.
Military equipment design is fundamentally about compromise:
Protection competes with mobility. Firepower competes with weight. Cost competes with capability. Timelines compete with ambition. No platform can maximise every parameter simultaneously. Yet indigenous manufacturers are often expected to do exactly that. Zorawar now risks entering the same cycle.
More armour means more weight. More weight requires greater engine performance. Greater engine performance may require transmission modifications. Transmission changes then trigger fresh qualification requirements. Fresh qualifications create delays. Delays place industrial supply chains at risk.
A transmission, engine or critical subsystem available during development may no longer be in production by the time mass manufacturing begins if firm orders are repeatedly deferred. When such problems emerge, criticism frequently shifts towards industry. Manufacturers are accused of failing to anticipate future needs.
In reality, no company can indefinitely preserve production capacity in the absence of assured orders and stable specifications. The greater responsibility lies with procurement authorities to define realistic requirements and maintain them.
The irony is that the Army itself identified an urgent requirement for a rapidly deployable light tank after the border crisis in Ladakh highlighted capability gaps in high-altitude armoured warfare. Industry responded with unusual speed.
The platform moved from concept to testing far faster than most major indigenous armoured vehicle programs. Yet before full-scale production has even begun, the tank is already evolving into multiple protection standards.
That suggests the requirement itself remains a moving target. For India's indigenous armoured fighting vehicle sector, the greatest obstacle is often not engineering capability but requirement creep. The country does not suffer from a shortage of engineers capable of building tanks.
It suffers from a procurement culture that too often treats successful prototypes as the starting point for a fresh set of demands. The Army has every right to demand battlefield effectiveness. What it cannot afford to do is repeatedly redefine success after development is largely complete.
Otherwise, Zorawar risks becoming another chapter in a familiar story: an indigenous platform conceived to meet an urgent operational requirement, only to be burdened by ever-expanding expectations until timelines slip, costs rise and the original problem remains unresolved.
IDN (With Agency Inputs)
