A global capability centre does not need a foreign office copied into an Indian floor plate. It needs a clear standard translated into a local building, local approvals, local climate and local ways of working. The best projects keep the global intent and adapt the parts that must respond to the site.
For a Pune or Mumbai project, the useful question is not whether a design looks current. It is whether the brief, building, services, procurement and operating rules agree. The following framework is written for decision-makers who need a workplace that can be priced, built, occupied and maintained.
Freeze the non-negotiables
Start with the standards that must be identical across locations: security zones, identity, room naming, technology baseline, accessibility approach, critical adjacencies and brand elements. Put these in a short global standard. Do not make every finish, workstation and meeting room untouchable. A standard that cannot be procured, maintained or approved locally becomes a source of delay.
Create a second document for local decisions. It should cover landlord rules, floorplate, fire and life-safety coordination, services capacity, materials, labour, operating hours and local procurement. The two documents together prevent the usual argument between 'global consistency' and 'local reality'.
Design for the operating model
A GCC may combine engineering, finance, support, analytics and leadership functions. Each has different confidentiality, collaboration and resilience needs. Map the work rather than using department names alone. Mark restricted data, incident response, quiet concentration, training, visitor access and 24-hour or shift-based requirements.
A test-fit should show the reason behind each zone. If a secure room exists, show the security boundary. If a team needs a home neighbourhood, show how it grows. If a room is shared across time zones, show its booking and acoustic assumptions. This turns a layout into an operating model people can challenge.
Coordinate technology with the room
Technology is not a late furniture accessory. Meeting-room microphones, cameras, displays, access readers, sensors, wireless access points and power all need locations, pathways and maintenance access. Include IT and AV leads while the walls are still movable. A pretty room that cannot support a reliable call has failed its core test.
Use a tiered room standard rather than specifying the most expensive equipment everywhere. Define a small room, medium room, boardroom and training room by use, capacity, acoustic needs and support model. The result is easier to procure and easier for a regional facilities team to maintain.
Respect the building and climate
Pune and Mumbai projects inherit different buildings, neighbourhood constraints and landlord systems. Confirm the handover condition, fresh-air strategy, cooling capacity, electrical load, water, drainage, fire systems and access rules. Do not infer building performance from a brochure or from a different site in the same city.
Building-services design is a measured coordination exercise. BEE's official site and professional guidance such as the CIBSE Knowledge Portal are useful starting points, but the appointed consultants and authorities must confirm the project's applicable requirements. That distinction belongs in the design record.
Build a repeatable governance rhythm
Global teams need decisions at the right level. Use a decision log with owner, due date, impact and approval status. Hold a short weekly design review and a separate commercial review. Escalate only decisions that affect the global standard, risk, cost or programme. Everything else should be resolved by the local project team.
A single accountable design-build partner can make coordination easier, but governance cannot be outsourced. The client still owns the operating brief, security requirements, technology standards and acceptance tests. Capture each approval so a late reviewer is not asked to reconstruct six months of meetings.
Commission the workplace, not just the hardware
Before opening, test the user journey: arrive, authenticate, find a seat, book a room, join a call, adjust comfort, report a fault and leave securely. Test representative rooms at realistic occupancy. Give facilities staff the manuals and training they need, then track the first weeks of defects.
A GCC launch is a business change. Pair the physical handover with neighbourhood guides, booking rules, help-desk routes and leadership behaviour. The aim is not to announce a fashionable workplace. It is to give people a dependable one.
Before approval, ask three plain questions. What is known from the site or the client? What is still an assumption? What will prove the decision worked after installation? Put the answers beside the relevant drawing, schedule or source. This keeps the conversation honest when the project moves from strategy to design, from design to procurement and from procurement to handover.
A decision checklist for the project meeting
Use this checklist to turn the article into a controlled next step. It is intentionally practical: each item should have a named owner, a source or drawing, a decision date and a test that another person can verify. If an item is still an assumption, label it as one. That is not a weakness. It is a warning before the assumption reaches procurement or site work.
- Freeze the non-negotiables: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Design for the operating model: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Coordinate technology with the room: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Respect the building and climate: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Build a repeatable governance rhythm: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Commission the workplace, not just the hardware: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
For a live project, carry the open questions into the brief, cost plan, programme and handover record. The team should be able to tell what is confirmed, what is provisional, what is excluded and what will be checked after installation. That discipline is more valuable than adding another adjective to the design description.
Decision matrix for this project
This guide is most useful when it becomes a project control. Use the table below to assign an owner, retain the evidence and define what will count as done. It keeps a design conversation connected to procurement, site work and handover.
| Decision area | Question to answer | Evidence to retain |
|---|---|---|
| Global standard | Which user and risk requirements must remain consistent? | Short non-negotiables document |
| Local translation | What must adapt to the building, climate and approvals? | Site survey and landlord rules |
| Technology | Which room types and systems need a common support model? | Room catalogue and interface map |
| Launch | How will the workplace be tested before occupation? | User journey, commissioning and training record |
Implementation checklist
Before releasing the next drawing, order or site instruction, check each of these items. A useful checklist does not replace judgement. It makes the judgement visible to the people who must approve, build and operate the workplace.
- Global standard: record the decision owner, evidence source, decision date and acceptance test.
- Local translation: record the decision owner, evidence source, decision date and acceptance test.
- Technology: record the decision owner, evidence source, decision date and acceptance test.
- Launch: record the decision owner, evidence source, decision date and acceptance test.
Questions decision-makers ask
The central decision is translating a GCC standard into a Pune or Mumbai building without losing security, technology or operational intent. Keep that decision visible in the brief so layout, procurement and delivery choices can be tested against it.
Confirm the evidence listed in the decision matrix: the scope, responsible owner, relevant drawings or records, and the date when the decision will be accepted. Mark assumptions instead of treating them as facts.
Coordinate it before procurement and before ceilings, partitions or services are closed. Late coordination usually turns a design question into a variation, rework or an operational compromise.
Separate global non-negotiables from local decisions, then run a site-led test-fit with facilities, IT, security and the delivery team. The useful next step is a controlled review with a named owner, an agreed evidence source and a simple acceptance test.
Sources and scope note
This article uses the official and professional reference pages below for the limited points they publish. Recommendations about layout, procurement and delivery are Vektor Spaces' practical project guidance, not a claim that a rating, code approval or performance outcome has been achieved. Confirm the current requirements with the appointed consultants, landlord and authorities for the actual project.
- Bureau of Energy Efficiency. Official BEE website. The article treats energy-code compliance as a project-specific design and approval question, not a universal promise.
- CIBSE Knowledge Portal. Professional engineering guidance portal used as a reference point for building-services design and operational questions.
- IGBC Green New Buildings rating system. Official IGBC page describing its Green New Buildings rating system and the wider family of green-building programmes.
- GRIHA rating. Official GRIHA page describing the national green-building rating approach and project evaluation.