Schedule baselines

A schedule baseline belongs to a work package and operating organization. Project Manager prepares its revision, planned hours and scope note, then submits its identity with the package’s task graph. The feasibility check examines dependencies and dates so an approved result can be tied to a specific schedule revision.

A feasible submission becomes Approved and is frozen; an infeasible submission becomes Rejected. The recorded decision and operation outcome make the technical result available for review. Delivery Lead then considers the checked package alongside scope and staffing and manually records a separate work-package decision for the team to follow during delivery.

• Submission. Project Manager identifies the correct package and baseline revision and sends the corresponding task graph for checking. Keep the technical reference useful for locating the actual plan behind the request.
• Feasibility result. The workflow checks circular dependencies, missing predecessor references and impossible finish-to-start dates. Inspect the resulting baseline state, decision and receipt before relying on the check.
• Work-package authorization. Delivery Lead decides whether the feasible package is an acceptable commitment. Manually record the work-package subject and decision notes so this management handoff remains distinct from the graph’s technical result.

Agree what the technical revision identifies and how a reviewer retrieves the checked graph. Decide how a changed task plan becomes a new baseline revision while preserving the earlier approved result. Keep organization and package references aligned with the project so the submitted graph cannot quietly represent a different engagement.

Agree when the team requires a recorded work-package decision and who may submit a baseline. Delivery Lead records that manual decision under the agreed procedure. Define what the lead needs to see about staffing, scope and unresolved risks before authorizing delivery. A feasible graph can still describe work the team cannot accept within its available capacity or business commitment, so retain that judgment in the decision notes.

Use a package with a valid predecessor chain but a successor scheduled to begin before its predecessor finishes. Project Manager submits the graph and reads the rejected result. Correct the date relationship and submit the revised plan. Inspect the approved revision and its locked time together with the recorded operation outcome.

Delivery Lead reviews that feasible plan and returns the work-package decision because the assigned people cannot cover the intended interval. Keep the approved feasibility result intact while the manager changes the working plan and prepares a new revision. Once the lead accepts the revised commitment, record the approved work-package decision. Rehearse a later task edit and verify which baseline remains the frozen reference for the earlier decision.

• Baseline Review Queue — Submitted baseline identities with their package, revision, planned hours and technical reference.
• Approved Baselines — Approved schedule revisions with their decision and locked times.
• Recorded Decisions — Recorded subject decisions and the notes explaining the authorized commitment.

Follow Plan and authorize a schedule, then use Review delivery exceptions when the working plan needs attention.