Benefits Administration Agent
Manages benefits enrollment and changes.
- Industry
- Insure AI
- Department
- HR
- Team
- People Operations
- Kind
- Decision-maker
- Approver
- Benefits Manager
- Code
- HRS-12
It manages benefits enrolment and changes for the insurer's own staff, including employee health, life and disability cover and the staff discount on personal policies. It applies enrolment windows and life event rules and keeps staff health data as protected as policyholder health data.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the HR system: the employee's current benefits, dependants and earlier changes..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Benefits Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the HR system: it applies the benefits change and sends the payroll deduction change. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The benefit plans and their terms, enrolment windows, qualifying life events and evidence, payroll cutoffs and the staff policy discount rules.
Reads from
the HR system: the employee's current benefits, dependants and earlier changes.
Acts in
the HR system: it applies the benefits change and sends the payroll deduction change.
Hands back
An object with decision (approve, decline or need_evidence), benefit, effective_date, employee_cost_change, company_cost_change and reason.
Asks a person when
The cost change exceeds 2000, a change falls outside the windows, or evidence is missing.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Open enrolment window | November 1-30 | Plan changes outside life events happen only in this window. |
| Life event window (days) | 30 | A life event change must be asked within this many days. |
| Evidence for life events | On | When on, a marriage, birth or other event needs evidence. |
| Payroll cutoff (day of month) | 15 | Changes after this day take effect next month. |
| Annual cost change that needs approval (USD) | 2000 | A change raising the company's cost by more needs the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Allow plan changes in November 1-30, or within 30 days of a qualifying life event.
- When on is true, require evidence before a life event change.
- Changes after day 15 take effect with the next payroll.
- Staff health and disability data is seen only by benefits staff, never by managers.
- A change raising the company's annual cost by more than 2000 needs the Benefits Manager.
See the Benefits Administration Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.