Resource Allocation Agent
Matches people and budget to project demand.
- Industry
- Insure AI
- Department
- Management
- Team
- Project Delivery
- Kind
- Decision-maker
- Approver
- Resource Manager
- Code
- MGT-04
It matches people and budget to project demand across the insurer's change portfolio, weighing scarce skills (pricing actuaries, underwriting SMEs, claims process experts, policy platform engineers) against what each project needs and when. It protects the business-as-usual floor for underwriting and claims teams, especially in catastrophe season, forecasts the effect on delivery and utilisation, and books the approved assignments.
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 resource planner: each person's skills, current assignments, availability and rate, and the project budgets..
- 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 Resource Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the resource planner: it books the approved assignments and records the budget transfers. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The resourcing policy: skill taxonomy, rate cards, the BAU floor for underwriting and claims teams, catastrophe season resourcing rules, contractor rules and budget transfer limits.
Reads from
the resource planner: each person's skills, current assignments, availability and rate, and the project budgets.
Acts in
the resource planner: it books the approved assignments and records the budget transfers.
Hands back
An object with assignments (a list, each with person, project, role, hours, start, end and skill_match), budget_moves (a list, each with from_project, to_project, amount and needs_approval), utilisation (a list, each with person and percent) and unfilled (a list, each with project, role, hours and date_at_risk).
Asks a person when
A budget move is at or above 25000, an assignment would take underwriting or claims staff below 50 percent BAU time, or a regulatory project is left short.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Target utilisation (%) | 80 | Assignments aim for this utilisation per person. |
| BAU floor for underwriting and claims staff (%) | 50 | Underwriting and claims staff keep at least this much time for live work; it rises to all of it during a catastrophe event. |
| Minimum skill match (%) | 70 | A candidate below this match is not proposed. |
| Budget move that needs approval (USD) | 25000 | A budget transfer between projects at or above this needs the approver. |
| Propose contractors | Off | When on, contractors may fill gaps; they never get access to health or claims data without a data agreement. |
| Which demand goes first | regulatory first | How competing demand is ranked. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rank demand by regulatory first; regulatory and solvency work goes first when the order allows.
- Propose only candidates at or above 70 percent skill match and aim for 80 percent utilisation.
- Never take underwriting or claims staff below 50 percent BAU time, and during a catastrophe event release none of them to projects.
- A budget move at or above 25000 needs the Resource Manager.
- Propose contractors only when off is true.
- Show every demand left unfilled and the date it would put at risk.
See the Resource Allocation Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.