The actual finish date (AF) is the point in time at which work on a schedule activity actually finished. Every other finish date in a schedule model is either a calculation or a forecast. The actual finish date is a recorded fact, and once it is entered it overrides the planned dates for that activity.
An activity finishes when its work is complete and meets its acceptance criteria, not when someone stops working on it. That distinction is the difference between a schedule that reflects reality and one that quietly accumulates activities stuck at 95 percent.
How an actual finish date gets into the schedule
- The team reports completion during the regular status cycle, against a fixed data date (DD).
- The date must be on or before the data date. A finish date in the future is a forecast, not an actual.
- The scheduling tool sets remaining duration to zero and percent complete to 100 for that activity.
- Actual duration is then measured from the actual start date (AS) to the actual finish date.
- Successor activities are recalculated from the actual date rather than the planned one, so a late finish pushes the network forward immediately.
Actual finish date vs. the other finish dates
| Date | What it is |
|---|---|
| Early finish date (EF) | Earliest possible finish from the forward pass. A boundary, not a plan. |
| Late finish date (LF) | Latest finish from the backward pass without delaying the project. |
| Scheduled finish date (SF) | The finish date in the current working schedule, somewhere between EF and LF. |
| Baseline finish date | The approved finish date frozen in the schedule baseline. The yardstick for variance. |
| Target finish date | A date imposed on the activity as a constraint or commitment. |
| Actual finish date (AF) | The date the work was actually completed. Recorded, never calculated. |
Actual finish date in PMBOK 8
The PMBOK Guide – Eighth Edition has no separate glossary entry for “actual finish date”. The exact phrase appears once, inside the definition of actual duration: the time in calendar units between the actual start date of the schedule activity and the data date if the activity is in progress, or the actual finish date if the activity is complete.
The concept itself is present in three places:
- Work performance data. “Actual start and finish dates of schedule activities” is listed among the raw observations gathered during execution and handed to the controlling processes.
- Schedule baseline. During monitoring and controlling, the approved baseline dates are compared to the actual start and finish dates to determine whether variances have occurred.
- Performance reviews. These measure, compare and analyze actual performance of work in progress against the schedule baseline, using actual start and finish dates, percent complete and remaining duration.
The ordering matters: an actual finish date on its own is data. It becomes work performance information only after it is compared against the baseline and the variance is interpreted.
Practice
- Define “finished” before you need it. Deliverable handed over, review passed, defects closed — whatever the rule is, agree it up front, otherwise every reported finish date means something slightly different.
- Collect against one data date. Status pulled from different people on different days produces a schedule that never matches any single moment in time.
- Do not backdate to protect a variance. The gap between baseline finish and actual finish is the signal you need for the remaining work. Erasing it costs you the forecast.
- An activity with an open defect is not finished. Record the finish when the rework is done, or track the rework as its own activity.
FAQ
Can an actual finish date be later than the data date?
No. The data date is the cutoff for reported progress. Anything after it is planned or forecast work.
What is the difference between actual finish and baseline finish?
Baseline finish is the approved commitment; actual finish is what happened. The difference between the two is the schedule variance for that activity.
Does the actual finish date still matter in agile work?
Yes, in a different form. The equivalent is the date a story met the definition of done or the date a timebox closed. Cycle time and throughput are built from exactly this kind of actual date.
What happens if completed work has to be redone?
Either reopen the activity and clear the actual finish date, or add a rework activity. Leaving a finish date on work that is being redone makes variance analysis and forecasting unreliable.
By Tom, PMP-certified since 2004. Last updated: July 2026