Calculate the critical path
The example below is filled in so you can see how it works. Change any row, or press Clear and type your own network.
27 days · critical path A → B → D → F → H → I
| ID | Activity | Days | Predecessors | Remove |
|---|---|---|---|---|
Result
Project length: 27 days. Critical path: A → B → D → F → H → I.
| ID | Activity | Days | ES | EF | LS | LF | Float | Critical |
|---|---|---|---|---|---|---|---|---|
| A | Define requirements | 3 | 0 | 3 | 0 | 3 | 0 | Yes |
| B | Design the system | 5 | 3 | 8 | 3 | 8 | 0 | Yes |
| C | Order hardware | 7 | 3 | 10 | 7 | 14 | 4 | No |
| D | Build the software | 10 | 8 | 18 | 8 | 18 | 0 | Yes |
| E | Install hardware | 4 | 10 | 14 | 14 | 18 | 4 | No |
| F | Integrate software and hardware | 3 | 18 | 21 | 18 | 21 | 0 | Yes |
| G | Write training material | 4 | 8 | 12 | 21 | 25 | 13 | No |
| H | Test the whole system | 4 | 21 | 25 | 21 | 25 | 0 | Yes |
| I | Train users | 2 | 25 | 27 | 25 | 27 | 0 | Yes |
How to use the calculator
- List the activities. Give each activity a short id (A, B, C), a name and a duration in whole days. Use 0 days for a milestone.
- Enter the predecessors. For each activity, type the ids of the activities that must finish before it can start, separated by commas. Leave it empty for activities that can start on day 0.
- Read the result. The calculator runs the forward and backward pass as you type. It shows the project length, the critical path, and the early start, early finish, late start, late finish and float of every activity.
- Open it as a Gantt chart. Open as a Gantt chart puts the network into the editor with its links, so you can set real dates, owners and progress. No account is needed.
What the columns mean
| Column | Meaning |
|---|---|
| ES, early start | The earliest day the activity can start: the latest early finish of its predecessors, or day 0 if it has none. |
| EF, early finish | Early start plus duration. |
| LF, late finish | The latest day it can finish without delaying the project: the earliest late start of the activities that wait for it, or the project end if none do. |
| LS, late start | Late finish minus duration. |
| Float | Late start minus early start: how many days it can slip before the finish date moves. Zero float means it is on the critical path. |
Days are counted from 0, the way most textbooks do it: an activity with ES 3 and a duration of 5 runs from the end of day 3 to the end of day 8. On a calendar, that is the 4th to the 8th working day.
The worked example, step by step
The example is a small system project: define requirements (A), then design the system (B) and order hardware (C) at the same time. The software build (D) waits for the design, and installing the hardware (E) waits for the order. Integration (F) needs both, testing (H) follows integration, and training (I) needs the training material (G) and a tested system.
Forward pass. A runs from day 0 to 3. B and C both start on day 3; B finishes on day 8 and C on day 10. D runs from 8 to 18, E from 10 to 14. F waits for the later of D and E, so it starts on day 18, not 14. H follows on day 21, and I waits for both G (finished on day 12) and H, so it starts on day 25 and the project ends on day 27.
Backward pass. Starting from day 27, I must start by day 25, so H must finish by then and start by day 21. F must start by day 18, which means both D and E must finish by day 18. E can therefore start as late as day 14, and C as late as day 7: 4 days of float each. G only has to finish by day 25, so it has 13 days of float.
Critical path. The activities with zero float are A → B → D → F → H → I, 27 days in total. Shortening any of them shortens the project; shortening C, E or G does not, until their float is used up and another path becomes the longest.
When the critical path changes
The critical path is a result, not a fixed list. If ordering the hardware takes 12 days instead of 7, C and E become critical and the design and build path gains float. Try it in the calculator: change C's duration and watch the summary line. On a live project this is why the critical path is rechecked whenever an estimate changes, rather than worked out once at the start.
For a project with dates, owners and progress, it is easier to keep the network on a Gantt chart, where the critical path is drawn on the bars and updates as you drag them. The free Gantt chart maker and every Gantt chart template on this site show it the same way.
Frequently asked questions
- What is the critical path?
- The longest chain of dependent activities from the start of a project to the end. Its total duration is the shortest time the project can take. Any delay to an activity on the critical path delays the finish by the same amount.
- How do you calculate the critical path?
- Run a forward pass to find each activity's earliest start and finish, then a backward pass from the project end to find each activity's latest start and finish. Float is latest start minus earliest start. Activities with zero float form the critical path.
- What is float (slack)?
- Total float is how many days an activity can slip without moving the project's finish date. An activity with 4 days of float can start up to 4 days late and the project still finishes on time, as long as nothing else slips.
- Can a project have more than one critical path?
- Yes. If two chains of activities have the same, longest total duration, both are critical and every activity on either has zero float. The table marks every zero-float activity as critical; the summary line follows one of the chains.
- Is my data sent anywhere?
- No. The calculation runs in your browser. Nothing is sent to gantt-chart.io unless you open the result in the editor and then sign in to save it.
- Does the calculator handle lag or other link types?
- No. It uses finish-to-start links with no lag, which is how most critical path examples and exam questions are set. The Gantt chart editor supports start-to-start, finish-to-finish and start-to-finish links and lag.