6.2.2: Step 2 - Create the Scope Control Register

🎯 Purpose of This Step

The Scope Control Register is your master list of deliverables—linked directly to your approved project plan—that allows you to track what’s completed, what’s in progress, and what has changed. It is the frontline tool for managing:

• Completion status

• Ownership and accountability

• Scope changes (both requested and approved)

• Early detection of scope creep or unplanned additions

In professional settings, this kind of register becomes the source of truth used by the project manager, sponsor, and execution team to stay aligned and avoid surprises.

🧭 What You’re Building

You will create a working table (typically in Excel, Google Sheets, Notion, or similar format) that lists every key deliverable or scope item, and tracks its status throughout the project.

Think of this as your “scope scoreboard.”

🧱 Step-by-Step Instructions

🔹 1. Start With Your Approved WBS and Deliverables List

Begin by pulling every Level 2 or Level 3 item from your Work Breakdown Structure that represents a tangible output.

• These are typically deliverables, artifacts, approvals, or major outcomes.

• Do NOT include internal coordination tasks or administrative actions.

• If you’re unsure, ask: Would this item be reviewed, signed off, or handed off?

📘 Example Deliverables:

• “Finalize Requirements Document”

• “Stakeholder Training Session Conducted”

• “Clinical Workflow Wireframes Approved”

• “Pilot Build Deployed”

🔹 2. Build a Scope Control Register Table With the Following Columns:

Column	Description
WBS ID	Optional. Use if you want to trace back to your project plan.
Deliverable / Output Name	Clear, actionable description of what will be completed.
Owner / Role	Who is responsible for delivering or managing this item.
Target Date	When this item is expected to be complete (from milestone schedule).
Current Status	Use dropdowns like: Not Started, In Progress, Complete, Blocked.
% Complete	Numeric progress indicator (optional but helpful).
Scope Change Flag (Y/N)	Has this item changed from its original scope?
Change Description / Notes	Why it changed, who approved, or other context.
Approval Required? (Y/N)	Helps clarify which deliverables need formal sign-off.

📘 Optional Add-Ons:

• “Linked Milestone” – helps connect to the bigger picture.

• “Revision History” – if this register is used weekly, this helps track versioning.

🔹 3. Define Status Triggers and Update Rhythm

Clarify how this register will be used and updated:

• Who updates it (PM? Lead? Each task owner?)

• How often (Weekly? Biweekly? After each milestone?)

• What triggers a change in status (e.g., draft submitted = 50%, sponsor sign-off = 100%)

• When does a scope change flag get activated?

📘 Example Status Rules:

• “Not Started” = No work or kickoff done

• “In Progress” = Work underway; draft or partial submission exists

• “Complete” = Fully delivered and approved (if required)

• “Blocked” = Can’t move forward due to external dependency

🔹 4. Use Color or Icons for Visual Clarity

Make the register scannable:

• Use color coding (e.g., ✅ for complete, 🔒 for blocked, ⚠️ for changed)

• Freeze top row headers for scrolling

• Conditional formatting (e.g., highlight overdue tasks in red)

This helps sponsors and team leads immediately identify risks and wins.

🔹 5. Set Ground Rules for Managing Scope Changes

Scope change is inevitable. Your register should include:

• A formal “Scope Change Flag” (Yes/No toggle)

• A “Change Description” column

• Possibly: Date of change, source of request, and resolution status

This becomes your first line of defense against scope creep.

📘 Example:

Scope Change	Description
Yes	Added an accessibility audit after client request. Approved by sponsor 3/12. Estimated +8 hrs.

✅ What a Strong Scope Control Register Looks Like

WBS ID	Deliverable	Owner	Target Date	Status	% Complete	Scope Change	Notes
2.1.1	Draft Requirements Document	BA	Mar 10	In Progress	60%	No	SME review pending
3.2.4	Launch Pilot Build	Dev Lead	Apr 5	Not Started	0%	No	Blocked by delay in Test Plan
4.1.3	Conduct Stakeholder Training	Trainer	Apr 12	Complete	100%	Yes	Training duration extended by 1 day

🧠 Why This Tool Is Powerful

• Keeps all parties aligned on what’s done and what’s changing

• Allows the team to focus on deliverables that matter

• Serves as early warning system for misalignment, drift, or blockers

• Supports transparent and professional stakeholder communication

• Creates a shared accountability culture among delivery leads

---

✅ Once your Scope Control Register is complete, you’re ready to track execution with clarity.