Skip to content
IKAN, talent mobility

India delivery, written for procurement

The India questions, answered in public.

Scope, city presence, channel safety, evidence status and service recovery in one buyer-ready view.

The public enquiry route publishes its owner and first-response window only after its readiness gates pass. Delivery owners, clocks and any programme SLA are set in the signed engagement.

01 / Scope

Twelve services. No hidden default.

The signed programme decides the included work, owner, evidence and acceptance point.
  1. 01Immigration & VisasRead scope
  2. 02Home Search & Destination ServicesRead scope
  3. 03Corporate Housing & Temporary AccommodationRead scope
  4. 04Family & Education SupportRead scope
  5. 05Tenancy & Lease ManagementRead scope
  6. 06Pet RelocationRead scope
  7. 07Departure & RepatriationRead scope
  8. 08Intercultural & Language TrainingRead scope
  9. 09International Move ManagementRead scope
  10. 10Mobility Policy & ProgramRead scope
  11. 11Employer of Record (EOR)Read scope
  12. 12Fleet & Chauffeur ServicesRead scope

02 / Channel firewall

IKAN does not use a public enquiry to step around an appointed RMC.

  1. 01

    When an RMC is already appointed, IKAN responds through that RMC.

  2. 02

    IKAN does not disclose an RMC client relationship to another provider.

  3. 03

    A person in an unsafe or urgent situation is helped first, and the programme route is informed.

  4. 04

    A reported breach is routed to the IKAN Enquiry Desk for review; the response owner and timing are confirmed on receipt.

Programme readiness

Five readiness gates before a programme scales.

The signed implementation plan sets dates, pilot volume and acceptance criteria. Each gate closes only when both teams confirm readiness.
  1. 01 · ScopeDefine the programme

    Agree services, commercial structure, governance, intake route and the records required before work begins.

  2. 02 · DesignMap the operating playbook

    Align programme instructions with IKAN's delivery process, specialist reviews and channel boundaries.

  3. 03 · ControlSet reporting and escalation

    Confirm reporting, invoicing, data handling, escalation and acceptance criteria.

  4. 04 · ProveRun agreed pilot files

    Test real handoffs, reporting and exception routes with a jointly reviewed pilot set.

  5. 05 · ScaleConfirm steady-state readiness

    Increase volume only when the agreed people, systems, capacity and pilot results support it.

03 / Coverage

Presence is labelled city by city.

Street-address office, on-ground metro team and serviced coverage are different records. Live capacity is checked for the brief.
CityPresencePublished record
BengaluruStreet-address officeIKAN publishes a physical Bengaluru office in Indiranagar.
MumbaiOn-ground metro teamIKAN publishes an on-ground Mumbai metro team; confirm the meeting point, address and live capacity for the move.
Delhi NCRStreet-address officeIKAN's published headquarters address is in Jasola, New Delhi.
HyderabadStreet-address officeIKAN publishes a physical office in Gachibowli, Hyderabad.
PuneStreet-address officeIKAN publishes a physical office in Yerawada, Pune.
ChennaiStreet-address officeIKAN publishes a physical office in Anna Nagar, Chennai.
AhmedabadServiced coverageIKAN supports Ahmedabad and nearby project corridors subject to an advance capacity check; this page does not represent a permanent IKAN office.
KolkataServiced coverageIKAN supports Kolkata subject to a current service and capacity review; this page does not represent a permanent IKAN office.

Another city or corridor? Ask for a capacity check.

04 / Evidence

Know what is proven, agreed, private or not claimed.

A request is not treated as proof. Status, limits, source and programme dependency stay visible.

Evidence key

