Resource Management Plan
A comprehensive framework for identifying, acquiring, and managing both human and physical resources throughout a project lifecycle.
- About this template
- Team Member Identification
- Staff Lifecycle (Acquisition & Release)
- Roles, Responsibilities, and Authority
- Team Management
- Physical Resources
- Quick Reference
§1 About this template
A project succeeds or fails based on the timely allocation of capable people and adequate physical infrastructure. This document establishes exactly how both will be sourced and governed.
The Resource Management Plan serves as the master blueprint for your project's resource lifecycle. It documents who is needed, what physical tools or materials are required, how they will be procured, and the terms of their eventual release. By standardising these parameters upfront, project managers reduce bottlenecks, clarify authority, and maintain strict control over budgetary forecasts.
Note on the Worked Example: This guide includes sample data drawn from a real-world scenario ("Mary’s Consulting - New Company Website") to demonstrate how theoretical categories are populated in practice.
§2 Team Member Identification
Before staff can be acquired, the project manager must define the functional roles, quantities, and necessary skill levels. This baseline allows functional managers to evaluate internal capacity versus the need for external procurement.
| Role | Number | Skill Level |
|---|---|---|
| Project Manager | 1 | Senior |
| Web Developer / Tech Lead | 1 | Senior |
| UX / Visual Designer | 1 | Mid-Senior |
| Content Strategist / Copywriter | 1 | Mid |
| Frontend Contractor | 1 | Mid (vendor) |
| Sponsor / Steering | 1 | Executive |
§3 Staff Lifecycle (Acquisition & Release)
Acquisition details how the project secures its human capital, whether through internal reallocation or external contracting. Release planning is equally critical; it ensures knowledge transfer is complete before returning staff to the wider organisational pool, preventing budget bleed on dormant tasks.
Staff Acquisition
The core team is sourced internally from existing firm headcount. Functional managers formally approve all allocations.
The Frontend contractor is sourced via the firm's approved vendor list, requiring the PM to sign the Statement of Work (SOW). All internal allocations must be confirmed prior to baseline approval (e.g., May 22, 2026).
Staff Release
Team members are released back to functional managers immediately as their final activity completes. Knowledge-transfer documents must be filed prior to release.
- Bill (UX): Released after accessibility audit (Oct).
- Christine (Content): Released after CMS training (Nov 24).
- Bob (Dev): Released after hypercare phase (Dec 10).
- Andrew (PM): Released at final project closeout (Dec 29).
§4 Roles, Responsibilities, and Authority
Clear demarcation of authority is vital. When decisions stall, an explicit authority matrix prevents scope creep and maintains project momentum. Each role must have defined responsibilities and, crucially, specific decision-making boundaries.
| Role | Responsibility | Authority |
|---|---|---|
| Project Manager (Andrew) | Plan, execute, monitor, and close the project; manage budget, schedule, scope, risks; primary liaison to sponsor. | Approve expenses up to $5,000; reallocate budget within 10% of categories; direct core team. |
| Sponsor (Mary, CEO) | Authorise project; approve charter, baselines, and changes; approve brand direction; provide funding. | Final approval on charter, scope/cost/schedule changes exceeding PM authority, brand decisions, project closure. |
| Web Developer (Bob) | Lead technical architecture, CMS configuration, frontend/backend development, CRM integration. | Owns technology stack decisions in consultation with PM; approves dev/staging/prod environment changes. |
| UX Designer (Bill) | Information architecture, wireframes, visual design, accessibility compliance. | Owns design system decisions; signs off on accessibility audit findings. |
| Content Strategist (Christine) | Content strategy, page copy, case studies, blog seed, consultant bio coordination. | Owns editorial standards; approves content from consultant submissions. |
| Marketing Lead | Internal stakeholder; approves brand fit, content tone, launch plan; owns site post-launch. | Approves content/brand alignment; final acceptance of marketing-related deliverables. |
Organisational Structure Mapping: In this framework, the Project Manager (Andrew) serves as the central node. The core execution team (Bob, Bill, Christine) and the internal stakeholder (Marketing Lead) all interface directly with the PM. The PM subsequently reports to the Project Sponsor (Mary, CEO) who sits at the apex of the project's governance hierarchy.
§5 Team Management
Resource management extends beyond mere allocation; it encompasses the active development, motivation, and upskilling of the team throughout the project lifecycle.
Training Requirements
Identify skill gaps before execution begins. In our example:
- Marketing team: 4-hour CMS training session at launch.
- UX Designer: WCAG 2.1 AA self-paced refresher prior to design.
- Content Strategist: Brand-voice workshop before drafting.
Rewards & Recognition
Link performance to structured outcomes:
- A $3,000 project completion bonus pool administered by the PM.
- Public recognition at all-hands meetings.
- Spot recognition during weekly status meetings.
- Named credit on the final platform for contributing consultants.
Team Development
Actively manage Tuckman’s stages (Forming → Storming → Norming → Performing). Establish a team charter in week one covering communication norms. Run weekly retrospectives during the build phase, supported by a hybrid co-location model (one in-person day per week).
§6 Physical Resources
Physical resources include the equipment, materials, facilities, and software licences required. Tracking physical assets ensures procurement lead times do not delay the critical path.
| Resource | Amount | Grade / Standard |
|---|---|---|
| Cloud hosting (dev/staging/prod) | 3 environments | Firm-approved cloud provider; standard tier |
| CMS licence (annual) | 1 seat group | Firm-approved CMS; supported tier |
| CI/CD pipeline access | 1 project | Firm-standard tooling |
| Stock imagery library | ~50 images | Royalty-free, commercial licence |
| Photography session | 1 day | External photographer; consultant headshots |
| WCAG 2.1 AA audit (3rd party) | 1 audit cycle | Accredited accessibility firm |
| Analytics & monitoring tools | 1 setup | Google Analytics, tag manager, uptime monitoring |
| Project tools (MS Project, etc.) | Existing licences | Firm-issued |
Resource Acquisition
Cloud and CMS resources are
Continue learning