Late Finish Date (LF)

In critical path method (CPM), the Late Finish Date is the latest time an activity's remaining work can be completed without moving the project completion date, as determined by the schedule network logic and any schedule constraints.

Key Points

  • Calculated during the backward pass of CPM analysis.
  • Driven by network logic, the required project finish date, and any constraints or deadlines.
  • For activities on the critical path, LF equals EF (total float is zero).
  • Total float can be computed as LF - EF (equivalently LS - ES).

Example

A project must complete by day 60. The backward pass shows Activity D has LF = day 40. If Activity D finishes after day 40, the project would slip past day 60, so day 40 is its latest allowable finish without delaying the overall completion.

PMP Example Question

While performing a backward pass, the team wants to find the latest date Activity X can finish without delaying the project finish. Which value are they determining?

  1. Early Finish Date (EF)
  2. Late Start Date (LS)
  3. Late Finish Date (LF)
  4. Free Float

Correct Answer: C — Late Finish Date

Explanation: LF is the latest permissible finish for an activity based on the schedule network, project completion date, and any constraints, identified during the backward pass.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Write the OT incident plan your site will actually use

Go from a blank page to an approved, usable plan for your industrial site, one chapter at a time. ICS/OT Incident Response Plan: Write One That Works includes 50 videos, the plan template, worksheets and a full model answer, delivered through HKSM Courses for US$147 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course