Status is part of the answer.

  • Externally verified

    A dated public source outside IKAN supports the record.

  • Published record

    IKAN publishes the information, with its source and limits stated.

  • Defined for the programme

    The control is agreed in writing for the specific engagement.

  • Not claimed

    IKAN does not assert a credential or control that it cannot evidence.

  • Shared during due diligence

    The item is handled through an approved due-diligence process, not published on the website.

  • Legal identity recordPublished record

    Legal name and CIN are displayed on this scorecard.

  • Service and city schedulesPublished record

    The public catalogue and presence types are rendered from the site's current content records.

  • Public proof receiptsExternally verified

    Dated source links are rendered from the public claim ledger.

  • Programme governance scheduleDefined for the programme

    Owners, reporting, escalation and acceptance criteria are agreed for the engagement.

  • Insurance evidenceNot claimed

    Not represented as current in this public record. Request dated evidence and verify it before reliance.

    Request dated evidence
  • Continuity evidenceNot claimed

    Not represented as current in this public record. Request the latest dated plan and exercise evidence.

    Request dated evidence
  • Operational performance dataShared during due diligence

    Case volumes, service timings and programme KPIs are shared through an approved due-diligence process, not published on the website.

Control register

Inspect the answer behind each diligence question.

Open only the control family you need. Print and PDF views include the complete record.
01Legal identity and channel safetyWho is the supplier, and how will it protect the existing relationship?

The legal identity is published below. Commercial structure, branding, intake, reporting and data boundaries are then agreed for the engagement.

  • Legal entityPublished record

    IKAN Relocation Services India Pvt Ltd, CIN U74140DL2010PTC202270.

    This is IKAN's published site record. A current registry extract is not attached to this public scorecard.
  • Sponsored-move boundaryPublished record

    India destination services and immigration support for employer- and RMC-sponsored moves.

    A private, self-funded move is not captured as a sales lead through this route.
  • RMC relationshipDefined for the programme

    IKAN works inside the agreed programme relationship. It does not use a public enquiry to step around an appointed RMC.

    Contract hierarchy, white-labelling, communications and escalation are confirmed before live work.
02Governance, reporting and escalationWho owns the India work, and what happens when it changes?

One India lead coordinates the agreed work. Named owners, update fields, exception routes and acceptance criteria belong in the implementation record.

  • Named India leadDefined for the programme

    A lead is appointed for the agreed scope, with specialist owners added where immigration, housing, school, lease or move work requires them.

  • Reporting recordDefined for the programme

    Milestones, open decisions, blockers, next actions, completion evidence and invoice support are mapped to the programme's required format.

  • Escalation routeDefined for the programme

    Operational and management escalation points, severity definitions and handoff rules are agreed before delivery.

  • Public response timingNot claimed

    This scorecard does not publish a universal response-time promise. The website shows a named owner and response window only when the live enquiry route has passed its operational readiness gates.

    Programme delivery and recovery clocks are agreed separately in the signed engagement record.
03Data protection and security evidenceWhat can procurement rely on today?

When secure website intake is enabled, recorded enquiries are stored in IKAN's Upstash-hosted lead queue for up to 90 days and handled under applicable Indian data protection law. Programme data, retention, subprocessors, incident handling and secure channels require written due diligence.

  • Website privacy noticePublished record

    The notice describes website lead data, first-party aggregate measurement, retention and contact rights.

    Read the privacy notice
  • Programme data termsDefined for the programme

    Purpose, data fields, roles, secure transfer, retention, deletion, incident contacts and subprocessor requirements are agreed for the engagement.

  • Security certificationNot claimed

    This scorecard does not assert a security certification. Procurement should request current evidence for every control it needs to rely on.

04Continuity, insurance and referencesWhich diligence documents are public, private or still missing?

Document status is stated directly. A request is not treated as proof, and confidential evidence is not converted into a marketing claim.

  • Business continuity planNot claimed

    This public scorecard does not represent a current plan as verified. Request the latest dated document, accountable owner, scope and exercise evidence.

  • Insurance scheduleNot claimed

    This public scorecard does not represent current insurance as verified. Request a dated certificate, scope, limits, exclusions, insurer and policy period.

  • Client referencesShared during due diligence

    No client or RMC is named on the public site. Any reference process requires approval, consent and contract-safe disclosure.

  • Case results and operating metricsNot claimed

    This public scorecard contains no client-derived or case-derived performance metric.

05Accessibility postureWhat standard is targeted, and what remains to be evidenced?

