Skip to content
Project Controls Open Standard

M1 — Scope, Data & Baselines

In the Open Standard

Module 1 establishes the essential building blocks for effective project controls. It explains how to define and structure project scope through a Work Breakdown Structure (WBS), establish consistent coding and control structures, and integrate scope, schedule, cost and responsibilities into an approved baseline. It also covers how to measure physical progress using objective evidence, distinguish actual performance from forecasts, and maintain reliable, traceable project data. Together, these practices provide a consistent and trustworthy foundation for planning, monitoring, reporting, decision-making and controlling change throughout the project lifecycle.

Started by James Williams ·
Last updated
Updated
Views
220 views

M1.1 — Scope & Work Breakdown Structures establishes the project’s scope backbone. It explains how to translate authorised scope into a practical Work Breakdown Structure that represents the whole undertaking without gaps or duplication, defines clear work-package boundaries and provides a stable basis for planning, estimating, assigning responsibility, measuring progress and controlling change.

M1.2 — Coding & Control Structures builds the information architecture around that scope backbone. It introduces the complementary structures and identifiers needed to view the same project by cost, organisation, resources, contracts, suppliers, locations and other management dimensions, showing how controlled mappings and reconciliations create multiple useful views without duplicating the underlying data.

M1.3 — Integrated Baselines brings scope, schedule, budget, responsibility, assumptions and progress rules together into one coherent authorised reference. It teaches the learner how to test whether discipline baselines describe the same project, distinguish the approved baseline from the latest forecast, challenge credibility before approval and preserve the reference so that subsequent performance and authorised change remain visible.

M1.4 — Progress Measurement defines how evidence of completed work is converted into a credible statement of physical accomplishment. It covers the selection of proportionate measurement methods, objective completion criteria, weighted aggregation, reporting cut-offs and the treatment of rework, while maintaining a clear distinction between genuine progress, elapsed time, money spent and the forecast of work remaining.

M1.5 — Data Quality, Integration & Traceability completes the module by ensuring that the resulting control information can be trusted. It explains how to define authoritative sources, common identifiers, data ownership, cut-offs, validation, reconciliation, lineage and historical snapshots so that management information can be traced to evidence, reproduced by another competent practitioner and used confidently for decision-making.

In this chapter

  1. 01M1.1 — Scope & Work Breakdown Structures
  2. 02M1.2 — Coding & Control Structures
  3. 03M1.3 — Integrated Baselines
  4. 04M1.4 — Progress Measurement
  5. 05M1.5 — Data Quality, Integration & Traceability

Comments

No comments yet.

Log in or join to comment

Knowledge

  • Work Breakdown Structure

    Wiki

  • Activity Codes

    Wiki

  • OBS and EPS in Primavera P6

    Wiki

  • Baseline Management

    Wiki

  • WBS Structure

    Wiki

Discussions

Blogs

Norms