India GCC Operational & Workforce Planning
Building the centre beyond incorporation — operating model, workforce phasing, leadership, employment, governance and the discipline that makes a GCC deliver.
Incorporating an India GCC entity is the starting point, not the objective. The centre must be able to hire the right people, transfer knowledge from the global business, establish governance that supports both day-to-day operation and long-term scale, manage employment compliance, control IP and data, and integrate with the group’s operating model.
These are not secondary concerns to be addressed after the entity is registered — they are the primary determinants of whether the GCC delivers commercial value. This page addresses the operational and workforce planning dimensions of India GCC establishment. Entity structuring, location strategy, and tax and transfer pricing are covered on the dedicated pages for each topic.
Start With the Operating Model
Before any hiring begins, the operating model should be clearly defined. This means being specific about what functions the centre will perform; how those functions integrate with the global business; what outputs the centre is expected to produce, for which entities, at what quality and frequency; how performance will be measured; and who has authority to direct India-based teams on operational matters.
A GCC without a defined operating model is a team without a mandate. Hiring before this is clear produces a centre where individual roles are filled but the centre’s collective function is not. This creates governance problems — unclear reporting lines, contested accountability, poor service level definition — that compound as headcount grows.
The operating model also determines what the intercompany agreements should say, what transfer pricing model is appropriate and what governance structure the entity needs. Operational planning and structural planning should be integrated from the outset, not treated as sequential exercises. Read more on India GCC structures.
Common Execution Failures
Most GCC performance problems are traceable to planning gaps, not market conditions. The following failures consistently appear in GCCs that underperform relative to their original commercial case.
Hiring before the operating model is defined
A centre built by filling roles before the function scope, reporting lines and governance framework are clear produces headcount without mandate. Individual hires may be excellent; the collective function remains unclear. This becomes most visible when global stakeholders need consistent, governed delivery and cannot get it.
Unclear reporting lines between India and global teams
Where India-based employees report functionally to global business units and operationally to a local country head with no clear hierarchy, decisions are slow, accountability is contested and escalation paths are unclear. Reporting structure and decision authority must be designed explicitly before the first hire.
Weak local leadership authority
A GCC's India leadership must have sufficient authority to make operational decisions without escalating everything to global stakeholders. Where the India head is a coordinator rather than a decision-maker, the centre cannot scale effectively. The role, authority level and global reporting relationship should be precisely defined.
Underestimating recruitment timelines for specialist roles
Senior roles, specialist technical positions and domain-specific hires consistently take longer than planned. A centre that begins hiring only after incorporation is typically three to six months behind where it needs to be. Recruitment planning should begin before entity setup is complete.
Using standard employment templates without adapting to the function
Employment contracts, IP assignment clauses, confidentiality provisions, non-solicitation terms and exit procedures must reflect the specific functions, data exposure and governance model of the centre. Standard templates create gaps that become visible when an employee exits, a vendor relationship changes or IP is disputed.
Scaling headcount without corresponding management depth
A centre that adds 50 people per quarter without adding management layers, process documentation and governance infrastructure creates an organisation growing faster than it can be governed. Headcount growth should be matched by management layer development, not treated as an independent variable.
Measuring success by headcount rather than operational maturity
Headcount is an input metric, not an outcome. A centre should be measured against service delivery quality, governance maturity, stakeholder satisfaction, process documentation, knowledge transfer completion and compliance discipline — not only against hiring targets.
Workforce Planning: Phase It, Don't Improvise It
A GCC typically passes through three operational phases, each with distinct workforce requirements. Planning across all three from the outset is significantly more effective than building sequentially.
Launch Phase
The priority is not headcount — it is quality and range. Core leadership, initial functional leads, HR and finance support, first delivery teams. The people hired at this stage must be capable of building processes, recruiting teams, absorbing group culture and managing global stakeholders — not simply executing defined tasks. Hiring speed is less important than hiring quality.
Stabilisation Phase
Process standardisation, service-level documentation, middle management development, knowledge transfer completion and performance measurement. This phase often reveals gaps in the launch model invisible at smaller scale — unclear process ownership, missing documentation, under-specified escalation paths.
Scale Phase
Broader hiring, deeper leadership layers, stronger internal controls, succession planning, automation and multi-site or hybrid work considerations. The operational discipline built earlier either holds or cracks here. A centre that has not built governance and process infrastructure faces significant disruption when scale demands reveal its absence.
Leadership Structure and Decision Authority
Leadership structure is one of the most consequential early decisions in a GCC build. A support centre may need functional leads and a local operations head. A larger GCC typically requires a country head or GCC head, functional heads, HR and finance capability, compliance oversight and a steering committee that connects India leadership to group stakeholders.
The India leadership team must have genuine authority to make operational decisions within agreed parameters, without escalating routine issues to global stakeholders. Where the India head is a coordinator or liaison rather than a decision-maker, the centre cannot operate efficiently at scale.
The question of whether to appoint an expat, a local hire or a returning diaspora professional to the GCC head role is consequential and depends on the function, the pace of the build and the maturity of the group’s India engagement. Expats provide integration and group culture but may create dependency and succession risk. Local hires move faster on ground but may carry less parent-company authority. Returning diaspora often combine both, but the pool is finite and competitive.
Employment Model and HR Compliance
India’s employment framework is substantive. Employment contracts, compensation structures, PF and ESI obligations, gratuity, payroll tax, bonus entitlements, POSH compliance, non-compete enforceability and exit procedures should all be reviewed before hiring begins.
Key employment documentation includes employment contracts with IP assignment and confidentiality provisions adapted to the GCC’s function; workplace policies; POSH / prevention of sexual harassment compliance documentation; payroll and benefits structure; contractor agreements where applicable; secondment documents for group employees working in India; and exit procedures with data and IP handover requirements.
Contractor and secondment arrangements carry their own compliance implications. EOR (employer of record) models may be appropriate in early stages but should not be treated as permanent structures for a centre expected to grow. The employment model should be reviewed and formalised before the centre reaches a scale at which compliance gaps become material.
Knowledge Transfer and Process Migration
Knowledge transfer is one of the most underplanned elements of GCC setup. It is the structured movement of process knowledge, documentation, training, accountability and service responsibility from existing teams to the India GCC. It is not simply training — it requires process mapping, documentation, shadowing, reverse shadowing, service levels, escalation rules and clear handover milestones.
A knowledge transfer plan should be agreed with the global business before the India team is fully staffed, not treated as an organic process that happens through proximity. It should specify what processes are being transferred, in what sequence, over what timeline, with what acceptance criteria, and who retains accountability during the transition period.
Poorly managed knowledge transfer is one of the most common sources of service quality problems in GCCs, particularly in the first twelve to eighteen months. Global teams that have not actively contributed to the transfer frequently find that the India team delivers against a specification that does not reflect how the process actually works in practice.
Governance and Performance Management
Governance in this context covers board oversight and decision rights, escalation protocols, performance metrics and reporting cadence, and how the India team stays connected to the parent group’s strategy and priorities as an operational matter rather than merely a cultural one.
Performance management for a GCC should be based on service delivery outcomes, process documentation maturity, stakeholder satisfaction, governance compliance and knowledge retention — not solely on headcount or cost metrics. A centre measured only on cost tends to manage to cost at the expense of quality and resilience.
Governance should be designed for the centre the group intends to build, not the one being launched. A governance structure adequate at launch but requiring overhaul at the hundred-person mark will be overhauled at the most operationally inconvenient time.
Technology, Data and Security Controls
Technology and data controls should be established before the India team has access to group systems, data or IP. The required controls depend on the function, but may include identity and access management, device controls, data classification policies, cybersecurity standards, software licensing compliance, vendor access rules, incident response protocols, business continuity planning, and access revocation procedures on employee exit.
For GCCs handling regulated data, customer personal data, financial data or proprietary IP, the control framework should be reviewed against the applicable data protection requirements in India and in the jurisdictions where the data originates. Controls retrofitted after a breach or regulatory inquiry are significantly more disruptive than controls established before operations begin.
Office and Operating Infrastructure
Office selection is both a real estate decision and an operational one. Grade-A office space with appropriate access controls, expansion capacity, backup power, network infrastructure and security provisions is relevant for GCCs handling sensitive IP, regulated functions or large-scale operations. Managed office or flexible workspace may be appropriate at early stages or for pilot teams.
The office environment affects hiring and retention as much as it affects operations. In India’s competitive GCC talent market, the quality of the work environment is a material factor in attracting senior leadership and retaining high-performing teams. Infrastructure decisions should not be made primarily on cost.
Vendor and Support Ecosystem
Most GCCs rely on external providers across recruitment, payroll, managed office operations, IT support, legal and tax advice, background verification, security and facilities management. This is practical and appropriate. Vendor dependence becomes a problem only when contracts are loose and operational accountability is unclear.
Vendor arrangements should define scope, service levels, data and confidentiality obligations, pricing, termination rights, audit access and responsibility for compliance failures. Critical functions, data relationships and employee accountability should not sit primarily with vendors. The GCC should be able to replace a vendor without losing operational continuity.
Scaling from Pilot to Mature Centre
The transition from pilot team to mature GCC is the most operationally demanding phase. A small team can survive on informal leadership and direct access to global stakeholders. At scale, neither is sufficient.
As headcount grows, the business should review leadership layers, middle management depth, role clarity, service catalogues, process documentation, HR policies, compensation benchmarking, retention strategy, compliance calendars and succession planning.
The guiding principle is that governance should scale with headcount, not lag behind it. The three-to-five-year operating trajectory should be designed into the early structure — not as a constraint, but as a direction. Early decisions that block future scale are consistently harder to reverse than they appear at the time.
International and Group Alignment
Where a GCC sits within a wider international group — headquartered or structured through Singapore, the UAE, the UK, Europe or the US — the India centre must be aligned with group operating architecture, not treated as a standalone entity. Relevant considerations include time-zone coordination, regional oversight, intercompany service flows, transfer pricing documentation, data access and confidentiality requirements, global employment policies, and decision-making authority.
Where a single India team supports multiple group entities, the service scope, charging model, reporting lines and accountability for each relationship should be clearly documented. The India centre’s value is as a governed component of a wider commercial structure. It should function as such from the outset. Read more on India–UAE GCC structures.
Operational Planning, Built In
We advise businesses, investors, family offices and promoter groups on the operational and workforce dimensions of India GCC establishment — from initial model design through to implementation and scale-up.
Clients typically engage us in one of four situations. They are establishing a GCC and need the operating model, workforce phasing, leadership structure, employment framework and governance design integrated into the entity and location plan before hiring begins. They have a GCC that has grown significantly and the original operating model, governance or employment structure is no longer adequate for the size and complexity of the current operation. They are UAE or international groups that need the operational planning aligned with the UAE parent structure, intercompany service flows, transfer pricing and group governance. Or they have encountered an operational problem — governance gaps, knowledge transfer failure, leadership authority conflicts, vendor dependency — and need an independent assessment of what needs to change.
An ATB engagement on India GCC operational and workforce planning is focused on reviewing the GCC operating model against the commercial function and group requirements; designing workforce phasing across launch, stabilisation and scale; advising on leadership structure and decision authority; reviewing employment model and documentation; planning knowledge transfer; designing governance and performance management frameworks; and aligning operational planning with entity structure, location strategy and intercompany arrangements.
We align this work with entity structure, location strategy, intercompany agreements and transfer pricing — so that operational planning and structural planning are integrated rather than sequential. Where specialist input is required on employment law, tax, data protection or regulatory compliance, we coordinate with appropriate advisers.
GCC Operations & Workforce — Answered
The operating model, function scope, leadership structure, reporting lines, employment model, knowledge transfer plan, technology access framework, data controls and scale plan should all be defined before substantive hiring begins. Hiring without this framework creates governance and execution risk that compounds as the centre grows.
It depends on the centre’s function and scale. A support centre may need functional leads and a local operations head. A larger GCC typically requires a country head or GCC head, functional heads, HR and finance capability, compliance oversight and a steering committee connecting India leadership to group stakeholders. The India leadership must have genuine authority to make operational decisions within agreed parameters, not merely coordinate between global teams.
Direct hiring through an Indian entity gives the strongest control and long-term alignment over employment, IP, data and institutional knowledge. Vendor-supported, EOR or BOT models can accelerate launch but require contractual structures that protect the group’s rights over employment, data, IP and transition. The choice depends on phase, function, timeline and risk appetite. EOR models should not be treated as permanent structures for a centre expected to grow.
Launch needs leadership and core delivery teams — quality over speed. Stabilisation needs process maturity and middle management development. Scale needs deeper leadership, retention planning, compliance infrastructure and governance depth. The plan should be designed with all three phases in view from the outset. Early decisions that constrain future scale are significantly harder to reverse than they appear at launch.
Knowledge transfer is the structured movement of process knowledge, documentation, training, accountability and service responsibility from existing teams to the India GCC. It requires process mapping, documentation, shadowing, reverse shadowing, service levels, escalation rules and clear handover milestones. It is not training — it is a formal, planned migration of operational responsibility that should be agreed with global stakeholders before the India team is fully staffed.
At minimum: employment contracts with IP assignment and confidentiality provisions adapted to the GCC’s function, workplace policies, POSH compliance documentation, payroll and benefits structure, contractor agreements where applicable, secondment documents and exit procedures with data and IP handover requirements. Documents should reflect the specific function, data exposure and governance model of the centre — not generic templates.
Required controls depend on the function but may include identity and access management, device controls, data classification, cybersecurity standards, software licensing compliance, vendor access rules, incident response, business continuity planning and access revocation on employee exit. Controls should be established before the India team has access to group systems and data, not retrofitted after a breach or regulatory inquiry.
Through contracts that clearly define scope, data access, confidentiality obligations, transition rights and compliance responsibility — and by retaining internal ownership of critical knowledge, governance and employee relationships. The test is whether the GCC can continue operating effectively if a vendor relationship ends. Where that answer is no, the vendor arrangement needs contractual or structural review.
The operating model should be reviewed before launch, after the first hiring phase, before any major scale-up, when new functions are added, when the centre starts serving additional group entities, and when data, IP or regulatory exposure increases. The operating model at launch is not necessarily appropriate at scale. A scheduled review discipline should be built into the governance framework from the first year.
Plan the centre, not just the entity.
The operating model, workforce phasing, leadership authority and governance should be designed before the first hire — so the centre delivers from launch and holds together at scale. Talk to our team when you are ready.
Get in touch