The site targets WCAG 2.2 Level AA and uses India's IS 17802 and RPwD Rules 2023 as relevant context. This is a target, not a blanket conformance claim.

  • Public accessibility statementPublished record

    The statement records scope, test methods, known limitations and the route for requesting help or an accessible format.

    Read the accessibility statement
  • Automated release checksPublished record

    The release gate is designed to cover sitemap routes at mobile and desktop widths, both motion preferences, keyboard traversal and browser accessibility-tree contracts.

Dated public receipts

Open the source, not just the claim.

  1. Published record1996

    India relocation roots

    IKAN company history (opens in a new tab)Checked 17 August 2026
  2. Externally verified2024

    FEM APAC DSP of the Year

    Forum for Expatriate Management (opens in a new tab)Checked 17 August 2026
  3. Externally verified2025

    FEM APAC DSP of the Year

    FEM APAC EMMAs (opens in a new tab)Checked 17 August 2026
  4. Externally verified4.8 / 5

    501 public reviews at check date

    Trustpilot public profile (opens in a new tab)Checked 17 August 2026 · Ratings and counts change over time.
  5. Externally verifiedSince 2015

    EuRA GQS qualified-member listing

    EuRA qualified members (opens in a new tab)Checked 17 August 2026

05 / Service recovery

A four-level route when the work changes.

Delivery and recovery clocks are set in the signed programme. Immediate danger goes to local emergency services first; the verified consultant or programme route follows.
  1. L1
    Change

    A document, landlord, school date or authority requirement changes the plan.

    First action

    The named lead records the change, explains the effect and names the next decision.

    Owner and clock

    Named IKAN lead. Set in the programme schedule.

  2. L2
    Blocker

    Something in scope cannot proceed and the household or programme is affected.

    First action

    The lead escalates internally and returns a written position with options.

    Owner and clock

    IKAN operations lead. Set in the programme schedule.

  3. L3
    Service failure

    IKAN did not do what the signed scope requires.

    First action

    A management owner records what happened, the recovery action and the next control.

    Owner and clock

    IKAN management. Set in the programme schedule.

  4. L4
    Urgent risk

    A person is unsafe, or there is a legal, immigration or safety emergency.

    First action

    Use the appropriate local emergency service first. Then use the move's verified consultant or programme route.

    Owner and clock

    Local emergency service first; then the named programme owner. Programme timing is set in the signed engagement.

Inspect the service-specific record

Signal
A lease term, property condition, maintenance issue or exit position becomes disputed or unclear.
First action
The tenancy owner gathers the agreement and condition evidence, records each party's position and identifies the decision required.
Escalation
Unresolved contractual, legal or habitability concerns follow the named programme route and accountable specialist boundary.
Record
The evidence, correspondence, owner, decision and remaining action stay attached to the tenancy record.

Capability appendix

The public web selector is replaced in print by the complete current register. Programme owners and clocks remain defined in the signed engagement.

01

Immigration & Visas

  • SignalA document, authority status or dependant requirement changes the agreed route.
  • First actionThe immigration specialist records the change, explains its effect and identifies the next decision.
  • EscalationAn unresolved authority or specialist dependency follows the named programme escalation route, with any external adviser identified.
  • RecordThe live status, open dependency, owner and completion evidence remain in the case record.

02

Home Search & Destination Services

  • SignalLive inventory, a household priority or a landlord position makes the current shortlist unworkable.
  • First actionThe consultant updates the brief, makes the trade-off visible and agrees the next search decision.
  • EscalationCommercial, lease or safeguarding concerns move to the named lead and the programme route before another commitment is made.
  • RecordThe revised brief, decision, owner and next handoff are captured in the move record.

03

Corporate Housing & Temporary Accommodation

  • SignalThe property, dates, readiness check or provider terms no longer fit the confirmed brief.
  • First actionThe service owner records the affected stay, confirms immediate housing facts and compares the viable routes.
  • EscalationSafety, habitability, contracting or unresolved provider issues move through the named programme route with responsibility kept explicit.
  • RecordThe exception, decision, booking owner and transition effect are added to the housing record.

