Build a Residential Project Work Breakdown Structure

A. Finished-Project Specification

Deliverable: one approved residential work breakdown structure, dividing the project into phases and deliverable-based work packages, each with a measurable deliverable, one assigned primary responsible party, aligned cost and schedule codes, linked drawing and specification references, identified quality and inspection requirements, and a supporting WBS dictionary, reconciled against the scope statement, the estimate, and the permit plan and approved by the authorized party.

B. WBS Document Schedule

Section	Content	Source	Purpose
Level-one deliverable	The final completed project as the top of the structure	Approved scope baseline	Establishes the single deliverable every package rolls up to
Phases	Major project divisions such as preconstruction, mobilization, sitework, structure, enclosure, MEP, interiors, exterior work, commissioning, closeout	Scope baseline, project type	Groups related work packages into manageable divisions
Work packages	Deliverable-based units for demolition, temporary work, permits, submittals, procurement, and trade installation	Scope baseline, drawings, specifications	Defines the lowest-level unit that can be assigned, scheduled, cost-coded, inspected, and closed
Package boundaries	Start condition, finish condition, and measurable deliverable for every package	Scope baseline, drawings	Prevents omitted or duplicated work
Owner, utility, and third-party work	Owner work, utility work, separate contracts, and excluded work identified within the structure	Scope baseline	Distinguishes contractor packages from work outside contractor responsibility
Allowances, alternates, and changes	Allowances, alternates, unit-price work, and potential changes as controlled branches	Scope baseline, estimate	Prevents hidden or unmanaged conditional work
Responsibility and codes	One primary responsible party, cost code, schedule identifier, and procurement identifier per package	Estimate, accounting system, scope baseline	Links each package to accountability, budget, and schedule
References	Drawing, specification, scope, and estimate reference per package	Drawings, specifications, estimate	Allows the package to be verified against controlling documents
Quality, risk, and closeout	Quality-control and inspection requirements, concealment, long-lead, high-risk, schedule-critical status, and closeout deliverables per package	Permit plan, quality requirements, scope baseline	Flags packages requiring special coordination before schedule and procurement are built
WBS dictionary	Code, title, scope, deliverable, exclusions, owner, references, acceptance, closeout for each package	All prior sections	Provides the complete written definition of every package in one reference document

C. Information and Document Takeoff

• Source records: the approved Project 01 scope baseline, drawings, specifications, and the Project 02 job file, sufficient to draft every section of the document schedule above without inventing missing scope information.
• Comparison records: the Book 24 estimate and the Book 25 permit-and-inspection plan, used in Steps 29–30 to identify cost codes without work packages, work packages without budget, and regulated work packages missing from the structure.
• Cost-code reference: the company accounting cost-code list, used in Step 18 to assign codes that reconcile with the estimate and accounting system.
• Approval record: written confirmation of the person or role authorized to approve the WBS baseline, obtained before the baseline is frozen.

D. Acceptance Standards

Check	Standard
Phases	Adjusted to the actual project; no unused category forced into the structure
Work packages	Every lowest-level package has a measurable, completed deliverable stated as a result, not an activity
Package boundaries	No scope item omitted; no scope item counted inside more than one package
Responsibility	Exactly one primary responsible party assigned to each package
Cost and schedule codes	Aligned with the Book 24 estimate and company accounting system; no invented parallel scheme
References	Every package linked to its governing drawing, specification, scope, and estimate reference
Reconciliation	WBS compared against the scope statement, estimate, and permit plan; gaps and duplications identified and resolved before approval
Approval	Written approval obtained from the authorized party; baseline number and date assigned before distribution

E. Preparation — Establish the Deliverable and Phase Structure

