Employee Self-Service Insurance Portal: What Good Looks Like
SAIBA Corporate · 13 September 2026 · 6 min read
Every HR team that runs a group health scheme knows the question that arrives ten times a day: am I covered, and where is my card? A self-service portal exists to answer it without a human in the loop. Here is what one should do, and what it takes to make employees actually use it.
Why HR ends up as the insurance help desk
Group medical, group personal accident and group term life cover are bought by the company, administered by a broker or third-party administrator, and used by employees who have never seen the policy. The employee’s only route to information is HR, and HR’s only route is a spreadsheet and an email thread with the broker.
The result is predictable. HR spends its days forwarding e-cards, checking whether a newborn has been added, chasing claim status, and explaining the same room-rent limit to the same people. None of this is HR’s job, and none of it needs a person once the data is in one place.
The portal is the employee-facing end of the same register HR uses for group health administration. If that register is current, the portal is right. If it is not, the portal is a faster way to give wrong answers.
What employees should be able to do
Keep the scope tight and make everything on it work perfectly. A useful self-service portal lets an employee:
- See their cover — which policies they are on, the sum insured, the policy period, and the main limits and exclusions in plain language rather than a scanned schedule.
- Download e-cards for themselves and every dependant, in a format a hospital admissions desk will accept.
- View and update dependants — add a spouse or newborn within the policy’s window, with the documents the insurer needs uploaded once, and see when the addition was accepted.
- Track claims — a cashless pre-authorisation or reimbursement claim with its current status, what is outstanding, and who to contact if it is stuck.
- Find a network hospital near them, with a clear note on whether cashless is available.
- Request business travel cover — dates, destination and purpose, routed for approval and returned as a certificate; see business travel insurance for employees for how that flow should work.
- Update nominees for group term life and personal accident cover, with an audit record of each change.
- Read the documents — policy summary, claim forms, the hospitalisation checklist — without emailing anyone.
Everything else — wellness content, flexible benefits, salary sacrifice schemes — can come later or live elsewhere. Do not let it crowd out the eight things above.
What it takes off HR's desk
The direct saving is the queue of routine questions. The larger saving is in the work HR did to answer them: maintaining a dependant list by hand, reconciling it against the insurer’s active roster, and raising endorsements by email.
With a portal in place, dependant additions arrive as structured requests with documents attached, ready to batch into the next endorsement to the insurer. Claim status stops being a phone call to the broker because the broker or administrator updates it once and everyone sees it. E-card requests disappear entirely.
HR’s job shifts from answering to approving: reviewing the day’s dependant requests, chasing the insurer on stale claims, and looking at which questions still reach a human so the portal can answer them next time.
Adoption: mobile, WhatsApp and e-sign
A portal nobody opens changes nothing. The employees who need cover information most urgently are usually standing in a hospital corridor with a phone, not at a desk with a laptop. Design for that.
- Mobile first. The e-card and the network hospital search must work on a phone screen with poor signal. If the portal only works on the office network, it has failed at the moment it is needed.
- No password to remember. Single sign-on where the company has it; a one-time code to the registered mobile number where it does not. Blue-collar and field staff without corporate email need the second route.
- WhatsApp for the common cases. Sending an e-card, confirming a claim status or acknowledging a dependant request over WhatsApp reaches people who will never install an app. Keep the portal as the system of record and WhatsApp as a channel to it.
- E-sign where a signature is needed. Nominee changes, dependant declarations and travel requests can carry an electronic signature so nothing is printed, signed and scanned.
- Launch at enrolment. The annual enrolment window, when everyone must confirm dependants anyway, is the one moment employees will log in. Use it, and make the first login rewarding: their card is already there.
Measure adoption honestly: what share of employees have logged in, how many e-cards were self-downloaded versus sent by HR, and how many questions still arrive by email.
Privacy and access control
The portal holds health information, family details and identity documents. Treat it accordingly.
Employees should see only their own records and those of their declared dependants. HR administrators should be scoped to the entities and locations they serve, and should see claim status without seeing diagnosis or treatment detail unless their role requires it. Brokers and administrators should have their own limited roles. Every view of a claim record, not just every edit, should be logged.
Collect only what the insurer needs to enrol a dependant, store documents encrypted, and set a retention rule so leavers’ records are not kept indefinitely. Where consent is required under data protection law for processing health data, capture it in the portal at enrolment rather than on a paper form that nobody can find later.
Integration with HR joiners and leavers
The portal is only as accurate as the roster behind it, and the roster changes every day. A new joiner expects cover from day one; a leaver must come off the policy so premium is refunded and no claim is paid on a person who has left. Both depend on the HR system telling the insurance register promptly.
The integration does not need to be elaborate. A daily feed of joiners, leavers and changes from the HRMS — employee ID, name, date of birth, date of joining or leaving, entity, location, grade — is enough to drive enrolment, generate the endorsement batch for the insurer, and switch portal access on and off. Grade matters because it usually determines the sum insured and whether parents are eligible.
Where no HRMS exists, a controlled monthly upload from HR’s master list is the fallback. What does not work is HR emailing the broker a list of names whenever someone remembers.
What good looks like
A well-run portal is quiet. Employees find their card without asking. Dependant additions flow through within the insurer’s window. Claim status is visible without a phone call. HR’s inbox on the first working day after a public holiday is no longer full of insurance questions.
Behind it sits one register that HR, the broker and finance all work from, so the portal, the endorsement to the insurer and the premium allocation to business units all agree. Platforms such as SAIBA Corporate are built around that single register, with the employee portal as one of its faces rather than a separate system to keep in sync.
If you are starting from nothing, start small: e-cards, cover summary and dependant requests for one entity, connected to the HR feed. Get those three right and the rest is addition, not rework.
Frequently asked questions
Can employees file claims directly through the portal?
Usually they can start a reimbursement claim by uploading bills and discharge documents, and track a cashless pre-authorisation that the hospital raised. The claim itself is still assessed by the insurer or administrator. The portal's value is that documents arrive complete, status is visible, and HR is no longer the intermediary.
Do we need a separate mobile app?
Not necessarily. A portal that works well in a phone browser, with a one-time code login and a downloadable e-card, covers most needs. An app helps if you want push notifications for claim updates. Whatever you choose, the portal must be usable on a phone with poor connectivity, because that is where it will be opened in an emergency.
How do employees without a corporate email log in?
Through a one-time code sent to the mobile number HR holds for them, or through WhatsApp. Field staff, plant workers and contract employees are often the people who most need quick access to an e-card, so a login route that does not depend on corporate email is essential, not an extra.
How is employees' medical information protected?
By role-based access so each person sees only their own records, encryption of stored documents, logging of every view of a claim, and a retention rule that removes leavers' data after a set period. HR staff should see claim status but not clinical detail unless their role needs it, and consent for processing health data should be captured at enrolment.
See your insurance program in one place
SAIBA Corporate turns scattered policies, assets and gaps into one live command centre — registers, cover rules, renewals and claims across every business unit. On your servers or on SAIBA Cloud.
Request a walkthrough →