Wipro’s decision to let employees in Band 2 and below remain on the bench for up to 180 days is more than an internal human-resources change. It is a measure of how Bengaluru’s technology economy is absorbing a period in which companies are limiting fresh hiring, tightening deployment rules and trying to extract more capacity from their existing workforce.
The revised Wipro bench policy, effective October 1, allows junior- and mid-level employees to remain unbilled for six months after being released from a billable project or returning to India from an onsite assignment without being allocated to another billable project. Employees in Band 3 and above continue to face a 45-calendar-day bench period under the company’s Extended Bench Leave Programme, while employees with disabilities receive a 75-day period.
The policy therefore creates different levels of employment protection within the same company. For Band 2 and below, the longer period provides more time for redeployment, training or reassignment. It does not guarantee continued employment. The policy document reviewed by the Times of India states that employees who do not secure an allocation within 180 days may be separated from the company in accordance with their employment contracts.
That distinction is important for understanding the changing relationship between the technology sector and Bengaluru’s labour market. A bench is not necessarily a period without work in the broader sense. It is a period in which an employee is not assigned to a billable project. The employee may still be paid and may be asked to undergo training, participate in internal assessments or seek another project within the organisation. The business challenge for the company is that the employee remains a cost without directly contributing to project revenue.
The revised policy gives Wipro more time to resolve that mismatch for a substantial part of its workforce. Industry experts cited by the Times of India said the extended period could help the company redeploy unbilled employees, particularly because Wipro has not hired freshers in the past few quarters. Employees on the bench could be upskilled and deployed on available projects, reducing the need to hire and train new talent.
This approach reflects a shift in how large technology companies are managing demand uncertainty. Instead of maintaining a broad pipeline of new recruits while waiting for projects, companies are placing greater emphasis on internal allocation, billability and skill matching. The pressure is not limited to whether an employee has a job. It also concerns how quickly the employee can be made useful to a project, whether existing skills match current demand and who bears the cost when the match does not happen.
Wipro president and chief human resources officer Saurabh Govil said during an earnings call that the company did not hire freshers during the June quarter. He added that Wipro would reassess hiring depending on the demand environment but was not providing hiring guidance. The company had onboarded about 7,500 graduates the previous year, taking its headcount to 2.4 lakh employees.
Those figures place the bench policy within a larger workforce cycle. When a large technology company recruits thousands of graduates, it assumes that future client demand will create enough projects to absorb them. When hiring slows, the existing employee base becomes the main pool from which the company must fill new requirements. The longer bench period can therefore function as a buffer between the end of one assignment and the beginning of another, while also reducing the immediate need for external recruitment.
At the same time, the policy makes the consequences of non-deployment explicit. The 180-day period is relief compared with the shorter norms being adopted elsewhere, but it is also a defined deadline. Employees have six months to secure an allocation before separation may follow. The result is a model in which the company provides additional time, but the responsibility for remaining deployable is increasingly formalised.
Wipro’s revised policy incorporates the capability development plan into compliance requirements and consequence management. A capability development plan may be initiated when persistent competency gaps are identified through structured interview evaluations, including failure to clear role-specific assessments conducted by Wipro or its clients. However, a single interview rejection is not enough. The policy allows the plan to be initiated after three successive interview rejections, provided the roles require comparable competencies and the gaps are consistent, evidence-based and formally documented.
This provision creates a formal link between project allocation and performance management. Employees on the bench are not assessed only on whether a vacancy exists. They may also be assessed on whether their skills correspond to the roles being offered and whether repeated failures indicate a capability gap. That process can help a company distinguish between a lack of available projects and a lack of readiness for available projects, although the supplied policy details do not establish how many employees may be affected under either category.
The contrast with other major technology companies shows why Wipro’s decision is significant. The Times of India reported that several large IT companies have tightened bench-time norms to roughly 45 to 60 days. TCS’s updated associate deployment policy requires employees to be billed for 225 days annually, effectively limiting bench time to a maximum of 35 business days in a year. Cognizant had reduced its bench period from 60 days to 35 days, according to the report.
These comparisons do not show that every company uses identical definitions or employment processes. Calendar days, business days, annual billability requirements and extended leave programmes are not directly interchangeable. They do, however, indicate the direction of travel: the period during which an employee can remain outside a billable assignment is being treated as a closely managed operational metric.
For Bengaluru, this is also an urban economy story. The city’s technology workforce supports a wide network of housing demand, transport use, commercial districts, professional services and household consumption. A change in employment certainty can affect how workers make decisions about rent, commuting, relocation, education and family finances. The available material does not quantify those effects, but the scale of Wipro’s workforce means that internal deployment rules have consequences beyond the company’s offices.
The policy also exposes a structural tension in the technology employment model. Companies need specialised skills that may not be immediately available when a project begins, but they also face pressure to limit the cost of employees who are not attached to revenue-generating work. Workers, meanwhile, may be employed by a large company while experiencing uncertainty about where and when their next assignment will come. The bench becomes the institutional space where those two pressures meet.
Wipro’s exclusion of the Extended Bench Leave Programme for Band 2 and below is another indication that the six-month period should not be read as an unconditional extension of employment. It is a redeployment window governed by allocation requirements, capability assessments and employment contracts. For Band 3 and above, the standard 45-day period remains in place, while employees with disabilities receive a separate 75-day period.
The evidence currently establishes a policy change, the company’s stated hiring position and a set of comparison points from other IT firms. It does not establish how many Wipro employees are currently on the bench, how many are expected to benefit from the new rule, how many could enter capability development plans or whether the policy will result in fewer separations. Wipro declined to comment on the Times of India’s questions, so those operational outcomes remain unreported in the supplied material.
What the policy confirms is that workforce utilisation has become a central management issue as technology companies reassess hiring and project demand. Wipro is giving a section of its workforce more time to find billable work, while retaining a defined separation route for employees who remain unallocated. The next significant indicators will be the company’s hiring decisions, the scale of internal redeployment and how the revised capability and allocation rules operate in practice.