04

Family & Education Support

  • SignalA school calendar, seat position or household priority closes the planned route.
  • First actionThe consultant updates the option set, explains the decision point and reconnects school, home and timing dependencies.
  • EscalationA material family, safeguarding or programme concern moves to the named lead through the agreed channel.
  • RecordThe current options, application status, family decision and open owner are recorded.

05

Tenancy & Lease Management

  • SignalA lease term, property condition, maintenance issue or exit position becomes disputed or unclear.
  • First actionThe tenancy owner gathers the agreement and condition evidence, records each party's position and identifies the decision required.
  • EscalationUnresolved contractual, legal or habitability concerns follow the named programme route and accountable specialist boundary.
  • RecordThe evidence, correspondence, owner, decision and remaining action stay attached to the tenancy record.

06

Pet Relocation

  • SignalA veterinary record, authority rule, airline condition or travel date changes the viable route.
  • First actionThe coordinator pauses the affected handoff, confirms the current requirement and remaps the document, travel and welfare sequence.
  • EscalationA welfare concern or unresolved authority or carrier issue follows the named programme route with the accountable specialist identified.
  • RecordThe requirement source, decision, route change and next owner are added to the pet-move record.

07

Departure & Repatriation

  • SignalA notice date, lease obligation, authority task or onward handoff cannot close as planned.
  • First actionThe named lead rebuilds the responsibility map and separates completed, blocked and newly required work.
  • EscalationA contractual, authority or cross-provider block follows the agreed programme route with the next accountable party identified.
  • RecordThe close-out summary records each open item, owner, evidence and onward handoff.

08

Intercultural & Language Training

  • SignalThe agreed session no longer reflects the role, household context or questions being raised.
  • First actionThe facilitator revisits the brief, records the gap and agrees a more relevant learning focus.
  • EscalationA sensitive workplace, wellbeing or programme concern moves to the named lead and the appropriate accountable route.
  • RecordThe revised brief, completed session and agreed follow-up are recorded without publishing private discussion.

09

International Move Management

  • SignalSurvey facts, documents, carrier capacity, customs status or delivered condition diverges from the agreed plan.
  • First actionThe move coordinator records the exception, protects the evidence and confirms the affected handoff and decision.
  • EscalationCustoms, carrier, loss or damage issues follow the named programme and insurance routes with responsibilities separated.
  • RecordThe shipment status, exception evidence, decision, owner and delivery outcome remain in the move record.

10

Mobility Policy & Program

  • SignalA policy choice creates an unowned exception, conflicting control or delivery gap.
  • First actionThe programme lead records the conflict, affected population and decision authority before recommending options.
  • EscalationLegal, tax, employment, immigration or governance questions move to their accountable owners through the agreed programme forum.
  • RecordThe decision log captures the option, authority, approval and resulting delivery responsibility.

11

Employer of Record (EOR)

  • SignalA role, document, payroll requirement or legal position no longer fits the approved engagement structure.
  • First actionThe service owner pauses the affected action, records the change and reconfirms the responsible legal, tax and payroll reviews.
  • EscalationEmployment, compliance or payroll blocks follow the signed governance route with the accountable entity and specialist named.
  • RecordThe approved structure, exception, decision and next payroll or employment action remain in the engagement record.

12

Fleet & Chauffeur Services

  • SignalThe vehicle, chauffeur, route or booking channel cannot fulfil the confirmed requirement.
  • First actionThe transport owner confirms the traveller's current position, records the exception and checks the approved alternative.
  • EscalationA safety, repeated supply or unresolved dispatch issue follows the named programme route and current duty-of-care process.
  • RecordThe booking, exception, replacement decision and completion status remain in the dispatch record.

06 / The private review

Bring the cities, services and panel date.

IKAN will separate the public record, the programme-defined controls and the documents provided under NDA.

Request diligence pack

Next useful

  1. 01Inspect public evidence
  2. 02Review India coverage
  3. 03Read the published review record

Partner enquiries are read by the Enquiry Desk and routed to account leadership. Your first reply names the owner for the review.