How to Create a Resource Plan: A Step-by-Step Guide for Project Managers

how to create a resource plan is a key topic in modern project management and teamwork. Every project starts with a promise about people: who will do the work, how much of their time it will take, and when they will be free to do it. Projects fall apart precisely where that promise is vague. The marketing team says it can deliver in two weeks, the designer is booked on another project, and the deadline arrives with half the work undone. A resource plan is the document that removes the vagueness — it lists the people, equipment, budget, and time the project needs, and then schedules that capacity against the work. This guide walks you through creating a resource plan in seven steps, with a worked example, real tools and their trade-offs, and the mistakes that silently destroy otherwise good plans.

Quick Answer: How Do You Create a Resource Plan?

Create a resource plan by defining the project’s work, estimating effort in hours per task, identifying the people and equipment required, checking each person’s availability, scheduling the work across the timeline, and resolving overallocations. The seven-step process ends with a weekly review that keeps the plan aligned with reality. The plan’s core output is a schedule that shows who is doing what, when, and for how many hours — with no person committed beyond their capacity.

The nuance: a resource plan is only as good as its estimates and its maintenance. A beautifully formatted plan built on guessed effort numbers fails the same way as no plan. Build it on data, keep it simple, and update it every time scope, people, or dates change.

What Is a Resource Plan?

A resource plan is a document (or view) that connects the project’s required work to the resources needed to complete it — people, equipment, facilities, and budget — across the project timeline. It answers three questions at any point in the project:

1. What work needs to happen? (the task breakdown)
2. What or who is required for each piece of work? (resource requirements)
3. Are those resources available when the work is scheduled? (capacity check)

A good resource plan is more than a staffing chart. It includes effort estimates, allocation percentages, availability, and a view of over- or under-allocation. It is the link between the project schedule and the people who make the schedule real.

Resource planning operates on three horizons, each with a different purpose:

• Short term (weeks): who is doing what next — the operational schedule.
• Mid term (1–3 months): can the team absorb the upcoming work — the tactical capacity check.
• Long term (quarters+): do we need to hire, contract, or train — the strategic plan.

Most project managers live in the short and mid term, but a plan that never looks ahead is a plan that is always reacting.

Step-by-Step: How to Create a Resource Plan

Step 1 — Define the Work and Break It Down

Start with the project scope and a work breakdown structure (WBS): decompose the deliverables into tasks and sub-tasks small enough to estimate. A task should be estimable in hours or days by a competent person. If you cannot estimate it, it is not broken down enough.

For a website redesign, this might produce 40–80 tasks across design, development, content, and QA. Do not skip this step — every later step depends on knowing exactly what the work is.

Step 2 — Estimate Effort for Each Task

For every task, estimate the effort required in hours (or days), independently of who will do it and when. Two estimation approaches:

• Bottom-up: sum estimates per task, then validate the total against experience.
• Historical-based: use effort from past similar projects — the most reliable method when records exist.

Record assumptions. A task estimated at 40 hours by one person may be estimated at 24 by a senior who has done it five times. The estimate should reflect the skill level you plan to assign. When in doubt, plan with a range and add a buffer — 10–20% on top of the total is a practical starting point for planning purposes.

Step 3 — Identify Required Resources and Skills

List what each task needs: the role (e.g., senior backend developer, motion designer), the skill, and any special equipment or facilities. Separate “who can do it” from “who is actually available.” This is where skills matrices earn their keep: knowing that only two people in the company can run the final security review changes the plan before it is drawn.

Also decide resource mix: full-time staff, part-time, contractors, and equipment. A balanced mix — not everyone senior, not everyone junior — gives the plan flexibility and keeps specialists from being wasted on routine work.

Step 4 — Check Availability Before Assigning Names

This is the step most plans get wrong. Before assigning a person, check their available hours for each week of the project, accounting for:

• Existing project commitments (other projects they are already on).
• Leave and holidays.
• Recurring commitments (meetings, support rota, admin).
• Realistic utilization — plan a person at 75–85% of their contract hours, not 100%.

Availability is the gatekeeper. If a person has 20 available hours in a week and the task needs 30, the plan is already broken at this step — fix it here, not in week three of execution.

Step 5 — Schedule and Allocate the Work

