The parent company rolls out a new leave policy by email on a Thursday. It assumes a five day week, a long summer break and a single public holiday calendar. The India team of ninety reads it on Friday and sends the centre head seventeen questions by Monday. She has no way to answer most of them, because nobody told her which parts are negotiable.
This is the everyday friction of a global parent and an India team. This guide shows how an India head can sort the parent's rules, adapt what must change, and keep the relationship with headquarters steady.
Why global rules misfit
A global policy is written for the average of many countries, which often means no country. It may assume statutory rights, working patterns, benefit norms or hiring practices that differ in India. It may also assume that managers know the policy, which is rarely true in a younger centre.
The parent usually wants consistency for fairness, cost control and risk. The India team wants rules that make sense on the ground. Both are reasonable. The task is to find where consistency matters and where local fit matters more.
Sort every policy into three piles
- Apply as written: values, code of conduct, information security, anti-bribery, conflict of interest.
- Apply with local changes: leave and holidays, working hours, expenses, travel, benefits, notice and probation terms.
- Replace with a local policy: anything that touches employment terms, pay structure or practices specific to India.
Do this with the parent HR partner, not alone. Walk through each policy and ask what the headquarters wants to protect. Often the goal can be met with a different method. A global expense rule meant to control cost may work with a local limit table.
A process for aligning, step by step
- 1
List every policy in force
Collect all global policies, forms and manager guides that touch the India team. Note who owns each at headquarters.
- 2
Read each with the team in mind
Ask two or three managers and a few employees where the policy confuses them or conflicts with how work happens. Mark the questions.
- 3
Check with your own advisers
Take every item touching employment terms, pay, benefits or data to your qualified legal and tax advisers. Record their points.
- 4
Propose changes in a standard note
For each policy, write the policy name, the issue, the proposed local version, the reason and who is affected. One page per policy.
- 5
Agree owners and dates
Name who signs off at headquarters, who signs off locally and when it takes effect.
- 6
Publish an India addendum
Issue the local version in plain words, with the global one linked. Brief managers before the staff announcement.
- 7
Review yearly
Check what generated questions or complaints and update the addendum.
Where friction shows up most
Working hours cause the first conflict. A team that joins late calls with the parent will ask for flexible starts, and the global policy may not mention it. Decide who approves the pattern, how late calls are compensated in time off, and how managers avoid assuming that someone is always available.
Leave and holidays come next. Agree an India holiday calendar, how floating days work, and what happens when the parent's release date falls on a local festival. Performance reviews are the third: global cycles often fall on dates that clash with local appraisal timing, so agree the calendar and rating scale.
Pay bands and global grades
Parent grades may map poorly to local roles. A global grade for senior engineer might hold people paid very differently in India. Build a mapping table of global grade to local role family and level, and a pay range for each. Treat the ranges as the company's decision and review them yearly. Never copy the parent's figures into India without asking whether they fit the local market.
Policy name and global owner.
Issue found in India, with an example.
Proposed local rule in plain words.
Reason in one sentence.
People affected and how many.
Advisers consulted and date.
Sign-off from headquarters and from the India head.
Effective date and manager briefing date.
Review date.Keeping headquarters on side
Parents resist changes that look like exceptions without reasons. Show them that you are asking for fit, not for special treatment. Bring evidence such as questions from staff, a clash with a local date, or a case where the global rule cannot be followed. Offer a trade: the India team will follow the global rule on the matters that headquarters cares most about, such as security, conduct and reporting.
Governance so the rules stay aligned
Set a simple governance routine. One person at each end owns the policy list. Changes go through a short note. A quarterly call reviews open questions. The service on HR policies and governance from GullyHR helps with policy sets, approval routes and manager briefings for firms in this position.
Enterprise software firms with global parents face the same questions at scale. See the notes on enterprise software companies for how those teams are usually structured.
Brief the managers first
Managers answer most questions in practice. Give them a one page guide with the five rules they will be asked about, the cases where they must check with HR, and who to ask. A manager who can answer in one minute prevents a week of rumours. For a new centre, the first ninety days guide sets out what to have ready before policies are published.
Listen after you publish
After the addendum goes out, collect questions for a month. Group them by theme, fix unclear wording, and tell staff what changed. Share the questions with headquarters too. They show where a global rule, written for a different setting, leaves people guessing.
