
Work Breakdown Structure
Docs + Word6 pages
Free
A work breakdown structure lists everything a project must deliver, split into pieces small enough to estimate, assign and track. Many plans fail because they are organized by phase, so scope gaps hide between activities. This eight-page Google Docs template organizes the work by deliverable: a layered tree, the method for building it, an article on the envelope, practical checks, the external works flow and a guide page for replacing the sample.
The sample is a fictional Dovecote Works depot build with six deliverables and 4,200 estimated hours in total, from substructure to external works. Replace the project name, branches, IDs and hours with your own, then confirm every branch sums to its parent before the plan is baselined.
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
Name the project as the top level, then list the deliverables as level 2 branches.
Replace the sample IDs and hours, and confirm each branch sums to its parent.
Write a dictionary line for every package with its owner and acceptance test.
Delete the guide page, then share the plan with your estimators or present it to the sponsor.
No. The WBS is organized by deliverable, while the programme sequences the same packages over time. Keep one numbering scheme, so the schedule and the cost plan can link to the same IDs.
No. Dovecote Works, its depot project, the packages, owners and every hour or dollar figure are fictional sample data. Replace them with your own before you use the plan on a live job.
Three to five levels is typical. Go deeper only where a package is still too large to estimate, and stop when each one can be estimated in under two weeks.

Docs + Word6 pages
Free
Docs + Word5 pages
Free
Slides + PowerPoint11 slides
Free