Now assign tasks to named people with start and end dates, matching the estimated effort to their available hours week by week. Express allocation as a percentage of capacity or as hours per week — “Mina is 60% allocated to this project for three weeks” is actionable; “Mina helps out” is not.

The output is a resource schedule: per person, per week, which tasks and how many hours. This is the view the whole team works from.

Step 6 — Balance Overallocation and Under-allocation

Compare scheduled hours to available hours for every person, every week. Expect mismatches and fix them deliberately:

• Resource leveling adjusts the project schedule — pushing tasks or the whole project later — to remove overallocations when resources are the constraint.
• Resource smoothing keeps the project dates fixed and shifts tasks within their float to even out workload, accepting that the peak may remain if it cannot be moved.

Beyond these, options include adding a contractor, reprioritizing lower-value work out of the window, or renegotiating scope. Whatever you choose, the plan is not finished until no person exceeds their available hours.

Step 7 — Review and Maintain Weekly

A resource plan is a living document. Each week: update actual hours against estimates, absorb leave and absences, reflect scope changes, and roll the plan forward. The discipline of the weekly review matters more than the tool — a plan nobody updates is a plan nobody can trust. Track the variance between planned and actual effort; recurring variance is the signal that your estimates (or your plan) need fixing.

What Goes Into a Resource Plan: A Handy Checklist

Tools for Creating a Resource Plan

The tool you choose shapes the plan’s quality. Here are real options with their trade-offs:

Spreadsheets — Excel or Google Sheets remain the most common resource planning tool, and for small teams they genuinely work.

• Pros: zero cost, universally understood, fully flexible, no learning curve.
• Cons: no live availability, manual updates, no automated overload warnings, version chaos, and a single error is invisible until a deadline is missed.
• Trade-off: a spreadsheet with strict weekly discipline beats an expensive tool nobody uses. But it scales poorly — past about 10–15 people or several projects, the maintenance cost is higher than the tool budget.
• Best for: small, stable teams that can commit to a weekly update ritual.

Microsoft Project — the classic enterprise scheduling tool with resource sheets, calendars, and leveling.

• Pros: powerful scheduling and leveling, resource calendars, familiar to certified PMs, strong reporting.
• Cons: dated interface in places, steep learning curve, overkill for small projects, and collaboration is clunky compared with modern cloud tools.
• Trade-off: if your PMO standardizes on Microsoft, it is a serious engine for complex schedules; for a fast-moving team, it is heavy and slow to share.
• Best for: large organizations with trained planners running complex, resource-intensive projects.

Float — a resource scheduling tool focused on people’s availability, bookings, and workload.

• Pros: clean per-person weekly view, live leave tracking, drag-and-drop scheduling, over-allocation warnings.
• Cons: light on project task management; no deep financial or skills modeling; per-user cost adds up.
• Trade-off: excellent at the scheduling half of a resource plan, but you will keep tasks and finances elsewhere.
• Best for: agencies and teams whose main planning problem is “who is free this week.”

Resource Guru — a simple booking calendar for people and equipment with utilization reporting.

• Pros: fast adoption, availability at a glance, leave built in, cheap entry point.
• Cons: limited forecasting and analytics; project depth is minimal.
• Trade-off: the easiest step up from a spreadsheet, but it solves scheduling, not the strategic capacity question.
• Best for: small consultancies that need a clean live booking calendar.

Saviom — an enterprise resource management suite covering demand forecasting, capacity planning, and allocation.

• Pros: enterprise-wide capacity vs demand views, heatmaps, skill-based planning, strong for large workforces.
• Cons: significant setup and cost; more than most small teams need; requires dedicated administration.
• Trade-off: the deepest resource planning capability on the market, at enterprise complexity.
• Best for: large organizations and PMOs that plan resources across the whole company.

Mosaic — a resource management platform with demand forecasting, scenario planning, and utilization analytics.

• Pros: strong what-if scenario modeling, skills-based allocation, utilization dashboards.
• Cons: built for scaling teams; cost and learning curve reflect that.
• Trade-off: the scenario planning helps answer “what if we hire one more?” before you commit; heavier than needed for a 5-person schedule.
• Best for: scaling professional services firms with real forecasting needs.

Three Real-World Scenarios

