The scheduled finish date (SF), also called the planned finish date, is the point in time at which work is planned to finish on a schedule activity. It lies inside the window the critical path method calculates: never earlier than the activity’s early finish date and never later than its late finish date.
How a scheduled finish date is produced
The calculated dates come first. A forward and backward pass through the network gives every activity an early start, early finish, late start and late finish. The PMBOK® Guide is explicit that those four dates are not the schedule itself: they define time windows within which each activity may be executed, based on durations, dependencies, leads, lags and constraints.
The scheduled finish date is the date the planner actually commits to inside that window. Getting there usually means:
- Resource optimization. Resource leveling adjusts start and finish dates to match the demand for resources with the available supply, which can push a scheduled finish past its early finish and may even move the critical path. Resource smoothing does the same within the available float, so it leaves the finish date alone.
- Calendars and constraints. Non-working days, shift patterns and imposed dates all shift the committed date away from the theoretical early finish.
- Approval. Once the schedule model is approved, its scheduled dates are frozen as the schedule baseline and from then on serve as baseline finish dates for variance measurement.
Scheduled finish date versus the other finish dates
- Early finish (EF): earliest the activity can finish given logic and durations. From the forward pass.
- Late finish (LF): latest it can finish without delaying the project or breaking a constraint. From the backward pass. See also late start date and early start date.
- Scheduled finish (SF): the date in the working, resource-optimized schedule. This is what the plan says will happen.
- Baseline finish: the scheduled finish at the moment the baseline was approved. It does not move when the working schedule moves; that is the point of it.
- Target finish date: a date imposed from outside, by a contract, a launch window or a regulator. It is a requirement, not a calculation, and it may well be earlier than any achievable scheduled finish.
- Actual finish date (AF): when the work really finished. Recording it sets remaining duration to zero.
The counterpart at the front of the activity is the scheduled start date (SS); the two together with the activity duration describe the planned occupancy of the activity.
Scheduled finish date and PMBOK 8
Scheduled finish date is a legacy glossary term. The Eighth Edition does not contain the phrase at all, and the same is true of scheduled start date. Nothing about the concept has changed, only where it lives: the dates are attributes of the schedule model produced by schedule network analysis, and the Eighth Edition talks about them in that context rather than defining an acronym for each field.
Where the term does still matter is in monitoring. During monitoring and controlling the approved baseline start and finish dates are compared with the actual start and finish dates to determine variance, and those actual dates are collected as work performance data as of the current data date. Scheduling software still labels the fields Start and Finish for the scheduled dates, with separate Early, Late and Baseline columns, so the distinction survives in every tool even where the glossary dropped the term.
FAQ
Is the scheduled finish date the same as the late finish date?
No. The late finish is the last date that does not delay the project. The scheduled finish is the date you plan to finish on, and in a healthy schedule it sits comfortably before the late finish, leaving total float as the buffer between them.
Why is my scheduled finish later than the early finish?
Almost always resource constraints or calendars. Leveling a shared resource, a shutdown period or a lag on a predecessor all move the committed date to the right without changing the network logic.
Can the scheduled finish date change after the baseline is approved?
Yes, and it should. The working schedule is re-forecast at every data date. The baseline finish stays put so that the difference between the two is a measurable variance. Changing the baseline itself requires an approved change request.
Does the concept apply to agile work?
Not per activity. In a timeboxed approach the equivalent commitment is the end date of the iteration, which is fixed in advance, while the scope inside it flexes.
By Tom, PMP-certified since 2004. Last updated: July 2026.