What HQ looks for before handing a GCC a bigger mandate

Most GCC leaders know the moment. A global sponsor leans back on a call and asks, “Could your team own this?” The answer that follows rarely depends on the pitch you make that day. It depends on what HQ has already seen from your centre over the previous year.

Bigger mandates are not handed out for good presentations. They follow evidence. Sponsors move ownership to a centre when the risk of doing so feels lower than the cost of not doing it. Your job, long before that conversation, is to make the evidence obvious.

Why mandates are moving now

India now hosts more than 2,100 GCCs. Many of them were set up to execute: run a process, maintain a platform, deliver to a specification written somewhere else. That model is changing. Global organisations are asking their centres to own products, platforms and decisions, and increasingly to lead on AI rather than wait for instructions.

With so many centres competing for attention inside the same global organisations, the question for a site leader is no longer whether bigger mandates exist. It is whether your centre looks like the safest place to put them.

Talk to global sponsors and the same themes come up again and again. We group them into five readiness signals.

The five readiness signals

2. 1Managers decideLocal decisions, fewer escalations
3. 2Clean last transitionPhases, risks and exit criteria
4. 3Business understandingOutcomes, not effort
5. 4A view on AIShared literacy and a plan
6. 5Trusted relationshipsClear, constructive, across time zones

A bigger mandate

---

1. Managers who decide, not escalate

If every non-routine question still travels to HQ, sponsors draw a simple conclusion: the centre executes, but someone else owns. Escalations are the most visible signal of readiness, because HQ feels each one directly.

The root cause is usually the middle layer. Fast-growing centres promote strong engineers into management quickly, often without preparation. They keep doing the work themselves, avoid difficult conversations and pass decisions upward because it feels safer.

Strengthening that layer changes HQ’s experience of the centre faster than almost anything else. The goal is not to stop escalating altogether. It is for managers to know which decisions are theirs, make them with confidence and brief HQ afterwards.

2. A clean track record on the last transition

Sponsors remember how the previous transfer went. If knowledge transfer was shallow, risks surfaced late or the “go-live” was followed by a spike in incidents, that memory shapes the next conversation.

A transition that ran through clear phases (shadow, reverse shadow, then independent operation), reported risk honestly and met agreed exit criteria does the opposite. It becomes the reference case HQ uses to justify the next move.

3. Business understanding, not only technical depth

Teams that talk about outcomes, customers and cost are treated as partners. Teams that talk about tickets, effort and utilisation are treated as suppliers, however good their engineering is.

This is often the biggest shift for people who joined from IT services firms, where success was measured against a statement of work. In a captive centre there is no client to escalate to. The measure is what the work does for the business.

Sponsors notice quickly when India teams ask about the customer impact of a change, or propose a simpler way to reach the same result. Those are the moments when a centre starts to look like an owner.

---

4. A credible view on AI

HQ increasingly expects its centres to have a point of view on how AI changes their own work. A centre that waits to be told what to do with AI looks like a centre that will wait to be told what to do with everything else.

Raising that number is less about technical training and more about a shared language in the leadership team: where AI will change the work, which roles need redesigning first, what governance looks like, and how to make the business case to HQ. A leadership team that can answer those questions together stands out.

5. Relationships that work across time zones

The last signal is the hardest to measure and the easiest for HQ to feel. Stakeholders want to be heard, to get early warning when something is off track, and to see constructive pushback rather than a quiet “yes” followed by a missed date.

Centres that run tight global meetings, write clearly and disagree well build trust quickly. That trust is what makes a sponsor comfortable taking the risk of moving more work.

Seen as an execution centre

Seen as an ownership centre

• Escalates non-routine decisions to HQDecides locally and briefs HQ afterwards
• Reports effort, tickets and utilisationReports outcomes for the business
• Waits for a fully formed backlogShapes the roadmap with product owners
• Follows HQ on AIBrings a plan for AI in its own work
• Says yes, then misses datesPushes back early, then delivers

---

Where to start: a 90-day readiness review

Most centres are strong on two or three of these signals. Very few are strong on all five. The weakest one is usually what holds the next mandate back, so that is where to focus.

A simple way to begin:

1. Score each signal honestly. Ask your leadership team, and one or two trusted HQ sponsors, to rate the centre on each signal from one to five. Look for the gaps between the two views.
2. Pick one signal. Choose the weakest, or the one HQ rated lowest. Resist the urge to fix everything at once.
3. Agree a measure. Escalations per month, transition milestones met, or stakeholder feedback scores are all practical. Take a baseline before you start.
4. Act for a quarter. Run a focused programme for the people who drive that signal, whether that is first-time managers, transition leads or the leadership team itself.
5. Ask your sponsor what changed. Do not tell HQ the centre has improved. Ask them what they have noticed. Their answer is the evidence that matters.

Repeat the cycle with the next signal. Over a year, the conversation with HQ shifts from “could your team own this?” to “what else could you take on?”