Resource Management Plan: [Project name]

Plan for the people, skills and equipment the project needs: requirements by role and period, team structure, RACI, acquisition and onboarding, capacity against demand, training and release. Based on common project management practice. Replace every [bracketed] value and every row marked Example.

1. Approach

Resource demand was estimated from the work packages in [WBS-001] and the activity durations in [SCH-001]. Internal staff are allocated by their line managers through [resource management process]; external staff are contracted through procurement. The project manager directs day-to-day work; line managers keep responsibility for performance reviews and well-being.

2. Resource requirements by role and period

Demand in full-time equivalents (FTE) by month:

Non-staff resources:

3. Team structure

The project team is organised by workstream.

4. RACI matrix

Responsibilities for key deliverables and decisions:

5. Acquisition and onboarding

Resources are acquired according to the plan below.

Onboarding checklist for each new team member:

• Access to repository, issue tracker, chat channel and test environments, approved by the system owners
• Briefing on objectives, plan, ways of working and the RAID log
• Security and data protection induction where personal data is handled
• Buddy assigned for the first two weeks

6. Capacity versus demand

Committed capacity is compared with demand per month; negative values are gaps.

Utilisation is checked to avoid planning people above sustainable load:

$\text{Utilisation} = \frac{\text{Allocated hours}}{\text{Available hours}} \times 100\%, \quad \text{target} \le 85\%$

7. Training and development

Skills gaps in the project team are closed as follows.

8. Team management and recognition

The project manager provides written performance input to line managers at the end of each stage and when a team member leaves the project. Workload conflicts are raised at the weekly project board; unresolved conflicts follow the escalation path in the communication plan. Contributions are recognised at stage gates and in the closure report.

9. Release plan

Resources are released when their work is complete and knowledge has been handed over.

Standard and licence note

Based on common project management practice for resource planning, responsibility assignment (RACI) and team management. This template is original text written for this collection. Template licence: MIT.