Scenario 1 — The launch plan saved by checking availability. A product team planned a launch assuming three engineers were full-time for six weeks. Checking availability first, the manager found one engineer was 50% committed to a data migration and another had two weeks of leave booked. The launch’s realistic capacity was 62% of what the original plan assumed. The team pulled a contractor for the migration, shifted the launch by one week, and re-sequenced tasks so the remaining engineer’s capacity was used fully. The launch shipped on the new date; without the availability check, it would have slipped by a month.

Scenario 2 — The agency that fixed overallocation with leveling. An agency’s resource plan showed its lead designer at 140% allocation for a six-week client project — the plan had simply added a new project on top of existing ones. Using resource leveling, the agency pushed the second project’s start by two weeks, and the designer’s load dropped to 92%. The client was told about the delay up front, the project finished on its new schedule, and the designer’s hours stayed sustainable. The fix was timing, not adding headcount.

Scenario 3 — The PMO that stopped guessing estimates. A services firm built its resource plans on gut-feel effort estimates and missed deadlines chronically. It introduced a rule: every task type had a historical estimate from the last three similar projects. Within two quarters, forecast vs actual variance shrank from around 30% to below 10%, and the resource plans stopped needing weekly rescue. The workflow was identical — the estimates were not. That single change made every downstream step of the plan reliable.

Common Mistakes When Creating a Resource Plan

Assigning people before estimating effort. Naming resources first locks in a schedule that was never tested against hours. Estimate the work, then find the people.

Ignoring availability. A plan that does not subtract existing commitments, leave, and meetings is a wish list. Always plan against available hours, not contract hours.

Planning everyone at 100% utilization. There is no room for meetings, sick days, rework, or scope changes. Sustainable plans keep people at 75–85%.

Guessing effort. Unvalidated estimates propagate through the entire plan. Use historical data, get the estimators involved, and record assumptions.

Forgetting non-project work. Internal initiatives, support, and admin consume the same hours as client work. If the plan ignores them, it is wrong.

Never updating the plan. A plan created once and never touched drifts into fiction within weeks. Weekly reviews are part of the plan, not optional maintenance.

Hiding risk. The one person who holds the only copy of a critical skill, the estimated-before-signed-off scope, the contractor who might leave — surface these as plan risks, not surprises.

Making it too complex. A plan nobody can read gets ignored. Keep the essential view simple: per person, per week, how many hours, on what work, with the overloads flagged.

Know This Before You Choose

Before you build (or buy) a resource planning process, answer these honestly:

• Do I have historical effort data I can plan from, or will every estimate be a first guess?
• Do I know each person’s true available hours for the planning window, including leave, meetings, and other projects?
• Can I see overallocation at a glance, or would I only notice it when a deadline is missed?
• Who owns updating the plan weekly, and do they have the authority to act on the overloads it reveals?
• Is my team’s plan built to 100% utilization, or does it leave a buffer?
• Does the plan include non-project work, or only “real” project tasks?
• If a key person takes leave tomorrow, does the plan show me what breaks?

When a Unified Workspace Makes Sense

Resource planning has a data problem: it depends on the task list, the schedule, the leave calendar, and the workload view being consistent with each other. When those live in four different tools, the resource plan is a manual photocopy of reality, already stale the day it is drawn. A platform that holds tasks, timelines, and workloads in one place turns the resource plan into a view of the actual plan rather than a separate artifact.

One such platform is Doitify, an all-in-one platform for project management, team management, and goal achievement — tasks and sub-tasks with owners and due dates, kanban boards, calendars, Gantt charts, workload and resource management, and project documents in one workspace. Because the schedule and the workload live together, allocation percentages and overload warnings stay connected to the real plan. To be transparent: Doitify is our product, which is why we know its capabilities from the inside. The honest guidance above still applies, though: the plan’s quality comes from effort data and weekly discipline, not from the logo on the tool. Start with a spreadsheet if your team is small and stable — and move to a unified workspace when the resource plan has to stay live across many people and projects.

Conclusion

A resource plan turns a vague promise about people into a schedule that can be tested: the work is broken down, effort is estimated, resources are named, availability is checked, and overallocations are resolved before they become missed deadlines. Build it in seven steps, plan people at 75–85% of their real available hours, and review it weekly. The two ingredients that separate a working plan from a beautiful one are honest estimates and regular maintenance — both are disciplines, not tools. Start simple, use historical effort where you can, and escalate to software when the plan must stay live across many projects. For a broader look at how project management tools support planning and execution, see our project management overview.