3.5 The WBS Dictionary
Key Takeaways
A WBS dictionary records work-package detail, ownership and acceptance criteria.
Change control evaluates cost, time, resources and risk before an authorised decision.
Quality control checks specifications, while scope acceptance confirms an agreed deliverable is accepted.
The WBS Dictionary
A visual WBS chart shows hierarchical structure, but lacks operational details. The WBS Dictionary provides the narrative data required to execute each work package unambiguously.
| WBS Code | Work Package Name | Deliverable Description | Responsible Owner | Acceptance Criteria | Estimated Cost |
|---|---|---|---|---|---|
| 2.1.3 | Ballroom Audiovisual Rigging | Overhead motor rigging, lighting trusses, and structural weight load certifications for main stage | Production Lead | Rigging plots approved by municipal structural engineer and venue rigging master | $28,500 |
| 3.2.1 | Keynote Speaker Briefing | Preparation and delivery of technical rider, stage format guide, and travel itinerary to 4 keynote speakers | Programming Manager | Written confirmation and receipt of stage presentation slides 14 days pre-event | $4,200 |
| 4.1.2 | Attendee Registration Portal | Development, testing, and deployment of online registration system with secure PCI-compliant gateway | Marketing Tech Lead | Live processing test completed with zero payment gateway errors and automated confirmation | $12,000 |
| 5.3.4 | Banquet Event Orders (BEOs) | Detailed catering specifications for 6 food functions, including verified dietary requirements | Logistics Coordinator | Signed BEOs from venue catering director matched against verified attendee dietary profiles | $64,000 |
Tip
In WBS design, ensure all elements are formatted as nouns or deliverables (e.g., "Registration Portal", "Catering Plan"), rather than action verbs (e.g., "Build Portal", "Order Food"). The WBS is a deliverable decomposition, not a chronological to-do list. Activities and actions belong in the project schedule, not the WBS.
Managing Scope, Preventing Scope Creep & Change Control
During event execution, external stakeholders, executive leaders, and committee members will inevitably propose modifications. Without disciplined governance, these modifications cause scope creep.
Scope Creep vs. Gold Plating
- Scope Creep: The uncontrolled, unapproved expansion of product or project scope without adjustments to time, budget, resources, or quality baselines. Scope creep occurs when planners accept seemingly minor stakeholder requests without evaluating operational impacts (e.g., an executive committee member asking to add an unbudgeted champagne toast at the closing reception).
- Gold Plating: The practice of the project team voluntarily adding extra features, enhancements, or higher-specification items beyond the agreed requirements without client approval, under the misguided assumption that it adds value. Gold plating consumes project contingency, distracts team members, and introduces unvetted failure points.
+-----------------------------------------------------------------------------------+
| FIVE-STEP CHANGE CONTROL PROCESS |
+-----------------------------------------------------------------------------------+
| [ Step 1: Change Request Submitted ] |
| Stakeholder submits formal Change Request Form (CRF) documenting proposed change |
| | |
| v |
| [ Step 2: Comprehensive Impact Assessment ] |
| Lead PM analyzes Triple Constraint: Cost ($), Schedule (Days), Scope/Quality |
| | |
| v |
| [ Step 3: Governance Review (CCB / Sponsor) ] |
| Change Control Board approves, rejects, modifies, or defers the request |
| | |
| +------------------+------------------+ |
| | | |
| [ APPROVED ] [ REJECTED ] |
| v v |
| [ Step 4: Baseline Revisions ] Notify requestor with written rationale |
| Update Scope Statement, WBS, Log decision in Project Change Register |
| Master Schedule, and Budget (Process Terminates) |
| | |
| v |
| [ Step 5: Implementation & Communication ] |
| Execute vendor contract addenda, notify operational teams, adjust run of show |
+-----------------------------------------------------------------------------------+
The Five-Step Formal Change Control Process
To accommodate genuine business needs while protecting project integrity, all requested modifications must pass through a formal change control system:
- Request Submission: The requesting party completes a formal Change Request Form (CRF) detailing the modification, the business justification, and desired implementation timing.
- Impact Assessment: The event project manager conducts an integrated impact analysis evaluating the request against the triple constraint:
- Financial Impact: Additional direct and indirect costs (e.g., labor overtime, rush shipping, equipment rental).
- Schedule Impact: Effect on predecessor tasks, critical path float, and delivery deadlines.
- Operational & Risk Impact: Venue spatial constraints, power/HVAC requirements, safety liabilities, and staffing capacity.
- Evaluation and Decision: The Change Control Board (CCB) or executive project sponsor reviews the assessment. The request is formally Approved, Rejected, Modified, or Deferred.
- Baseline Adjustment: For approved changes, the project manager formally updates the project scope statement, WBS, WBS dictionary, schedule baseline, and budget.
- Implementation & Stakeholder Communication: Contract addenda are issued to vendors, operational crews are briefed, and the change is integrated into the production schedule.
Scope Verification vs. Quality Control
Planners must distinguish between checking deliverables for technical accuracy and securing formal acceptance:
- Quality Control (QC): An internal inspection process focused on verifying that deliverables meet established technical specifications, safety standards, and contract criteria (e.g., the technical production lead tests wireless microphone frequencies during rehearsal to verify zero RF interference).
- Scope Verification (Scope Validation): A governance process focused on securing formal, written acceptance of completed deliverables from the client, executive sponsor, or designated stakeholder (e.g., the corporate client conducts a pre-event walkthrough of the finished general session stage and signs off that it matches the approved architectural rendering).
+-----------------------------------------------------------------------------------+
| QUALITY CONTROL vs. SCOPE VERIFICATION |
+-----------------------------------------------------------------------------------+
| QUALITY CONTROL (QC) |
| - Focus: Correctness and technical compliance |
| - Performed by: Internal event team, engineers, safety inspectors |
| - Timing: During deliverable production and rehearsal |
| - Example: Sound engineer measuring decibel levels to ensure compliance with |
| municipal noise limits (under 85 dBA) |
| |
| SCOPE VERIFICATION (VALIDATION) |
| - Focus: Formal customer / stakeholder acceptance |
| - Performed by: Client, executive sponsor, authorized committee chair |
| - Timing: At milestone completions and final pre-con walkthrough |
| - Example: Client signs off on the ballroom stage setup after physical inspection|
+-----------------------------------------------------------------------------------+
Warning
Never begin operational work on an out-of-scope request based on verbal assurances from a client or executive. If an unbudgeted $15,000 hybrid video stream is executed without a signed change order, the finance department will enforce the contracted baseline budget during post-event audit, leaving the event planner personally accountable for the deficit.
Two weeks prior to an annual symposium, the vice president of marketing requests that the event team add an interactive virtual networking lounge with dedicated live moderation for remote attendees. This feature was not included in the original project scope statement. What is the correct procedure for the event project manager to follow?
Implement the request immediately to satisfy executive leadership, absorbing the additional technician costs into the general meeting supply budget
Reject the request outright and inform the vice president that no changes can ever be made to an event within 30 days of opening
Direct the audiovisual contractor to provide the streaming equipment as an unbilled favor to the organization
Require submission of a formal Change Request Form, conduct an impact analysis evaluating costs, schedule, and technical staffing, and submit it to the Change Control Board or sponsor for decision
During the final pre-conference venue inspection, the lead planner and the hotel convention services manager confirm that all 50 breakout tables are set precisely 6 feet apart against this event’s approved six-foot spacing specification. Later that afternoon, the corporate client's executive sponsor walks the ballroom, reviews the stage layout, and signs the formal physical acceptance document. In project management terminology, how are these two activities properly classified?
The fire safety distance check is Quality Control, while the sponsor's signed acceptance of the stage is Scope Verification (Validation)
The fire safety distance check is Scope Verification, while the sponsor's signed acceptance is Quality Control
Both activities represent internal Quality Control audits performed by supplier personnel
Both activities represent Scope Creep mitigation checkpoints governed by the Project Charter
Sections you finish are checked off in the contents.