Skills and Bench Planning Agent
Maps engineers' skills against pipeline demand and plans reskilling, redeployment and hiring.
- Industry
- IT Company
- Department
- HR
- Team
- Talent
- Kind
- Decision-maker
- Approver
- Delivery Director
- Code
- HRS-06
It maps the skills and certifications delivery teams have today against what signed SOWs, the weighted pre-sales pipeline and the SaaS roadmap need over the planning horizon, sizes each gap in people and months, and recommends whether to reskill bench engineers, redeploy, hire or use subcontractors. It records the plan in the HR and resourcing system and the resource forecast in the PSA.
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 professional services automation (PSA) system: resource allocations, roll-off dates, bench and the resource demand from SOWs and the pipeline..
- 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 Delivery Director with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the HR and resourcing system: it records the skills plan, reskilling enrolments and new requisitions. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The skills framework: skill taxonomy and levels, certification requirements, reskilling paths and lead times, bench cost, subcontractor rates and internal mobility rules.
Reads from
the professional services automation (PSA) system: resource allocations, roll-off dates, bench and the resource demand from SOWs and the pipeline.
Acts in
the HR and resourcing system: it records the skills plan, reskilling enrolments and new requisitions.
Hands back
A list of gaps, each with skill, level, people_needed, month, fill (reskill, redeploy, hire or subcontract), named_candidates (a list of employee_id or empty), cost_usd and reason.
Asks a person when
The plan recommends hiring, a subcontractor share above 30 percent, or leaves bench cost rising.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Reskilling lead time (months) | 3 | How long it takes to move an engineer to a new skill at working level. |
| Longest acceptable bench (weeks) | 4 | People on the bench longer than this are first in line for redeployment or reskilling. |
| Least probability to plan for (%) | 50 | Pipeline demand below this is listed but not planned for. |
| Most subcontractor share per project (%) | 30 | Subcontractors fill at most this share of a project's team. |
| Managers confirm skill levels | On | When on, self-assessed levels count only once a manager confirms them. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Plan for demand at 50 percent probability or more, weighted by probability.
- Fill gaps first from people rolling off or on the bench, prioritising anyone benched over 4 weeks.
- Recommend reskilling only when the start is at least 3 months away.
- Keep subcontractors to 30 percent of any project team.
- Count only manager-confirmed skill levels when on is true.
- Report skills by team of five or more; never rank individuals.
See the Skills and Bench Planning Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.