Work Breakdown Structure Template: Free Excel, Word & PDF Download

1. Define your top-level work packages. In the first WP ID column, number the major phases or components of your project (1, 2, 3) and name each one. The sample uses phases like environment setup, analysis, data migration, and production cutover. Together, these should cover 100% of the project scope, with no overlaps.
2. Break each one into smaller work packages. Use the second WP ID column to add sub-packages under each phase (1.1, 1.2, 2.1). A good work package is small enough to estimate and assign, typically between 8 and 80 hours of effort. If one is bigger, split it.
3. Add the tasks for each work package. In the Task column, describe the actual work in one clear action, such as “Install DB server” or “Run complete data migration on test environment.” If a work package needs several tasks, give each one its own row.
4. Assign an owner and a deliverable. Put one responsible person on each row, even if several people help. Then link the row to the deliverable it produces. The sample uses short codes like “D12 – Detailed technical design,” so everyone can see which output each task feeds into.
5. Map effort across the timeline. Enter the estimated effort for each task in the time-period columns where the work will happen. Spreading effort across periods, instead of using one total, shows when work actually lands and how long each task runs.
6. Mark milestones and the critical path. Add a Milestone row wherever a key checkpoint falls, like a design sign-off, a completed UAT, or a go-live, and number them in order (MS 1, MS 2). Flag the sequence of work that can’t slip without delaying the whole project as your Critical Path. This is where to focus attention.
7. Check resource load before you commit. The summary at the bottom of the sheet shows how much work each person has in each period. Look for spikes where someone is overbooked, gaps where work is missing, and tasks that depend on something unfinished. Then rebalance before the plan goes to stakeholders. Easily forgotten items include testing, approvals, handover, and project closure.

Then use your project management tools to turn the WBS into assigned tasks, timelines, and status updates.

Why Use a WBS Template?

Use this WBS template to turn a complex project into clear deliverables, work packages, owners, and timelines.

It helps you:

• Break down scope faster: Start with a ready-made structure instead of building your WBS from scratch.
• Organize work in one place: Map deliverables, tasks, subtasks, owners, outputs, effort estimates, and deadlines.
• Spot planning gaps early: Review dependencies, missing owners, unclear outputs, and potential resource conflicts before work begins.
• Create a shared reference: Give your team and stakeholders one place to understand what needs to happen, who owns it, and how the work connects.

For more inspiration, see these work breakdown structure examples.

Author's Tip

If you need more templates for your project management processes, you can find more in our project management templates roundup.

Join For More Project Management Templates

Want access to 100+ PM templates? Join our membership community and get access to our templates, samples, examples, and connect with 100s of other digital project managers in Slack.