A Work Breakdown Structure divides the complete project scope into packages that can be planned, priced, assigned, and monitored. A reliable WBS connects drawings, the BOQ, programme, budget, procurement, and progress reporting.
Start with the project objectives and scope
Define the required project outcome, work boundaries, assumptions, exclusions, and controlled reference documents. Record unresolved scope as an open decision instead of hiding it inside a general package.
Choose an appropriate hierarchy
Build the hierarchy from project to phase, area or discipline, work package, and manageable activity. Avoid packages that are too broad to measure or so detailed that administration becomes inefficient.
Apply the 100 percent rule
The WBS should include the entire agreed scope, including temporary works, testing, mobilisation, records, and handover. Child packages must fully represent their parent without duplication.
Connect the WBS to cost and schedule
Assign a unique code to every package and use it consistently in the BOQ, cost plan, schedule, procurement register, and reports. This makes the time and cost effect of a scope change traceable.
Assign responsibility and completion criteria
Each work package needs an owner, deliverable, measurement basis, required resources, and acceptance criteria. A defined completion rule prevents progress from being reported subjectively.
Review checklist
Confirm there are no omissions or overlaps, codes are consistent, packages are measurable, responsibilities are clear, and links to cost, schedule, quality, risk, and procurement are recorded.
WBS dictionary and cost-code example
| Level | Example | Control purpose |
|---|---|---|
| 1 | Project | Overall reporting |
| 2 | Structure, architecture, MEP | Discipline control |
| 3 | Zone or floor | Location control |
| 4 | Work package | Cost, schedule, and responsibility |
A WBS Dictionary should define scope boundaries, deliverables, drawings, measurement rules, ownership, dependencies, risks, and acceptance criteria for every code. Design, QS, planning, procurement, and site teams should jointly validate coverage.
Common errors and quality indicators
- Mixing deliverables and activities without a consistent rule.
- Using vague package names with unclear boundaries.
- Omitting testing, commissioning, records, or handover.
- Using different codes in the BOQ, schedule, and cost report.
- Assigning packages without one accountable owner.
A strong WBS maps all scope, cost, activities, progress, and changes without omissions or double counting.
Supporting products
Use the Quantity Surveyor Pro Template Package with RAP Contractor Pro to structure work packages and project controls.
Conclusion
A WBS is not merely an activity list. It is the project control framework. Clear boundaries, codes, deliverables, and ownership make cost, time, change, and accountability easier to manage.
Professional implementation framework
A WBS is a control structure that decomposes project scope into deliverables and work packages that can be estimated, scheduled, assigned, measured, and closed. An activity list without links to scope, cost, and accountability will not provide a controllable baseline.
Roles and accountability
The project manager defines decomposition rules; the planner links packages to the schedule; the quantity surveyor and cost controller connect quantities and cost; discipline engineers validate technical scope; document control protects codes and revisions; package owners accept accountability for deliverables.
Mandatory inputs and hold points
The contract, scope of work, drawings, specifications, BOQ, milestones, construction methods, procurement strategy, zoning, organization structure, and coding standard are minimum inputs. Record assumptions and exclusions to prevent overlap and omissions.
Every hold point must be recorded in the Inspection and Test Plan. Work must not proceed on verbal approval alone when the next activity will conceal or remove inspection evidence.
Control sequence
- Define the highest level by deliverable, area, phase, or discipline in line with the control strategy.
- Decompose until each work package has a clear boundary, one accountable owner, quantity basis, duration, cost, and verifiable output.
- Prepare a WBS dictionary covering code, description, inclusions, exclusions, acceptance, interfaces, owner, and references.
- Map each package to schedule activities, cost codes, procurement packages, risks, and reporting without duplicate codes.
- Complete cross-discipline review and a 100-percent scope test before baseline approval.
Acceptance criteria
Contract scope is represented once, packages do not overlap, each package has an owner and measurable output, codes are consistent, BOQ and schedule links are traceable, and revisions follow change control.
Convert each criterion into a checklist item supported by a measurement, compliant/noncompliant status, location, date, document revision, inspector, and photograph. Terms such as good or adequate are not acceptable without a defined measure or reference.
Quality records and handover
Retain the WBS master, dictionary, WBS-BOQ-schedule mapping, owner matrix, review minutes, approved baseline, and revision log. Progress reports must use the same coding structure so time and cost can be reconciled.
Index records by area and date so they remain traceable during changes, claims, defects, and owner reviews. Incomplete documents become outstanding items with an owner and target closure date.
Risk and nonconformance
Packages that are too large conceal problems, while excessive detail creates administrative burden. Other risks include gaps, double counting, changing codes after award, and misaligned procurement. Review routinely without informal baseline changes.
Do not conceal a finding with subsequent work. Identify the area, review the cause, approve corrective action, and reinspect. A repair is closed only when objective evidence confirms that the required function and quality have been restored.
Work close-out
Close a package after deliverable acceptance, quantity and cost reconciliation, completion of as-built or handover records, identification of open claims, and transfer of lessons learned.
