Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 17 tasks across 6 phases, about 6 weeks from start to finish with the parallel work shown.
What's in the template
| Phase | Task | Owner | Duration | Starts | Depends on |
|---|---|---|---|---|---|
| Plan | Kickoff and scope | Project manager | 2 days | Day 1 | Nothing (starts first) |
| Plan | Resource plan and availability check | Project manager | 2 days | Day 3 | Kickoff and scope |
| Design | User research interviews | Designer | 5 days | Day 5 | Resource plan and availability check |
| Design | Wireframes | Designer | 5 days | Day 10 | User research interviews |
| Design | Visual design | Designer | 6 days | Day 15 | Wireframes |
| Build | Technical architecture | Lead developer | 4 days | Day 5 | Resource plan and availability check |
| Build | Back end and data model | Lead developer | 10 days | Day 9 | Technical architecture |
| Build | Front-end screens | Developer | 10 days | Day 15 | Wireframes, Technical architecture |
| Build | Integrations | Lead developer | 6 days | Day 19 | Back end and data model |
| Build | Apply visual design | Developer | 4 days | Day 25 | Visual design, Front-end screens |
| Content | Help content and copy | Content writer | 6 days | Day 15 | Wireframes |
| Test | Test plan and test cases | QA analyst | 4 days | Day 15 | Wireframes |
| Test | System testing | QA analyst | 6 days | Day 29 | Integrations, Apply visual design, Test plan and test cases |
| Test | Fix defects | Lead developer | 4 days | Day 35 | System testing |
| Launch | User acceptance testing | Project manager | 4 days | Day 39 | Fix defects |
| Launch | Go-live | Milestone | Day 43 | User acceptance testing, Help content and copy | |
| Launch | Handover and release the team | Project manager | 2 days | Day 43 | Go-live |
Durations are examples to replace with your own estimates, not benchmarks. Some work runs in parallel, so the plan takes 44 days instead of the 80 it would take one task at a time. The 11 darker bars are the critical path: a day lost on any of them moves the finish date.
About this resource plan
Most project schedules are built as if every person could work on unlimited tasks at the same time. The links say design must finish before build starts, but nothing says the same developer cannot build the back end and the integrations in the same week. A resource plan adds that second question to every task: who is doing it, and are they free?
This template is a six-role delivery project (project manager, designer, lead developer, developer, content writer and QA analyst) laid out as a Gantt chart with an owner on every task. The work has already been levelled: where one person has two tasks, the second waits for the first, so no role is on two bars at the same time, and the 44-day finish is one the team can staff.
Rename the roles to the people on your team, change the durations to their estimates, and colour the chart by owner to see each person's work as one colour. If an edit puts the same owner on two overlapping tasks, the editor shows a schedule conflict and offers to move the later task, give it to someone else or shorten it.
Who it's for: Project managers, delivery leads and agency owners who need a schedule that respects who is available, not just which task comes first.
How to use it
- Use this template. Click Use this template. The plan opens in the editor with every task, link and owner in place, and no sign-up is needed to start.
- Replace the roles with your people. Change each owner from a role to a name. If two roles are the same person on your team, give both sets of tasks the same owner and the editor will flag every place they overlap.
- Colour the chart by owner. Switch the chart colour to Owner. Each person's work becomes one colour, so gaps (someone waiting) and stacks (someone overloaded) are visible at a glance.
- Resolve conflicts, then share. Where the editor reports a schedule conflict, pick a fix: move the later task, reassign it or shorten it. Then share a read-only link so each person can see when they are needed.
Task links versus resource links
Two kinds of link hold this plan together. Logic links exist because of the work itself: front-end screens cannot start until there are wireframes to build from. Resource links exist only because the same person does both tasks: the lead developer builds the back end and then the integrations, not because integrations need the back end finished, but because there is one lead developer. In this template, Integrations waits for Back end and data model for both reasons: it uses the data model, and the same lead developer builds both.
The difference matters when you add people. Remove a resource link by giving the second task to someone else and the plan gets shorter. Try to remove a logic link the same way and nothing improves, because the work genuinely has to wait. A good resource plan makes it obvious which is which, so nobody suggests hiring to fix a delay that is really a dependency.
Reading the plan: who is critical and who has room
The critical path runs from kickoff through the designer's research and wireframes, the developer's front-end screens and visual design pass, then system testing, defect fixes, acceptance testing and go-live. The designer is on the critical path through research and wireframes, and the developer after that, so those are the two people whose sick days move the launch. Visual design has four days of slack.
The lead developer's chain (architecture, back end, integrations) has four days of slack, and help content has more than three weeks of it. That spare time is useful: the content writer can take on other work, and the lead developer can absorb a small overrun without moving go-live. Slack is capacity you can plan with, which is the point of resource planning.
How detailed should a resource plan be?
Plan people at the level you can check. Booking each person on whole tasks, one at a time, is enough for most project teams and keeps the plan readable. Splitting people into percentages (half a designer here, a quarter there) looks precise but is rarely how work happens, and it hides context switching.
If someone is genuinely shared with another project, block their time on this plan as a task ("Designer on other project") rather than assuming they are free. It keeps the dates honest and shows the cost of the shared time to whoever decides it.
Planning tips
- Check availability before you commit to dates: holidays, other projects and support rotations are the usual reasons a levelled plan still slips.
- Use roles in the template stage and names once people are assigned. A role can be in two places at once on paper; a person cannot.
- Keep one owner per task. Pair work is fine, but the owner is the one who updates the bar.
- Look at slack per person, not just per task. The person with the most slack is your buffer when a critical task runs late.
- Re-level after every big change. Moving one task often creates a conflict two weeks later on someone else's bar.
Frequently asked questions
- What is a resource planning template?
- It is a project schedule where every task has an owner, so you can check that no one is booked on two things at once. This one is a Gantt chart with six roles, task links and an owner on every bar, already levelled so no role overlaps itself.
- What is the difference between resource planning and resource levelling?
- Resource planning decides who does each task and when they are available. Resource levelling is the step that fixes overloads by delaying or reassigning work so no one is double-booked. This template shows the result after levelling: the lead developer and the designer each work through their tasks one at a time.
- Does gantt-chart.io warn me when someone is double-booked?
- Yes. When two tasks with the same owner overlap, the editor shows a schedule conflict naming the person and the tasks, and offers three fixes: move the later task, give it to someone else or shorten it. You choose; nothing is rescheduled silently.
- Can I use this resource plan in Excel?
- Yes. Download CSV gives you every task with its owner, start date, end date, phase and dependencies, which opens in Excel or Google Sheets.
- Is this resource planning template free?
- Yes. Opening and editing it in the browser is free with no sign-up, and the CSV download on this page is free. A free account keeps one saved project.
Related templates and guides
- Project Plan Gantt chart template
- Work Breakdown Structure (WBS) Gantt chart template
- Milestone Chart Gantt chart template
- Implementation Plan Gantt chart template
- Smartsheet alternative
- Free Gantt chart maker, no sign-up
- Critical path calculator
- Free timeline templates
- All Gantt chart templates
- Gantt chart examples
- How to make a Gantt chart
- Excel Gantt chart template
The free plan saves one project. Downloads from the editor (PDF, CSV) and more projects are on Solo, $12/month.