Build work and cost structures and retain a scope baseline
Create WBS work packages, CBS cost codes and explicit relationships to delivery records; freeze exact work and allocation revisions as a baseline.
Current Revision 7 Reviewed Oct 27, 2026
On this page
Before you beginCurrent capability and authorityClearly labeled synthetic exampleRetain a named schedule comparison baselineInputs and terminologyProcedureVerify the resultWhat happens nextTroubleshootingBefore you begin#
- controls_read to inspect the structure and control_admin to configure it.
- Existing equipment, delivery stages and requirement records for the intended scope.
Current capability and authority#
Create WBS work packages, CBS cost codes and explicit relationships to delivery records; freeze exact work and allocation revisions as a baseline.
Clearly labeled synthetic example#
Synthetic work package WP-SWG links SWG-01, its procurement release milestone and its approved capacity requirement. A later scope edit does not rewrite baseline BL-01.
Retain a named schedule comparison baseline#
Scope baselines retain WBS/CBS relationships. Open Schedule, expand Named schedule baselines and choose Publish comparison baseline. Review the current milestone source basis, choose Original adopted milestone dates or Currently assessed forecast dates, and enter a baseline name and decision basis. Choose Review baseline, then Publish retained baseline. Publishing requires a project manager with schedule approval authority.
Publishing appends an immutable version with exact milestone revisions and calendar basis; it does not rewrite original milestone baseline dates. Missing forecast dates remain unknown. Select the retained baseline name to inspect its dates, or Compare in analytics to select that exact comparison version. Calendar-day variance is not critical-path computation.
Inputs and terminology#
| Term | Meaning |
|---|---|
| WBS | Work breakdown structure: deliverables and accountable work packages. |
| CBS | Cost breakdown structure: project cost codes, independent of software licensing. |
| Allocation | An explicit work/cost/equipment relationship with a defined percentage; not a copied financial amount. |
Procedure#
Create work packages
Open Scope and choose Work breakdown. Add a work package with reference, title, owner and scope statement. Select its parent where applicable.
Connect the delivery basis
Search and select equipment, delivery milestones, power requirements and exact evidence versions. Review retained links before saving.
Create cost codes and allocations
Use Cost breakdown to create the CBS. In Allocations, connect a work package and cost code, select relevant equipment or an authorized commitment, and set the allocation percentage.
Record the scope baseline
Open Scope baselines, add a baseline, select the exact current work-package and allocation revisions, and record the approval/decision basis.
Inspect history
Use Inspect versions to verify the retained record and source relationships. Create another baseline when the agreed scope changes.
Verify the result#
The baseline stores explicit revision references; subsequent live edits leave its original contents intact.
What happens next#
A scope baseline does not approve a contract, a cost posting or an engineering acceptance.
Project closure and retention still follow the configured organizational policy.