Compare two states
Review current and proposed finish dates, affected activities, conflict days and projects beyond commitment dates.
Compare current and proposed schedules across projects, shared people and delivery commitments.
| Project commitment | Current finish | Proposed finish |
|---|---|---|
| Atlas · 23 Oct | 23 Oct | 26 Oct |
| Nova · 28 Oct | 28 Oct | 28 Oct |
The proposal preserves a locked task. One shared-resource conflict remains unresolved.
A change that helps one project can create a conflict elsewhere. Teams need to see the full effect before applying it.
An explainable change decision across the portfolio.
Review current and proposed finish dates, affected activities, conflict days and projects beyond commitment dates.
Dependencies, locked work, daily availability and source reservations constrain the planning proposal.
Use manual or assisted proposals, inspect unresolved conflicts, then apply the reviewed change or discard it.
Adjust a date, remaining effort or allocation in the draft.
Inspect people conflicts and project finish changes.
Commit the reviewed proposal or discard the preview.
A proposal is not a saved commitment until applied. Automatic proposals do not guarantee an optimal or conflict-free plan; confirm availability for your release.
Review the full product scope →Plan dependent work with working days, shared resources and visible delivery commitments.
DeliveryReview workload, remaining effort and availability across project tasks and company work.
People & costReview project and portfolio labor and material budgets, approved actuals, forecasts and margins.
Bring a real workflow to the conversation.
We’ll explore where MCT Orbit fits.