Build a team resource allocation plan

Map team capacity against project demands to prevent overallocation and identify gaps before they become crises.

Workflow · Project ManagementRole · Project Manager●●● IntermediateUpdated 2026-07-31

The prompt

Copy and customize

prompt.txt
**Role:** You are a Project Manager building a resource allocation plan for project {project_name}.

**Context:**
Overallocated teams deliver late and burn out. You need to match the right skills to the right tasks at the right time. The project runs from {start_date} to {end_date} and involves {team_members_and_capacity}.

**Task:**
Analyze the demand from the project workplan, map it against available capacity, flag conflicts, and propose resolutions for any gaps. Consider both availability (time) and capability (skills).

**Input Available:**
- {project_name}: Project name
- {workplan_tasks}: Key project tasks with estimated effort (hours/days) and timeline
- {team_members_and_capacity}: Each team member with their available hours per week and key skills
- {parallel_projects}: Other projects competing for the same people
- {critical_skills}: Skills that are hardest to replace
- {budget_for_external}: Whether external contractors or tools can be used

**Output Format:**
1. Capacity vs. demand table by person by week
2. Overallocation flags: Who | Week | Overallocated by | Resolution options
3. Skill gap analysis: Skill needed | Who has it | Backup option
4. Critical path people: Individuals whose absence would delay the project
5. Recommendations: Prioritization, sequencing adjustments, or hiring/contractor recommendations
6. Contingency plan if a key resource becomes unavailable

**Guardrails & Quality Control:**
- Alert clearly if any team member exceeds 80% allocation — that is the practical overload threshold
- Do not assume people can work more than their stated available hours
- Account for meeting overhead (typically 20–30% of working time)
- Flag if critical skills exist in only one person — single points of failure are high risk

How to use

Run this prompt in four steps

  1. 1Gather actual availability from team members directly, not from org charts.
  2. 2Update weekly as the project progresses — capacity changes frequently.
  3. 3Share the overallocation flags with team leads for joint resolution.
  4. 4Review after each phase gate to rebalance for the next phase.

When to use

When to use this prompt

Use at project planning and revisit monthly. Critical for any project where people are shared across multiple initiatives.

Limitations · Worth knowing

This prompt has limitations you must understand.

AI works with the data you provide. If team members under-report other commitments, the plan will be inaccurate. Validate with team leads.