HR professionals spend an average of nine hours a week just answering employee benefits questions, according to HealthJoy’s survey of more than 9,000 HR professionals (July 2020) — despite a decade of self-service software promising to fix exactly that. At most universities, supplementary insurance enrollment is the clearest example: a paper form, a signature, a trip to the HR office, and a data-entry clerk retyping it all into a spreadsheet.
Self-service portals are supposed to solve this. When they work, they take routine tickets like leave balances, payslip lookups and policy questions off HR's desk by letting employees handle them directly. But a lot of self-service rollouts fail quietly: they digitize the bureaucracy without removing it. An online form that still needs an HR staffer to verify identity, cross-check a national ID, and manually approve every submission isn't self-service — it's the same paperwork with extra steps.
The part self-service usually skips: who's actually asking
Verifying that the person enrolling a spouse or a child in supplementary insurance is actually who they claim to be is the step most self-service portals quietly outsource back to a human. That's the piece worth automating first, not last — because it's the one that currently requires a staff member's judgment call for every single request.
FanCover, our supplementary-insurance management system for organization staff, starts there. Login runs through a national identity provider (دولتمن), so identity is verified before a request ever reaches HR's queue — not after. From there, staff manage their own insurance records and register dependents directly; HR reviews and approves instead of retyping. The system runs as an isolated microservice with its own database, so it doesn't sit inside the same blast radius as unrelated HR data. Built for Lorestan University's staff insurance program and multi-tenant for any organization with the same need.
If your HR team is still the bottleneck between a staff member and their insurance coverage, the fix usually isn't a bigger form — it's removing the identity-verification step from the human queue entirely.
We also wrote about why FanCover runs as its own isolated service, not a CMS module, and what that separation protects.
Enrollment is only the first step; the larger workload comes later, as we showed in tracking a supplementary insurance claim after it's filed.
Student services have the same problem in a sharper form at the start of each term; see what a real single service window needs.
