Free Resource Plan Template — Excel Download

01 — What's Included

What's in the Template — Columns and Layout

The resource plan is a single-sheet Excel file in landscape orientation. The first five columns capture resource identity information; columns 6–17 form the 12-month allocation grid; the final two columns calculate totals and flag over-allocation.

Column(s)	Field	Notes
A	Role	The project role — not the job title. "Business Analyst", "Test Lead", "Integration Developer" rather than "Senior Associate" or "Technology Consultant".
B	Name	Named individual where confirmed. "TBC" or "To be resourced" where a gap exists — visible gap is better than false precision.
C	Type	Internal / Contractor / Vendor. Important for budget (contractors and vendors have a day rate; internal resources have an opportunity cost) and for procurement planning.
D	Department / Org	The home department or organisation for the resource. Helps identify line manager approval requirements and potential conflicts with other projects.
E	Day Rate / Cost	Optional. Day rate for contractors or vendor resources. Leave blank for internal resources unless the organisation charges out internal time.
F–Q	Month 1–12 (% allocation)	The percentage of the resource's working time committed to this project in each month. 100% = full-time. 50% = half their time. Conditional formatting: ≤80% green, 81–100% amber, >100% red (over-allocated).
R	Total Effort (days)	Auto-calculated: sum of monthly allocations converted to person-days. Useful for budget and capacity planning.
S	Notes / Constraints	Any availability constraints: planned leave, part-time working, shared across multiple projects, onboarding time required, security clearance needed.

The Gap Identification Row

Below the 20 resource rows, a Gaps / TBC row highlights months where the plan shows "TBC" resources — roles required but not yet filled. This row is your recruitment and resourcing radar: any month with a TBC entry needs attention before work is scheduled to begin in that period. A plan that shows all roles confirmed is not necessarily accurate — it is only accurate if every "TBC" has been replaced with a real name.

💡

Name every resource — or name the gap. A resource plan that lists roles without names is a wish list, not a plan. For every "TBC" entry, the PM should know: who needs to approve the resource, what the lead time is for sourcing them, and what the plan is if they are not available. A confirmed resource plan is one where every row has a name and every name has confirmed their availability for the periods shown.

02 — Allocation Guide

Resource Allocation — What the Percentages Mean

The most common resource planning mistake is allocating people at 100% and then wondering why they are constantly behind. People are not machines. A realistic working allocation account for meetings, context-switching, administrative tasks and the inevitable interruptions of organisational life.

>100%

Over-allocated

Impossible. Something will slip. Either the person is double-booked or the schedule is wrong.

80–100%

High — caution

Leaves no buffer for meetings, admin, unexpected issues. Risk of burnout and late delivery.

50–80%

Healthy range

Realistic for most project roles. Allows for organisational overhead and unexpected work.

<50%

Part-time

Viable for advisory or review roles. Context-switching costs increase at lower allocations.

The 70% Rule for Project Work

A widely used rule of thumb: a person allocated at 100% to a project will realistically deliver approximately 70% of a full-time equivalent of project output. The remaining 30% is consumed by meetings (internal and organisational), email and communication, administrative tasks, interruptions and the cognitive cost of context-switching between tasks.

This means a four-person team at 100% allocation should be planned as approximately 2.8 FTE of productive project output. If your schedule requires four FTE of work, you need approximately 5–6 people at 100%, or you need to extend the timeline. Building this adjustment into the resource plan from the start is more accurate than discovering the gap mid-project.

Example Resource Allocation — 6-Month View

Role / Name	Apr	May	Jun	Jul	Aug	Sep
PM — S. Ahmed	60%	60%	80%	70%	70%	50%
BA — J. Patel	80%	80%	60%	60%	—	—
Dev Lead — TBC	TBC	TBC	100%	120%	100%	80%
Test Lead — M. Khan	—	—	50%	80%	80%	60%

This view immediately shows two issues: the Dev Lead role is not yet filled for April–May (needs urgent action), and the same role is over-allocated at 120% in July (schedule needs adjusting). The Test Lead has no allocation in April–May — check whether this is intentional or a planning gap.

03 — Common Mistakes

Five Resource Planning Mistakes That Cause Project Delays

Resource planning errors are responsible for more project delays than scope changes, technical problems and sponsor interference combined. These five mistakes appear on almost every project that runs late.

⏰

Planning at 100% allocation

Scheduling every person at 100% assumes they will spend every working minute on project tasks. Meetings, email, admin and context-switching consume at least 20–30% of every knowledge worker's day.

Fix: Plan at 70–80% for full-time resources. Build the buffer in the plan, not in people's weekends.

👥

Treating shared resources as fully available

A resource shared across three projects is not 33% available to each — they are 33% available but their context-switching cost means each project gets less than 33% of productive output.

Fix: Negotiate dedicated blocks of time rather than percentage splits. A person working on your project two days a week delivers more than one spread across five days in 20% slices.

📅

Not accounting for ramp-up time

A new team member allocated at 100% from Day 1 will not deliver 100% output on Day 1. Onboarding, environment setup, knowledge transfer and familiarisation take time — typically 2–4 weeks for an experienced hire on a complex project.

Fix: Show new resources at 25–50% allocation for their first 2–4 weeks and plan accordingly.

🏖️

Not accounting for planned leave

A 12-month project will see every team member take at least 20–25 days of annual leave. If your schedule does not account for this, every summer and holiday period will generate "unexpected" delays.

Fix: Add a Notes column entry for planned leave periods. Reduce the allocation % for those months or build explicit leave buffers into the schedule.

🔍

Leaving TBC gaps unresolved

TBC entries in the resource plan are risks — not placeholders. Every month that starts with a TBC resource is a month that may be delayed. TBC entries are often left unresolved until the project is already in trouble.

Fix: Every TBC should have a named action owner, a resolution date and an escalation path. Treat unfilled roles with the same urgency as open Critical issues.

04 — FAQ

Resource Plan — 4 Common Questions

A resource plan identifies all human and non-human resources needed to deliver a project, maps when each is needed and confirms available capacity. It documents the role, named person, effort allocation percentage and availability across the project timeline. Resource planning is one of the most common sources of project failure — most schedule delays trace back to conflicts, unavailability or gaps not identified during planning. In PMBOK, resource planning is part of the Project Resource Management knowledge area.

Resource loading is assigning resources to tasks and calculating how much capacity is consumed each period — identifying over and under-allocation. Resource levelling resolves over-allocations by adjusting the schedule: moving tasks, extending durations or adding resources so no resource exceeds 100% capacity. Levelling typically extends the project schedule. On the PMP exam, both are tools used in the Develop Schedule and Control Schedule processes. The resource plan template supports resource loading — use it alongside your scheduling tool to identify where levelling is needed.

Start from the WBS — decompose the project into tasks, estimate the effort required for each task, then map those estimates to the roles needed. Three-point estimation (optimistic, most likely, pessimistic) reduces systematic underestimation. Historical data from similar projects is the most reliable basis. Common mistakes: estimating at 100% allocation when 70–80% is realistic after overhead, and not including time for rework, reviews and knowledge transfer. Always add the 70% productivity adjustment: plan for what people will actually deliver, not what they are theoretically capable of.

A resource plan should include: a register of each role and named resource; their effort allocation percentage; their availability period; which project phases or tasks they are assigned to; a capacity summary showing total effort by period; and a gap analysis identifying months where required capacity exceeds confirmed availability. It should also note constraints — part-time availability, shared resources, planned absences, onboarding time and security clearance requirements. The RACI matrix complements the resource plan by mapping roles to specific decisions and deliverables.

Free Resource Plan Template Excel Download