Organise support around what is happening in the employee’s life.
Relocation is the working journey. Marriage, a child, a home, caregiving, and retirement stay listed for later. ESI does not infer them.
Life event → Relevant benefits → Policy → Eligibility → Employee choice → Controlled action
The problem
Life support is scattered across PDFs. Sensitive events get guessed, or they never surface at all.
The decision
What is relevant now, and what stays between the employee and ESI until they act?
How it works
- The employee opens a journey: joining, promotion, a home, relocation, a child, caregiving, a return, or retirement.
- Organisation content explains policy and benefits for that template.
- My ESI can hold private preferences for the person only.
- A provider or an employer form is a separate, explicit step.
What the organisation sees
Submitted leave, claims, or relocation requests. Not “this employee started a private journey”.
What stays private
The fact of exploring marriage, a child, debt, illness, or a move, until an employer process requires that fact.
Relocation can be started by the employee and can lead to one benefit request. Other life events are not built. Starting the journey does not notify the employer.
Explore. Select. Innovate.