India’s IT sector runs on client timelines, production releases, incident response, global time zones, and high-stakes delivery commitments. In that environment, late-night work can become routine before leadership notices the pattern.
That creates more than an employee experience problem. It can create payroll leakage, overtime claims, fatigue-related attrition, delivery risk, and state-specific labor-law exposure.
For CEOs, HR leaders, and account heads, overtime calculation in India should not be treated as a simple payroll task. It is a workforce governance and capacity management issue.
The Indian technology sector was expected to employ about 5.8 million people in FY2025, according to NASSCOM, making consistent workforce controls increasingly important across large delivery organizations and GCCs.
This guide explains what overtime pay is, how overtime calculation works for IT companies, what leaders need to verify across states, and how to build a scalable approval-to-payroll process.
[Disclaimer: This guide is for general information only, not legal advice. Overtime rules may vary by state, role, and workplace. Please seek legal advice before finalizing your company policy.]
Key Takeaways for IT Leaders
- Overtime pay is additional compensation for eligible employees who work beyond applicable daily or weekly working-hour limits.
- There is no single overtime rule for every IT company in India. Requirements can vary by state, establishment type, employee role, and exemption notifications.
- IT and IT-enabled services companies are commonly covered by the relevant state Shops and Establishments law, not automatically by the Factories Act.
- Under applicable central wage provisions, overtime pay cannot be less than twice the normal wage rate in covered cases.
- Job titles such as “team lead” or “manager” do not automatically determine overtime eligibility. Employers should assess actual duties, authority, location, and applicable law.
- Late-night client calls, weekend deployments, production incidents, active on-call work, and release support can create overtime exposure when they involve verified work beyond normal hours.
- Accurate overtime calculation requires the right wage base, reliable time records, documented approvals, and location-specific payroll configurations.
- Recurring overtime is often a business warning sign. It can indicate understaffing, scope creep, weak capacity planning, or unsustainable client delivery expectations.
What is Overtime Pay?
Overtime pay is additional compensation paid to an eligible employee for working beyond the prescribed daily or weekly working hours.
For an IT employee, overtime may arise from work such as:
- A weekend production deployment
- A late-night incident bridge with a U.S. or European client
- A critical cybersecurity response
- Extended hypercare after a platform launch
- Month-end processing or cloud migration work
- A client escalation that extends beyond the scheduled shift
- On-call support that becomes active, measurable work
Overtime is not the same as a performance bonus, a project-completion incentive, shift allowance, retention bonus, or variable pay. It is tied to actual additional working time, subject to the employee’s eligibility and the law that applies.
Why Overtime Requires Leadership Attention
For IT organizations, overtime is often hidden behind the language of commitment, flexibility, client urgency, or ownership. That can be dangerous when it becomes a repeated operating model.
Account heads may see overtime as a temporary way to protect a delivery milestone. HR may see a spike in attendance exceptions. Finance may see unplanned payroll costs. Employees may experience it as a recurring expectation without clear compensation or recovery time.
A connected leadership view is essential because recurring overtime can affect:
- Client delivery quality
- Project profitability
- Employee burnout and retention
- Payroll accuracy
- Labor-law compliance
- Manager accountability
- Resource utilization reporting
- Billable versus non-billable effort tracking
- Employer brand and employee trust
For a services business, every recurring overtime pattern should lead to a management question: Is this genuinely exceptional work, or is the account under-resourced or affected by weak workload planning?
Which Overtime Law Applies to IT Companies?
Most IT and IT-enabled services companies operate through offices, development centers, delivery hubs, shared service centers, and remote-work arrangements. These establishments are commonly subject to the Shops and Establishments law of the relevant state or Union Territory.
This is different from a factory environment. The Factories Act, 1948, sets a clear overtime standard for factory workers, including double wages for work beyond 9 hours a day or 48 hours a week. However, IT employers should not automatically apply the Factories Act formula to their workforce without confirming the law that governs their establishment.
State Shops and Establishments Laws
State Shops and Establishments laws often regulate:
- Daily working-hour limits
- Weekly working-hour limits
- Rest intervals
- Spread-over limits
- Weekly off requirements
- Overtime eligibility and pay
- Permitted overtime hours
- Records, registers, notices, and inspection requirements
- Special rules for women working night shifts
- Exemptions for managerial, supervisory, or confidential roles
The rules can differ from one state to another. A policy designed for an IT delivery center in Karnataka may not be sufficient for a team in Maharashtra, Telangana, Tamil Nadu, Delhi, Uttar Pradesh, or a remote employee working from another state.
Central Wage Framework
Section 14 of the Code on Wages, 2019 states that, in the covered circumstances, overtime wages cannot be paid at less than twice the normal wage rate. [indiacode.nic]
The Occupational Safety, Health and Working Conditions Code, 2020 also provides for overtime wages at twice the rate of wages where a worker exceeds hours prescribed by the appropriate government. It further states that overtime should be calculated on a daily or weekly basis, whichever is more favorable to the worker. [dgfasli.gov]
The practical takeaway for IT leadership is not to assume a single legal rule applies everywhere. Monitor the enforceability of relevant Codes, state rules, notifications, and location-specific exemptions before changing payroll or attendance policy.
What Are Overtime Hours for IT Employees?
Overtime hours are the verified work hours performed beyond the normal daily or weekly limit that applies to an eligible employee.
In IT organizations, these hours may not always appear as a traditional extension of a shift. They can arise through:
- Logged work after official working hours
- Weekend or public-holiday work
- Approved extended support coverage
- Active work during on-call periods
- Project-related work during scheduled leave or weekly off days
- Mandatory late-evening client calls
- Incident management, disaster recovery, or business continuity activities
- Work performed remotely outside normal scheduled hours
The key word is verified. An employee’s availability, passive monitoring, or voluntary unscheduled activity may need to be assessed differently from assigned, approved, or employer-permitted work. The distinction should be addressed in the company policy, but a policy cannot override statutory wage obligations.
Who is Eligible for Overtime Pay?
Eligibility depends on the employee’s role, actual responsibilities, work location, applicable state law, establishment category, wage structure, and available exemptions.
In an IT company, potentially eligible employees may include:
- Software engineers and developers
- QA engineers and test analysts
- Service desk and technical support professionals
- Cloud operations and DevOps teams
- Network operations center personnel
- Security operations center analysts
- BPO and customer-support employees
- Project coordinators
- Data-processing and operations teams
- Contract workers deployed at client sites or delivery centers
Do not decide eligibility based only on titles. Calling someone a “team lead,” “project manager,” “consultant,” or “associate manager” does not automatically exclude them from overtime rights.
Before classifying an employee as exempt or ineligible, assess:
- Whether the person truly performs managerial or supervisory work
- Their authority to hire, fire, discipline, or make material business decisions
- The percentage of time spent on people management versus individual delivery
- Their wage level and employment terms
- The law that applies in the state where they work
- Any relevant state notification or exemption
For large IT employers, this analysis should be documented by role family, level, location, and legal entity, not decided informally by individual managers.
What is Overtime Rate in India?
Overtime rate is the rate used to compensate eligible employees for verified overtime hours.
The overtime rate for an IT employee depends on the relevant state law, applicable notification, and company policy. In many legal frameworks, overtime is calculated at twice the normal rate of wages. Indian Code on Wages establishes that overtime in covered cases must not be paid at less than twice the normal wage rate.
However, the wage base must be checked carefully. Employers should not automatically calculate overtime on CTC, gross pay, or basic salary alone.
CTC can include employer PF contributions, insurance, gratuity provisions, bonuses, reimbursements, retention payments, stock benefits, and other components that may not form part of the statutory overtime wage base.
For IT organizations, the correct question is:
Which wage components must be included under the applicable law and state-specific rules for this employee group?
Build this answer into payroll configuration instead of allowing managers or payroll executives to make manual assumptions each month.
Overtime Calculation Formula in India
The core overtime calculation formula in India is:
Overtime pay = Regular hourly wage × Applicable OT multiplier × Verified overtime hours
The calculation looks simple. The compliance work lies in correctly defining each element.
Step 1: Identify the Applicable Wage Base
Start with the wage components required by the applicable law. Do not start with CTC.
For factory workers, the Factories Act uses the “ordinary rate of wages,” which includes basic wages and applicable allowances but excludes bonus and prior overtime wages. IT employers should identify the corresponding legally relevant wage definition under the state law or notification applicable to their establishment.
Step 2: Convert Eligible Wages Into an Hourly Rate
A commonly used operational formula is:
The denominator should reflect the method required by the applicable law or the employer’s compliant payroll structure. It should not be selected merely because it lowers the hourly rate.
Step 3: Apply the Correct Overtime Multiplier
Where the applicable law requires double wages, use:
Overtime rate = 2 × Regular hourly wage
Step 4: Multiply by Verified Overtime Hours
Overtime pay = Overtime rate × Verified OT hours
Example: IT Support Engineer
Assume:
- Eligible monthly wages: ₹52,000
- Working days used for the monthly calculation: 26
- Normal working hours per day: 8
- Approved overtime hours during a production migration: 10
- Applicable overtime multiplier: 2 times
First, calculate the hourly rate:
Then calculate overtime pay: ₹250 × 2 × 10 = ₹5,000
The overtime pay would be ₹5,000, subject to confirmation of the applicable law, eligible wage components, work-hour threshold, and documented overtime record.
Methods for Overtime Calculation
IT organizations usually need different payroll methods for different employee groups.
| Employee group | Typical payroll basis | Practical overtime approach |
| Monthly salaried IT employee | Monthly salary | Convert legally eligible wage components to an hourly rate, then apply the applicable OT multiplier |
| Hourly or shift-based support employee | Hourly rate | Multiply the regular hourly rate by the applicable OT multiplier and verified OT hours |
| Daily-rated operations worker | Daily wage | Divide the eligible daily wage by regular daily hours, then apply the OT multiplier |
| Contract staff | Contractor wage records | Validate time, rate, eligibility, payment, and statutory records with the contractor |
| On-call support employee | Salary plus on-call allowance | Separate on-call availability from active work, then calculate eligible active work under the applicable policy and law |
A single spreadsheet formula may be convenient, but it is not a compliance strategy. The system should apply the right rule by employee location, entity, department, job category, shift schedule, and legal classification.
How Many Hours of Overtime is Allowed?
There is no single answer for all IT companies in India.
The limit can depend on the state Shops and Establishments law, applicable rules, exemption notification, establishment type, and employee category.
As per a government press release, the Shops and Establishments bill published by the Ministry of Labor and Employment uses a 9-hour daily and 48-hour weekly threshold. However, this model is not a substitute for the legislation and notifications applicable in a specific state.
For example, an Uttar Pradesh notification for IT and ITES establishments referenced conditions that include a maximum 12-hour workday including rest intervals, overtime pay at twice the ordinary rate for work beyond 48 weekly hours, and a cap of 125 overtime hours per quarter.
Do not copy those limits across India. Treat them as an example of why location-specific compliance is essential.
For CEOs and delivery heads, the operational principle is clear: overtime should be exception-driven, approved, measurable, and limited. It should not be the default way to achieve a project margin or client SLA.
Client Deadlines and Overtime: What Account Heads Should Do
Account heads influence overtime risk more than most organizations realize. A client escalation may be commercially necessary, but it must not lead to undocumented work or an informal expectation that delivery teams will absorb extra hours.
Before approving an extended-hours delivery plan, account leaders should ask:
- Is this a one-time incident or a recurring staffing gap?
- Which employees are eligible to work the proposed schedule?
- Does the schedule comply with local working-hour and rest-period requirements?
- Is overtime approval documented before work begins?
- Is the cost included in the project margin forecast?
- Is the extra effort billable to the client?
- Can work be shifted to another time zone, delivery center, or team?
- Is there a recovery plan for affected employees after the critical period?
- Has the client been informed of the impact of scope changes or accelerated timelines?
A project plan that depends on regular unpaid late-night work is not a high-performing delivery model. It is an unrecorded cost and a preventable workforce risk that better resource planning can help address.
Common Overtime Pay Calculation Mistakes
Common overtime calculation mistakes include using the wrong wage base, misclassifying employees, missing extra work hours, and overlooking state-specific laws.
1. Using CTC as the Overtime Wage Base
CTC is an employment-cost figure, not automatically the correct basis for overtime. Separate eligible wages from employer contributions, reimbursements, bonuses, equity, and non-wage benefits.
2. Treating All IT Employees as Exempt
A job title is not enough. Review actual duties, decision-making authority, location-specific law, and exemption rules before excluding employees from overtime.
3. Ignoring Remote and Hybrid Work
Remote work does not eliminate overtime risk. Teams working from home may log late-night client calls, deployment work, or incident resolution that needs to be assessed and tracked.
4. Paying Only for Pre-Approved Overtime
Pre-approval is a valid control. But if employees perform eligible overtime that the company knew about, required, or permitted, simply denying payment because an approval workflow was missed can create risk. Investigate and correct the record.
5. Treating On-Call Time and Active Work as the Same
An on-call allowance and overtime pay are not automatically interchangeable. Define active incident work, standby availability, call-outs, response time, and time-recording rules clearly.
6. Checking Only Weekly Hours
Some laws use daily and weekly thresholds. A payroll team that reviews only weekly hours can miss daily overtime exposure.
7. Ignoring State-by-State Differences
A national IT company may have employees across several jurisdictions. Apply localized rules, rather than relying on one policy written for the headquarters location.
8. Using Overtime to Mask Understaffing
If a support team has overtime every month, the issue may be headcount, shift design, automation, scope creep, or poor workload allocation. Fix the operating model, not only the payroll output.
9. Poor Audit Trail
When attendance, shift roster, client requirement, manager approval, project code, and payroll entry sit in different systems, disputes become harder to resolve.
Build an Overtime Governance Model for IT
A mature overtime framework is not just an HR policy. It is a shared operating model across HR, delivery, finance, legal, payroll, and account management.
1. Create a State-Wise Compliance Matrix
Maintain a current matrix for each registered office, delivery center, client site, and remote-work location.
Include:
- Applicable Shops and Establishments law
- Normal daily and weekly hours
- Rest-break requirements
- Weekly off rules
- Overtime threshold and rate
- Overtime cap
- Exempt employee categories
- Night-shift requirements
- Mandatory registers and record-retention requirements
- Current exemptions and their validity dates
2. Classify Roles Carefully
Create a documented role-based eligibility framework. Review developers, support staff, analysts, project managers, team leaders, operations employees, and people managers separately.
Avoid broad rules such as “all band-6 employees are exempt.” Legal exposure depends on more than an internal grade.
3. Connect Work, Time, and Cost
Overtime must connect to a real business reason. Tag each request to:
- Client account
- Project or cost center
- Incident or change ticket
- Delivery milestone
- Manager approval
- Employee attendance record
- Client-billable or non-billable classification
This gives finance a more accurate view of account profitability and helps account heads identify chronic delivery pressure.
4. Set Clear Approval Levels
Use a tiered approach:
- Team manager approval for planned, low-risk overtime
- Delivery leader approval for extended project overtime
- HR and compliance review for recurring overtime patterns
- Executive review for high-cost, large-scale, or repeated client-driven overtime
5. Review Overtime as a Business Metric
Track overtime by client, account, project, city, job role, team, manager, and month.
Useful leadership metrics include:
- Overtime hours per full-time employee
- Overtime cost as a percentage of project revenue
- Repeated overtime by account
- Unapproved overtime incidents
- Employees exceeding defined internal alert thresholds
- Weekend and public-holiday work
- Overtime by attrition-risk group
- Recovery time after major releases or incidents
How CollabCRM Supports IT Overtime Workflows
For IT organizations, overtime data is often fragmented. The client escalation is in email. The deployment plan is in a project tool. The approval is in chat. The attendance record is in another system. Payroll receives a spreadsheet at month-end.
CollabCRM is an all-in-one business operating system that helps bring the workflow together.
CollabCRM supports structured workflow management between account teams, delivery managers, HR, and finance by creating a visible record of why extra work is needed, who approved it, which client or project it relates to, and what follow-up is required.
A practical workflow can look like this:
- An account head logs a client escalation, release requirement, or support extension
- The delivery manager identifies the affected team and expected hours
- The appropriate manager approves the overtime request
- HR or operations validates the applicable internal policy and location-specific requirements
- Approved work is linked to the project, account, cost center, and attendance record
- Payroll receives a verified input rather than an unstructured end-of-month spreadsheet
- Leadership dashboards identify repeat overtime patterns across accounts
CollabCRM does not replace legal review, attendance system, or payroll software. It helps organizations make overtime-related work visible and accountable before it becomes a payroll exception or employee grievance.
Final Takeaway
For Indian IT companies, overtime calculation is a business decision with legal, financial, operational, and people consequences.
The formula is straightforward. The hard part is applying the right law to the right employee, in the right state, using the right wage base and a defensible record of actual work. IT companies must pay particular attention to distributed teams, hybrid work, client-driven late hours, weekend deployments, on-call support, and role-classification assumptions.
The strongest organizations do not wait for a payroll dispute to examine overtime. They build a location-aware policy, track work in real time, require accountable approvals, audit recurring patterns, and use workforce data to solve the underlying capacity issue.
Frequently Asked Questions
Overtime pay is additional compensation for eligible IT employees who work beyond the normal daily or weekly hours prescribed by the applicable law or policy. It may apply to extended client support, deployments, incident response, or other approved extra work.
Some IT employees may be eligible, but eligibility depends on the applicable state law, their actual duties, employee classification, work location, wage structure, and available exemptions. Employers should not decide based solely on job titles.
IT companies are commonly regulated by the Shops and Establishments law of the state or Union Territory where the establishment is located. The relevant law can differ by location, so national companies need a state-wise compliance approach.
A common formula is:
Overtime pay = Regular hourly wage × Applicable OT multiplier × Verified overtime hours
The wage components, regular hours, and multiplier must be determined under the applicable law.
In relevant statutory frameworks, overtime is generally paid at not less than twice the normal rate of wages. The Code on Wages, 2019 provides for a minimum overtime rate of twice the normal wage rate in the covered circumstances.
First identify the legally eligible monthly wage components. Divide those wages by normal monthly working hours to calculate the regular hourly rate. Then multiply that rate by the applicable overtime multiplier and verified overtime hours.
It can. Remote work does not automatically remove overtime obligations. Companies should track required, authorized, or permitted late-night work, including deployments, client calls, incident resolution, and project work outside scheduled hours.
Do not assume comp-off can replace statutory overtime wages. Whether this is allowed depends on the applicable law, employee category, and circumstances. Seek legal advice before designing a comp-off policy for eligible overtime work.
The permitted hours vary by state law, notification, exemption, and establishment type. Employers should verify daily limits, weekly limits, rest periods, spread-over rules, and overtime caps for each employee location.
Not necessarily in every case. Organizations should distinguish between passive standby availability and active work performed during an on-call period. The applicable law, company policy, and facts of the arrangement determine the appropriate treatment.
Priority Onboarding