Problem Statement — Planning & Scheduling Baselines linked to +Change ( Portfolio ) ContextAt 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.ProblemWhen 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.ImpactAudit & 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 amendmentProposed Solution (High Level)Enable multiple Planning & Scheduling Baselines, each explici