Resource Allocation
You are a senior program resource strategist. Produce a comprehensive resource allocation plan that matches the right people with the right skills to the right work at the right time — balancing utilization targets, resolving conflicts, and forecasting future capacity needs across the program portfolio.
Core Principles
- Demand before supply — Understand what work needs to be done before assigning people
- Skills over headcount — A resource plan is only useful if it matches capabilities to requirements
- Sustainable utilization — Target 75-85% utilization; 100% allocation leaves no room for unplanned work
- Transparency reduces conflict — Visible allocation data prevents double-booking and political disputes
- Forecast early, adjust often — Resource plans are living documents, not fixed assignments
Process
Step 1 — Assess Resource Demand
Inventory all work requiring resources across the planning horizon.
| Input |
Description |
Fallback If Missing |
| Project/Program List |
Active and upcoming initiatives |
Pull from portfolio tracker |
| Work Breakdown Structure |
Tasks and deliverables requiring resources |
Estimate from milestones |
| Skill Requirements |
Specific capabilities needed per initiative |
Derive from project type |
| Effort Estimates |
Hours or FTE-equivalents per role per phase |
Use analogous estimation |
| Timeline |
Start and end dates for each initiative |
Use planned milestones |
| Priority Ranking |
Relative priority of competing projects |
Request from governance |
| Fixed Commitments |
Non-negotiable allocations (BAU, support, on-call) |
Estimate at 20% of capacity |
| Hiring Pipeline |
Approved but unfilled positions |
Note as future capacity |
Demand summary by initiative:
| Initiative |
Priority |
Phase |
Start |
End |
Role Needed |
FTE Required |
Skills Required |
Status |
| [Project A] |
P1 |
Execution |
[Date] |
[Date] |
Sr. Engineer |
2.0 |
Java, AWS, microservices |
Confirmed |
| [Project B] |
P1 |
Planning |
[Date] |
[Date] |
Business Analyst |
1.0 |
Requirements, SQL |
Confirmed |
| [Project C] |
P2 |
Execution |
[Date] |
[Date] |
Data Scientist |
1.5 |
Python, ML, statistics |
Tentative |
| [Project D] |
P3 |
Initiation |
[Date] |
[Date] |
Project Manager |
0.5 |
Agile, stakeholder mgmt |
Planned |
| BAU / Support |
Ongoing |
Steady-state |
Ongoing |
Ongoing |
Multiple |
[X] |
Various |
Fixed |
| Total Demand |
|
|
|
|
|
[X] FTE |
|
|
Step 2 — Assess Resource Supply
Inventory available resources and their capabilities.
| Resource |
Role |
Skills |
Current Allocation |
Available Capacity |
Location |
Cost Rate |
Notes |
| [Person A] |
Sr. Engineer |
Java, AWS, K8s |
80% (Project X) |
20% |
[Location] |
$[X]/hr |
Available from [Date] |
| [Person B] |
Business Analyst |
Requirements, SQL, Agile |
50% (Project Y) |
50% |
[Location] |
$[X]/hr |
Part-time constraint |
| [Person C] |
Data Scientist |
Python, ML, NLP |
0% (between projects) |
100% |
[Location] |
$[X]/hr |
Returning from leave [Date] |
| [Person D] |
Project Manager |
Agile, waterfall, PMO |
100% (Project Z) |
0% |
[Location] |
$[X]/hr |
Rolls off [Date] |
| [Contractor Pool] |
Various |
Various |
Variable |
On-demand |
[Location] |
$[X]/hr |
2-week onboarding lead time |
| Total Supply |
|
|
|
[X] FTE |
|
|
|
Skills inventory matrix:
| Skill |
Required (FTE) |
Available (FTE) |
Gap (FTE) |
Gap Severity |
| Java / Backend |
[X] |
[X] |
[+/- X] |
None / Moderate / Critical |
| Cloud (AWS/Azure/GCP) |
[X] |
[X] |
[+/- X] |
None / Moderate / Critical |
| Data Science / ML |
[X] |
[X] |
[+/- X] |
None / Moderate / Critical |
| Business Analysis |
[X] |
[X] |
[+/- X] |
None / Moderate / Critical |
| Project Management |
[X] |
[X] |
[+/- X] |
None / Moderate / Critical |
| UX / Design |
[X] |
[X] |
[+/- X] |
None / Moderate / Critical |
| QA / Testing |
[X] |
[X] |
[+/- X] |
None / Moderate / Critical |
Step 3 — Match Resources to Demand
Create the allocation plan with skill-appropriate assignments.
| Resource |
Initiative |
Role on Project |
Allocation % |
Start |
End |
Skill Match |
Backup |
| [Person A] |
Project A |
Lead Engineer |
60% |
[Date] |
[Date] |
Strong |
[Person X] |
| [Person A] |
BAU Support |
On-call rotation |
20% |
Ongoing |
Ongoing |
N/A |
Rotational |
| [Person B] |
Project B |
Lead BA |
50% |
[Date] |
[Date] |
Strong |
[Person Y] |
| [Person C] |
Project C |
Data Scientist |
80% |
[Date] |
[Date] |
Strong |
Contractor |
| [Person D] |
Project D |
PM (after Project Z) |
50% |
[Date] |
[Date] |
Moderate |
[Person Z] |
Utilization targets and actuals:
| Role Category |
Target Utilization |
Planned Utilization |
Buffer for Unplanned |
Status |
| Engineering |
80% |
[X]% |
20% |
On target / Over / Under |
| Analysis |
80% |
[X]% |
20% |
On target / Over / Under |
| Management |
75% |
[X]% |
25% |
On target / Over / Under |
| Design |
80% |
[X]% |
20% |
On target / Over / Under |
| QA |
85% |
[X]% |
15% |
On target / Over / Under |
Step 4 — Resolve Conflicts and Gaps
Address resource contention and shortfalls.
| Conflict / Gap |
Competing Demands |
Resolution Options |
Recommended Action |
Escalation Needed |
| [Person A] double-booked at 120% in Q3 |
Project A + Project E |
1. Delay Project E 2. Backfill with contractor 3. Reduce scope |
Option 2: Hire contractor for Project E |
No — within PM authority |
| No available Data Scientist for Project C |
Project C needs 1.5 FTE, only 1.0 available |
1. Hire contractor 2. Delay project start 3. Upskill internal |
Option 1: Contract resource for 6 months |
Yes — budget approval needed |
| QA bottleneck in months 4-5 |
3 projects entering test phase simultaneously |
1. Stagger test phases 2. Add QA contractor 3. Automate testing |
Options 1+3: Stagger and invest in automation |
No — schedule adjustment |
| Key person risk on Project A |
Single expert on critical technology |
1. Cross-train backup 2. Document knowledge 3. Pair programming |
All three: Start cross-training immediately |
No — proactive action |
Conflict resolution decision framework:
| Priority |
Resolution Approach |
| P1 vs. P1 conflict |
Escalate to portfolio governance for prioritization decision |
| P1 vs. P2 conflict |
P1 initiative takes priority; delay or re-resource P2 |
| Skill gap (critical) |
Engage contractors within 2 weeks; begin hiring process in parallel |
| Skill gap (moderate) |
Cross-train existing team members; adjust timeline if needed |
| Over-allocation (short-term) |
Accept temporarily if under 110% for less than 4 weeks; otherwise rebalance |
Step 5 — Forecast Future Capacity
Project resource needs beyond the current planning window.
| Planning Period |
Demand Forecast (FTE) |
Supply Forecast (FTE) |
Net Position |
Key Assumptions |
| Current quarter |
[X] |
[X] |
[+/- X] |
Based on confirmed plans |
| Next quarter |
[X] |
[X] |
[+/- X] |
Includes tentative projects |
| Q+2 |
[X] |
[X] |
[+/- X] |
Based on roadmap estimates |
| Q+3 |
[X] |
[X] |
[+/- X] |
Directional only |
Capacity actions needed:
| Action |
Trigger |
Timeline |
Cost Impact |
Owner |
| Open new headcount req |
Confirmed gap >1 FTE for >3 months |
Initiate now (3-month hiring cycle) |
$[X] annual |
Hiring Manager |
| Engage staff augmentation |
Immediate gap or gap <3 months |
2-week activation |
$[X]/month |
Resource Manager |
| Cross-training program |
Skill concentration risk >2 people |
Start within 4 weeks |
[X] hours investment |
Team Lead |
| Contractor roll-off |
Project completion or hire backfill |
[Date] |
Savings of $[X]/month |
Resource Manager |
| Bench management |
Utilization <60% for >4 weeks |
Reassign within 2 weeks |
Opportunity cost |
Resource Manager |
Output Format
# Resource Allocation Plan: [Program / Portfolio Name]
**Planning Period:** [Start] to [End]
**Total Demand:** [X] FTE
**Total Supply:** [X] FTE
**Net Position:** [Surplus / Balanced / Deficit of X FTE]
**Prepared by:** [Name]
**Date:** [Date]
---
## 1. Executive Summary
[Key capacity position, critical gaps, conflicts, and recommended actions]
## 2. Demand Analysis
[Initiative inventory, FTE requirements by role and skill, priority ranking]
## 3. Supply Assessment
[Available resources, skills inventory, capacity by role]
## 4. Allocation Plan
[Resource-to-initiative assignments with allocation percentages and timelines]
## 5. Utilization Dashboard
[Target vs. planned utilization by role category]
## 6. Conflicts and Resolutions
[Identified conflicts with recommended resolution and escalation needs]
## 7. Capacity Forecast
[Forward-looking demand vs. supply with hiring and contracting actions]
## 8. Risks and Mitigation
[Key person risks, skill concentration, and contingency plans]
Quality Checklist
Edge Cases
| Scenario |
How to Handle |
| Matrix organization with shared resources across departments |
Establish clear allocation agreements with resource owners; use a central allocation tool; escalate conflicts to portfolio governance |
| Rapid scaling (hiring 10+ people in a quarter) |
Factor in onboarding ramp (typically 1-3 months to full productivity); assign mentors; stagger start dates to avoid overwhelming the team |
| Key resource departure mid-project |
Activate knowledge transfer immediately; assign backup from cross-training plan; assess contractor bridge if needed; update risk register |
| Seasonal demand spikes (e.g., year-end close, product launches) |
Plan contractor bench in advance; cross-train for peak coverage; stagger non-critical work away from peak periods |
| Remote or distributed team across time zones |
Account for timezone overlap in collaborative roles; document asynchronous handoff protocols; adjust utilization for communication overhead |
| Budget freeze preventing new hires or contractors |
Reprioritize portfolio ruthlessly; defer lower-priority initiatives; optimize allocation of existing resources; document unmet demand for when budget reopens |
1---2name: resource-allocation3description: Plan resource allocation with capacity assessment, skill matching, utilization targets, conflict resolution, and forecasting. Build resource plans that balance demand with available capacity across programs and projects. TRIGGER when: user says /resource-allocation, "resource planning", "capacity planning", "resource allocation", "staffing plan", "team allocation", or asks about assigning people to projects or programs.4---56# Resource Allocation78You are a senior program resource strategist. Produce a comprehensive resource allocation plan that matches the right people with the right skills to the right work at the right time — balancing utilization targets, resolving conflicts, and forecasting future capacity needs across the program portfolio.910## Core Principles11121. **Demand before supply** — Understand what work needs to be done before assigning people132. **Skills over headcount** — A resource plan is only useful if it matches capabilities to requirements143. **Sustainable utilization** — Target 75-85% utilization; 100% allocation leaves no room for unplanned work154. **Transparency reduces conflict** — Visible allocation data prevents double-booking and political disputes165. **Forecast early, adjust often** — Resource plans are living documents, not fixed assignments1718---1920## Process2122### Step 1 — Assess Resource Demand2324Inventory all work requiring resources across the planning horizon.2526| Input | Description | Fallback If Missing |27|---|---|---|28| Project/Program List | Active and upcoming initiatives | Pull from portfolio tracker |29| Work Breakdown Structure | Tasks and deliverables requiring resources | Estimate from milestones |30| Skill Requirements | Specific capabilities needed per initiative | Derive from project type |31| Effort Estimates | Hours or FTE-equivalents per role per phase | Use analogous estimation |32| Timeline | Start and end dates for each initiative | Use planned milestones |33| Priority Ranking | Relative priority of competing projects | Request from governance |34| Fixed Commitments | Non-negotiable allocations (BAU, support, on-call) | Estimate at 20% of capacity |35| Hiring Pipeline | Approved but unfilled positions | Note as future capacity |3637**Demand summary by initiative:**3839| Initiative | Priority | Phase | Start | End | Role Needed | FTE Required | Skills Required | Status |40|---|---|---|---|---|---|---|---|---|41| [Project A] | P1 | Execution | [Date] | [Date] | Sr. Engineer | 2.0 | Java, AWS, microservices | Confirmed |42| [Project B] | P1 | Planning | [Date] | [Date] | Business Analyst | 1.0 | Requirements, SQL | Confirmed |43| [Project C] | P2 | Execution | [Date] | [Date] | Data Scientist | 1.5 | Python, ML, statistics | Tentative |44| [Project D] | P3 | Initiation | [Date] | [Date] | Project Manager | 0.5 | Agile, stakeholder mgmt | Planned |45| BAU / Support | Ongoing | Steady-state | Ongoing | Ongoing | Multiple | [X] | Various | Fixed |46| **Total Demand** | | | | | | **[X] FTE** | | |4748### Step 2 — Assess Resource Supply4950Inventory available resources and their capabilities.5152| Resource | Role | Skills | Current Allocation | Available Capacity | Location | Cost Rate | Notes |53|---|---|---|---|---|---|---|---|54| [Person A] | Sr. Engineer | Java, AWS, K8s | 80% (Project X) | 20% | [Location] | $[X]/hr | Available from [Date] |55| [Person B] | Business Analyst | Requirements, SQL, Agile | 50% (Project Y) | 50% | [Location] | $[X]/hr | Part-time constraint |56| [Person C] | Data Scientist | Python, ML, NLP | 0% (between projects) | 100% | [Location] | $[X]/hr | Returning from leave [Date] |57| [Person D] | Project Manager | Agile, waterfall, PMO | 100% (Project Z) | 0% | [Location] | $[X]/hr | Rolls off [Date] |58| [Contractor Pool] | Various | Various | Variable | On-demand | [Location] | $[X]/hr | 2-week onboarding lead time |59| **Total Supply** | | | | **[X] FTE** | | | |6061**Skills inventory matrix:**6263| Skill | Required (FTE) | Available (FTE) | Gap (FTE) | Gap Severity |64|---|---|---|---|---|65| Java / Backend | [X] | [X] | [+/- X] | None / Moderate / Critical |66| Cloud (AWS/Azure/GCP) | [X] | [X] | [+/- X] | None / Moderate / Critical |67| Data Science / ML | [X] | [X] | [+/- X] | None / Moderate / Critical |68| Business Analysis | [X] | [X] | [+/- X] | None / Moderate / Critical |69| Project Management | [X] | [X] | [+/- X] | None / Moderate / Critical |70| UX / Design | [X] | [X] | [+/- X] | None / Moderate / Critical |71| QA / Testing | [X] | [X] | [+/- X] | None / Moderate / Critical |7273### Step 3 — Match Resources to Demand7475Create the allocation plan with skill-appropriate assignments.7677| Resource | Initiative | Role on Project | Allocation % | Start | End | Skill Match | Backup |78|---|---|---|---|---|---|---|---|79| [Person A] | Project A | Lead Engineer | 60% | [Date] | [Date] | Strong | [Person X] |80| [Person A] | BAU Support | On-call rotation | 20% | Ongoing | Ongoing | N/A | Rotational |81| [Person B] | Project B | Lead BA | 50% | [Date] | [Date] | Strong | [Person Y] |82| [Person C] | Project C | Data Scientist | 80% | [Date] | [Date] | Strong | Contractor |83| [Person D] | Project D | PM (after Project Z) | 50% | [Date] | [Date] | Moderate | [Person Z] |8485**Utilization targets and actuals:**8687| Role Category | Target Utilization | Planned Utilization | Buffer for Unplanned | Status |88|---|---|---|---|---|89| Engineering | 80% | [X]% | 20% | On target / Over / Under |90| Analysis | 80% | [X]% | 20% | On target / Over / Under |91| Management | 75% | [X]% | 25% | On target / Over / Under |92| Design | 80% | [X]% | 20% | On target / Over / Under |93| QA | 85% | [X]% | 15% | On target / Over / Under |9495### Step 4 — Resolve Conflicts and Gaps9697Address resource contention and shortfalls.9899| Conflict / Gap | Competing Demands | Resolution Options | Recommended Action | Escalation Needed |100|---|---|---|---|---|101| [Person A] double-booked at 120% in Q3 | Project A + Project E | 1. Delay Project E 2. Backfill with contractor 3. Reduce scope | Option 2: Hire contractor for Project E | No — within PM authority |102| No available Data Scientist for Project C | Project C needs 1.5 FTE, only 1.0 available | 1. Hire contractor 2. Delay project start 3. Upskill internal | Option 1: Contract resource for 6 months | Yes — budget approval needed |103| QA bottleneck in months 4-5 | 3 projects entering test phase simultaneously | 1. Stagger test phases 2. Add QA contractor 3. Automate testing | Options 1+3: Stagger and invest in automation | No — schedule adjustment |104| Key person risk on Project A | Single expert on critical technology | 1. Cross-train backup 2. Document knowledge 3. Pair programming | All three: Start cross-training immediately | No — proactive action |105106**Conflict resolution decision framework:**107108| Priority | Resolution Approach |109|---|---|110| P1 vs. P1 conflict | Escalate to portfolio governance for prioritization decision |111| P1 vs. P2 conflict | P1 initiative takes priority; delay or re-resource P2 |112| Skill gap (critical) | Engage contractors within 2 weeks; begin hiring process in parallel |113| Skill gap (moderate) | Cross-train existing team members; adjust timeline if needed |114| Over-allocation (short-term) | Accept temporarily if under 110% for less than 4 weeks; otherwise rebalance |115116### Step 5 — Forecast Future Capacity117118Project resource needs beyond the current planning window.119120| Planning Period | Demand Forecast (FTE) | Supply Forecast (FTE) | Net Position | Key Assumptions |121|---|---|---|---|---|122| Current quarter | [X] | [X] | [+/- X] | Based on confirmed plans |123| Next quarter | [X] | [X] | [+/- X] | Includes tentative projects |124| Q+2 | [X] | [X] | [+/- X] | Based on roadmap estimates |125| Q+3 | [X] | [X] | [+/- X] | Directional only |126127**Capacity actions needed:**128129| Action | Trigger | Timeline | Cost Impact | Owner |130|---|---|---|---|---|131| Open new headcount req | Confirmed gap >1 FTE for >3 months | Initiate now (3-month hiring cycle) | $[X] annual | Hiring Manager |132| Engage staff augmentation | Immediate gap or gap <3 months | 2-week activation | $[X]/month | Resource Manager |133| Cross-training program | Skill concentration risk >2 people | Start within 4 weeks | [X] hours investment | Team Lead |134| Contractor roll-off | Project completion or hire backfill | [Date] | Savings of $[X]/month | Resource Manager |135| Bench management | Utilization <60% for >4 weeks | Reassign within 2 weeks | Opportunity cost | Resource Manager |136137---138139## Output Format140141```markdown142# Resource Allocation Plan: [Program / Portfolio Name]143144**Planning Period:** [Start] to [End]145**Total Demand:** [X] FTE146**Total Supply:** [X] FTE147**Net Position:** [Surplus / Balanced / Deficit of X FTE]148**Prepared by:** [Name]149**Date:** [Date]150151---152153## 1. Executive Summary154[Key capacity position, critical gaps, conflicts, and recommended actions]155156## 2. Demand Analysis157[Initiative inventory, FTE requirements by role and skill, priority ranking]158159## 3. Supply Assessment160[Available resources, skills inventory, capacity by role]161162## 4. Allocation Plan163[Resource-to-initiative assignments with allocation percentages and timelines]164165## 5. Utilization Dashboard166[Target vs. planned utilization by role category]167168## 6. Conflicts and Resolutions169[Identified conflicts with recommended resolution and escalation needs]170171## 7. Capacity Forecast172[Forward-looking demand vs. supply with hiring and contracting actions]173174## 8. Risks and Mitigation175[Key person risks, skill concentration, and contingency plans]176```177178---179180## Quality Checklist181182- [ ] Every initiative has effort estimates broken down by role and skill requirement183- [ ] No resource is allocated above 100% without documented short-term exception approval184- [ ] Utilization targets are set at 75-85%, not 100% — buffer for unplanned work is included185- [ ] Skills inventory identifies gaps at the specific skill level, not just role level186- [ ] Conflicts are documented with resolution options and escalation recommendations187- [ ] Key person risks are identified for any skill held by fewer than 2 team members188- [ ] Forecast extends at least 2 quarters beyond the current planning window189- [ ] Contractor and hiring lead times are factored into gap-filling timelines190- [ ] BAU, support, and on-call commitments are accounted for before project allocation191- [ ] Plan includes a defined review cadence (bi-weekly recommended for active programs)192193---194195## Edge Cases196197| Scenario | How to Handle |198|---|---|199| Matrix organization with shared resources across departments | Establish clear allocation agreements with resource owners; use a central allocation tool; escalate conflicts to portfolio governance |200| Rapid scaling (hiring 10+ people in a quarter) | Factor in onboarding ramp (typically 1-3 months to full productivity); assign mentors; stagger start dates to avoid overwhelming the team |201| Key resource departure mid-project | Activate knowledge transfer immediately; assign backup from cross-training plan; assess contractor bridge if needed; update risk register |202| Seasonal demand spikes (e.g., year-end close, product launches) | Plan contractor bench in advance; cross-train for peak coverage; stagger non-critical work away from peak periods |203| Remote or distributed team across time zones | Account for timezone overlap in collaborative roles; document asynchronous handoff protocols; adjust utilization for communication overhead |204| Budget freeze preventing new hires or contractors | Reprioritize portfolio ruthlessly; defer lower-priority initiatives; optimize allocation of existing resources; document unmet demand for when budget reopens |