1. Begin with the approved scope baseline and current project documents. Confirm the version in use matches the current baseline recorded in the job file.
2. Identify the final project deliverable as WBS level one. State the completed project as the single top-level deliverable every package rolls up to.
3. Divide the project into major phases such as preconstruction, mobilization, sitework, structure, enclosure, MEP, interiors, exterior work, commissioning, and closeout. Use these as the starting phase list.
4. Adjust phase names to the actual project rather than forcing unused categories. Remove or rename a phase that does not apply to the approved scope.
5. Break each phase into systems, areas, floors, rooms, or work packages that can be managed independently. Divide each phase to a level field supervision can assign and track.
6. Identify demolition, temporary work, protection, access, and enabling work as separate deliverables. Do not bury enabling work inside a permanent-work package.
7. Identify permit, submittal, procurement, utility, inspection, testing, and owner-decision packages. Record each as its own work package rather than an implied task.
8. Identify each trade installation package from start condition through accepted completion. State the condition that begins the package and the condition that completes it.
9. Include layout, material handling, installation, testing, correction, cleanup, and handoff within each package where applicable. Confirm the package deliverable accounts for all of these where relevant.
10. Define a measurable deliverable for every lowest-level work package. State the deliverable as a completed, verifiable result.

F. Define Package Boundaries and Third-Party Work

11. Avoid vague verbs that do not describe a completed result. Replace activity-only phrasing with a stated finished condition.
12. Define package boundaries so work is neither omitted nor counted twice. Check adjoining packages for overlap and gaps at every boundary.
13. Identify owner work, utility work, separate contracts, and excluded work in the structure. Mark each item with its correct category so it is not mistaken for a contractor-responsible package.
14. Identify allowances, alternates, unit-price work, and potential changes as controlled branches rather than hidden tasks. Give each its own identifiable branch in the structure.
15. Assign one primary responsible party to each work package. Confirm the assignment matches the responsibility matrix from Project 01.
16. Identify supporting, reviewing, approving, inspecting, and informed parties. Record these roles alongside the primary responsible party for each package.
17. Link each work package to the relevant drawing, specification, scope, and estimate reference. Record the exact document and section reference, not a general description.

G. Assign Codes and Identify Risk Factors

18. Assign cost codes aligned with the Book 24 estimate and company accounting system. Use the accounting system's exact code structure.
19. Assign schedule activity identifiers that can be rolled up to the WBS. Confirm each identifier maps back to exactly one WBS package.
20. Assign procurement package identifiers for material-dependent work. Link each material-dependent package to its procurement identifier for use in Project 07.
21. Assign quality-control and inspection requirements to each applicable work package. Record the requirement at the package level rather than as a separate unlinked list.
22. Identify required submittals, samples, shop drawings, mockups, and owner selections. Record these against the specific package they affect.
23. Identify predecessor inputs and successor handoffs without yet assigning dates. Record the logical relationship only; leave date assignment to Project 04 and Project 05.
24. Identify work that will be concealed and requires preclosure documentation. Flag each concealed package for the quality plan in Project 13.
25. Identify long-lead, high-risk, high-value, safety-critical, and schedule-critical packages. Record the reason for each flag.
26. Identify closeout deliverables generated by each trade or supplier. Record these against the applicable package for use in Project 18.

H. Build the Dictionary, Reconcile, and Approve the WBS

27. Create a WBS dictionary defining code, title, scope, deliverable, exclusions, owner, references, acceptance, and closeout for each package. Complete one dictionary entry per work package without exception.
28. Compare the WBS with the scope statement and confirm every scope item appears. Record any scope item not represented by a package.
29. Compare the WBS with the estimate and investigate cost codes without work packages or work packages without budget. Record every mismatch found.
30. Compare the WBS with the permit and inspection plan. Confirm every regulated package is represented and correctly flagged.
31. Review the WBS with field supervision, estimator, scheduler, procurement, accounting, quality, safety, and key trades as applicable. Distribute the draft far enough in advance for informed review.
32. Revise packages that are too broad to control or too detailed to manage efficiently. Adjust package size based on reviewer feedback before freezing the baseline.
33. Freeze the approved WBS baseline and assign its revision. Record the baseline number and date directly on the WBS-approval record.
34. Distribute the WBS and dictionary to the project team. Confirm distribution against the stakeholder list from Project 01.
35. Require approved scope changes to update the WBS before schedule and budget changes are finalized. State this rule directly in the WBS documentation.