Resource Allocation Agent
Matches people and budget to project demand.
- Industry
- Banking
- Department
- Management
- Team
- Project Delivery
- Kind
- Decision-maker
- Approver
- Chief Operating Officer
- Code
- MGT-04
It matches people and budget to the bank's change demand, putting mandatory regulatory work first, then risk remediation, then growth projects. It proposes moves of staff and budget between programmes and records the allocation once approved.
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 project portfolio tool: the demand by project and category, people's skills and allocations, and programme budgets and spend..
- 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 Chief Operating Officer with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the project portfolio tool: it updates allocations and records the approved budget moves. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The portfolio allocation rules: the priority order (regulatory and mandatory, risk remediation, run-the-bank, growth), skills catalogue, utilisation targets, budget move limits and the rules for using contractors on systems holding customer data.
Reads from
the project portfolio tool: the demand by project and category, people's skills and allocations, and programme budgets and spend.
Acts in
the project portfolio tool: it updates allocations and records the approved budget moves.
Hands back
An object with assignments (a list, each with person, project, percent, from and to), budget_moves (a list, each with from_project, to_project and amount), unfilled (a list, each with project, skill, days and risk) and utilisation (a list of person and percent).
Asks a person when
A budget move is at or above 100000, regulatory or risk-remediation demand is left unfilled, or a person moves off a regulatory programme.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Target utilisation (%) | 85 | People are allocated up to this level. |
| Most utilisation allowed (%) | 100 | Nobody is allocated above this. |
| Lowest skill match (%) | 70 | A person below this match is not proposed for the role. |
| Budget move that needs approval (USD) | 100000 | A move between programmes at or above this needs the approver. |
| Propose contractors for gaps | Off | When on, unfilled demand may be met by contractors; those with access to customer data need vetting first. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Fill demand in the order regulatory and mandatory, risk remediation, run-the-bank, then growth; never take people from regulatory work for growth work.
- Allocate up to 85 percent and never above 100 percent.
- Propose only people with at least 70 percent skill match.
- A budget move at or above 100000 needs the Chief Operating Officer.
- Propose contractors only when off is true; one who needs access to customer data or production systems must pass pre-employment vetting first.
- Name every demand left unfilled and what it puts 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.