Context

At the end of the Planning phase, Program Managers build the full program schedule (stages, tasks, durations, dependencies) and take a single Planning & Scheduling Baseline. Current guidance allows only one such baseline at that point.

Problem

When scope changes after planning (e.g., an Amendment / +Change to the original MSA ), there is no mechanism in Planview to:

• take an additional Planning & Scheduling Baseline, and
• associate that new baseline to the specific amendment/SOW it supports.

This prevents clear traceability between contractual changes and the schedule state that was agreed at that time.

Impact

• Audit & Traceability gaps: Cannot prove which baseline aligns to which amendment / SOW
• Baseline integrity risk: Teams could overwrite or avoid baselines, losing historical comparators
• Reporting limitations: Portfolio and PMO reports cannot roll-up baseline deltas by amendment

Proposed Solution (High Level)

Enable multiple Planning & Scheduling Baselines, each explicitly linked to a contract artifact

Key Capabilities

1. New Baseline Action (Planning & Scheduling):
   • Allow additional baselines to be captured post-planning when scope changes
2. Association on Capture:
   • Required metadata inputs on baseline creation:
   • Amendment / +Change ID ( Lookup to +Change Register )
     1. Amendment Title
     2. Reason Code (scope, compliance, customer request, etc.)
     3. Notes (optional)
3. Uniqueness & Governance:
   • Enforce one baseline per amendment ID ( +Change)
   • Role-based permissions; audit log of who / when / why
4. Acceptance Criteria

• AC1: Users can create additional Planning & Scheduling Baselines after the initial planning phase
• AC2: On creation, user must select / enter a valid +Change ID; save is blocked if missing / invalid
• AC3: System prevents multiple baselines tied to the same Amendment ID (unless explicitly overridden by an admin)
• AC4: Baseline records store: ID, Name, Amendment ID, Reason, User, Timestamp, Notes
• AC5: Full audit trail recorded and reportable

Benefits

• Restores contractual traceability between amendments and schedule state
• Improves governance and auditability
• Enables accurate variance reporting and better change control decisions

Kind Regards,

Haydn Milton