Guide
How to Build a Product Breakdown Structure (PBS)
A practical guide for engineering project managers: how to decompose your product into a bill-of-materials-style structure with costs, delivery dates, and links to your schedule.
A Product Breakdown Structure (PBS) is a hierarchical decomposition of everything the project will produce or procure — assemblies, sub-systems, components, and purchased parts. Where a Work Breakdown Structure (WBS) answers "what work do we need to do?", a PBS answers "what are we building, and what does it cost?"
For complex engineering projects with significant hardware content, the PBS is often where the bill of materials, make/buy decisions, supplier delivery dates, and cost-based earned value all come together — separately from, but linked to, the task schedule in the WBS.
Building your PBS, step by step
1. List what the project must produce, not how
Start from the end product and break it down into the physical assemblies, sub-systems, and components it consists of — for example 'Enclosure', 'Mainboard', 'Power supply', 'Wiring harness'. Unlike a WBS, a PBS describes things, not activities — there are no verbs in a PBS.
2. Decompose down to orderable or buildable items
Keep breaking each assembly down into its sub-assemblies and parts until you reach a level where each item is either something you'll manufacture/assemble in-house, or something you'll purchase as a single line item from a supplier.
3. Mark each leaf as 'make' or 'buy'
For every leaf node, decide whether it's produced internally (make) or sourced externally (buy). This single flag drives how the item shows up later: 'make' items typically need a linked WBS work package to produce them; 'buy' items mainly need a cost, a supplier, and a delivery date.
4. Add quantity, unit cost, and currency
Each leaf gets a quantity and a unit cost in its own currency (useful when sourcing from international suppliers). Costs roll up automatically: a leaf's cost is quantity × unit cost, and every parent node's cost is the sum of its children — so the top-level PBS node always shows the full bill of materials cost for the project.
5. Set delivery dates for procured items
For 'buy' items especially, set a target delivery date. These appear on the Gantt chart as orange delivery diamonds, distinct from project milestones — giving you a single timeline view of both internal work and external deliveries.
6. Link PBS deliverables to WBS work packages
Where a 'make' item requires internal effort, link the PBS node to the WBS task(s) that produce it. This connects your bill of materials to your schedule: the people doing the work, the hours they'll spend, and the deliverable they're producing are now traceable to each other.
7. Track actuals as the project progresses
Once the project is active, record actual delivery dates and actual costs against each PBS node as items arrive and invoices come in. Comparing planned vs. actual cost and delivery date per item gives you an early warning when a sub-system is running late or over budget — well before it shows up in the overall project EVM numbers.
Common PBS mistakes to avoid
Mixing activities into the PBS
Items like 'Integration testing' or 'Design review' are work, not products — they belong in the WBS. If a PBS node describes something you'd never put in a bill of materials, it's probably a WBS task in disguise.
Skipping the make/buy decision
Without a clear make/buy flag, it's easy to end up with deliverables that have neither a cost (because nobody is buying them) nor a linked WBS task (because nobody is making them) — and they silently fall out of both the budget and the schedule.
Leaving unit costs blank "for now"
A PBS with missing unit costs can't roll up to a meaningful total, which undermines cost-based EVM (PV/EV/AC) for the whole project. Even a rough placeholder cost, refined later, is better than a gap in the rollup.
Forgetting currency on international purchases
If sub-systems are sourced from suppliers in different currencies, set the currency per PBS node and let the platform apply exchange rates — don't pre-convert manually, or the audit trail back to the original quote is lost.
Already have a schedule? See How to Build a Work Breakdown Structure (WBS) to connect your deliverables to the work that produces them.
Track your bill of materials alongside your schedule
Helmcraft's PBS editor rolls up costs bottom-up, shows delivery dates as diamonds on the Gantt chart, and links deliverables to the WBS tasks that produce them — free for teams up to 3 seats.