HSC Mathematics Standard 2 critical path analysis (2026 guide)
Critical path analysis finds the minimum project duration as the longest path through the activity network; forward scanning gives earliest start times for events, backward scanning gives latest start times, and float = LFT EST duration identifies which activities are critical (zero float) and which have slack (positive float).
Jump to a section
Figure 1. Activity-on-edge network for a 7-activity kitchen renovation. The heavier accent edges form the critical path A D E F G with total duration days. The three trades B, C and D run in parallel between events 2 and 3; B and C finish with time to spare, so they carry float. Each activity has a box at its tail showing its earliest start time (EST, left) and latest start time (LST, right); a critical activity has EST LST.
Critical path analysis (CPA) is the most heavily examined Networks topic in HSC Mathematics Standard 2. Every paper since the 2017 syllabus reform has had a CPA question, typically worth - marks in Section II.
It is also one of the most predictable topics in the entire paper. The procedure is mechanical: build the activity network from the precedence table, forward scan for earliest times, backward scan for latest times, compute float, identify the critical path. The only real skill is being neat with the diagram and the table of values, so that markers can follow your work.
This guide covers everything you need: building the network, the scanning algorithms, computing float, identifying the critical path, and Australian-context worked examples.
What is critical path analysis
Critical path analysis is a project management technique used to:
- Compute the minimum possible duration of a project given the dependencies between its activities.
- Identify which activities are critical (cannot be delayed without delaying the whole project).
- Identify which activities have slack and can be delayed by some amount without affecting the project end date.
It is used in construction, software engineering, event planning, manufacturing rollouts, and any project with multiple interdependent tasks.
The activity network
NESA uses the activity-on-edge (AOE) convention:
- Vertices (nodes) represent events. An event is a state of completion, such as "Activity A complete and Activity B can begin".
- Edges (arrows) represent activities. Each activity is labelled with its name and its duration.
- The graph is directed: edges have arrows showing which event comes before which.
- The graph is acyclic: there are no cycles (a cycle would mean activities circularly depend on each other, which is impossible).
Building the network from a precedence table
A precedence table lists each activity, its duration, and its immediate predecessors. To build the network:
- Identify activities with no predecessors. These start at the project-start node.
- For each activity, find the event where all its predecessors have just finished. This is the start node for the activity.
- Draw the activity as an arrow from its start node to a new (or shared) end node.
- Continue until all activities are drawn. The project-end node is where the activities with no successors terminate.
You may need dummy activities (zero-duration edges) to enforce precedence without introducing false connections. Standard 2 questions usually avoid these.
Forward scanning (earliest times)
Label each event with the earliest time at which it can occur. This is the EST (earliest start time) of any activity that starts at that event.
The algorithm:
- Start event: EST = .
- For each other event, EST is the maximum over all activities arriving at that event of (EST of activity's start event + activity's duration).
Take the maximum because all predecessors must finish before the event can occur.
After the forward scan completes, the EST of the project-end event equals the minimum possible project duration.
Backward scanning (latest times)
Label each event with the latest time it can occur without delaying the project. This is the LFT (latest finish time) of any activity that ends at that event.
The algorithm:
- End event: LFT = minimum project duration (from forward scan).
- For each other event, LFT is the minimum over all activities leaving that event of (LFT of activity's end event activity's duration).
Take the minimum because the event must complete in time for the earliest required successor.
Per-activity calculations
For an activity from event to event with duration :
- EST (earliest start time) =
- EFT (earliest finish time) =
- LFT (latest finish time) =
- LST (latest start time) =
- Float = LST EST = LFT EFT =
The critical path
The critical path consists of all activities with float = . These activities cannot be delayed without delaying the project. The critical path is the longest path through the network.
If two or more paths tie at the longest length, all of them are critical.
A project to renovate an Australian kitchen has these activities:
| Activity | Duration (days) | Predecessors |
|---|---|---|
| - Demolition | None | |
| - Plumbing rough-in | ||
| - Electrical rough-in | ||
| - Floor laying | ||
| - Cabinet installation | , , | |
| - Tiling and painting | ||
| - Final inspection |
Step 1. Identify the events from the precedence table.
Each event is a moment when one set of activities has just finished and the next set can begin. Reading down the predecessor column gives six events: project start, after , after the parallel trio , and , after , after , and project end.
- Event : project start.
- Event : after (so , , can begin).
- Event : after , and (so can begin).
- Event : after (so can begin).
- Event : after (so can begin).
- Event : after (project end).
Step 2. Forward scan, event by event, taking the maximum at every join.
At each event we take the maximum over all incoming activities. The maximum is the earliest moment every predecessor has finished, which is what an event represents.
- Event : EST .
- Event : only arrives, so EST .
- Event : three activities arrive, so EST , with the maximum coming from .
- Event : only arrives, so EST .
- Event : only arrives, so EST .
- Event : only arrives, so EST .
Minimum project duration is therefore days.
Step 3. Backward scan, event by event, taking the minimum at every fork.
The backward scan starts at the project end and subtracts activity durations. Where one event has multiple activities leaving it we take the minimum, because each successor must start in time for the project to finish on schedule.
- Event : LFT .
- Event : LFT .
- Event : LFT .
- Event : LFT .
- Event : three activities leave, so LFT , with the minimum coming from .
- Event : LFT .
Step 4. Build the per-activity table, including float.
Float for each activity equals , where is the start event, is the end event, and is the duration.
| Activity | Duration | EST | EFT | LST | LFT | Float | Critical? |
|---|---|---|---|---|---|---|---|
| Yes | |||||||
| No | |||||||
| No | |||||||
| Yes | |||||||
| Yes | |||||||
| Yes | |||||||
| Yes |
Step 5. State the critical path and slack explicitly.
The critical activities (zero float) form the longest path through the network.
Answer. Critical path , minimum duration days. Plumbing has day of slack and electrical has days of slack, so both can be delayed by their float amount without pushing the project end date.
A simplified Sydney apartment build:
| Activity | Duration (weeks) | Predecessors |
|---|---|---|
| - Foundation | None | |
| - Structural frame | ||
| - External walls | ||
| - Roofing | ||
| - Plumbing | , | |
| - Internal finishes |
Step 1. Map the events from the precedence table.
After the foundation and frame we get a parallel branch where roofing and external walls both depend on the frame but neither depends on the other. They rejoin at the start of plumbing.
- Event : project start.
- Event : after .
- Event : after (so and can begin in parallel).
- Event : after and (so can begin).
- Event : after .
- Event : project end (after ).
Step 2. Forward scan.
Take the maximum at the join where and both arrive at event , because event cannot occur until both finish.
- Event : EST .
- Event : EST .
- Event : EST .
- Event : EST via .
- Event : EST .
- Event : EST .
Minimum project duration is weeks.
Step 3. Backward scan.
Take the minimum at the fork where and both leave event , because both must start in time for event to be reached by its LFT.
- Event : LFT .
- Event : LFT .
- Event : LFT .
- Event : LFT via .
- Event : LFT .
- Event : LFT .
Step 4. Compute float per activity.
| Activity | Float () | Critical? |
|---|---|---|
| Yes | ||
| Yes | ||
| No | ||
| Yes | ||
| Yes | ||
| Yes |
Answer. Critical path , minimum duration weeks. External walls has week of slack and can drift by up to week without delaying handover.
A school musical has the following partial precedence table:
| Activity | Duration (days) | Predecessors |
|---|---|---|
| - Casting | None | |
| - Set build | ||
| - Costume making | ||
| - Rehearsals | , | |
| - Final dress run |
Find the float of costume making and explain what it means in plain language.
Step 1. Establish the events and run a forward scan to find EST values.
We need the EST of the event where starts and the EST of the event where it finishes, so we run the full forward scan.
- Event (start): EST .
- Event (after ): EST .
- Event (after and , before ): EST via .
- Event (after ): EST .
- Event (project end): EST .
Step 2. Run a backward scan to find LFT values.
Minimum project duration is days, so LFT at event is .
- Event : LFT .
- Event : LFT .
- Event : LFT .
- Event : LFT via .
- Event : LFT .
Step 3. Apply the float formula to activity .
Costume making runs from event () to event () with duration . The float formula is .
Step 4. Translate the answer into project language.
A float of days means costume making can be delayed by up to days from its earliest start (or its finish can slip by days) without delaying the dress run on day . If the costumes slip a fourth day they push back rehearsals and therefore the final project finish.
Answer. Float of is days. The costume team can absorb up to a -day delay without pushing the show date.
A given activity network has the following labelled events (the diagram is described in the question, you are not asked to draw it).
| Activity | Edge (events) | Duration (hours) |
|---|---|---|
Find the critical path and the minimum project duration.
Step 1. Identify all paths from event to the project end ().
Reading the edges, only one path passes through event and one passes through event . They rejoin at event , then a single activity leads to event .
- Path 1: via events .
- Path 2: via events .
Step 2. Compute the length of each path.
The critical path is the longest from start to end. Add the durations along each path.
- Length of Path 1: hours.
- Length of Path 2: hours.
Step 3. Compare the two lengths and identify the critical path.
Path 2 is longer, so it is the critical path. Every activity on it has zero float.
Step 4. Confirm by computing float on Path 1.
Take for example. EST at event is (from ), and LFT at event is (event less duration of ). So float of is hour. Path 1 is not critical, which agrees with our path-comparison answer.
Answer. Critical path () with minimum project duration hours.
Dummy activities
Most Standard 2 networks can be drawn with one activity per edge, but sometimes two activities share some of their predecessors and not others, and a plain activity-on-edge diagram cannot capture that. The fix is a dummy activity: a zero-duration edge, drawn dashed, that carries a dependency from one event to another without representing any real work.
Take this project, where activity must wait for both and , but activity waits for only:
| Activity | Duration | Predecessors |
|---|---|---|
| None | ||
| None | ||
| , | ||
| , |
If you simply ran and into one shared event and started both and from it, you would wrongly force to wait for as well. Instead, give and separate end events, then add a dummy from the end of across to the end of . Now leaves the end of (so it needs only), while leaves the end of , which the dummy has tied back to as well (so needs both).
Figure 2. The dashed arrow is the dummy: zero duration, so it adds a dependency without adding time. It lets depend on both and while still depends on alone.
The scan runs exactly as before; the dummy passes the earliest and latest times across with no duration added. Forward and backward scanning produce the per-activity boxes shown, giving the critical path with a minimum duration of . Activity has units of float, and and each have .
When you need a dummy. Reach for one whenever two activities have overlapping but different predecessor lists, or whenever two activities would otherwise share the same start and end event (every activity needs its own unique pair of events). If neither situation applies, you do not need a dummy.
Exam strategy
Layout
The HSC marker wants a clean layout. Standard approach:
- Draw the activity network with all activities and durations labelled.
- Label each event with EST and LFT (a two-number tag at each node).
- Compute float in a table.
- State the critical path and the minimum duration explicitly.
Common loss-of-marks
- Skipping the network diagram and just listing paths. Markers want the network.
- Wrong max/min direction in the scans. Forward scan uses MAX over predecessors; backward scan uses MIN over successors.
- Mislabelling events with EST as LFT or vice versa.
- Forgetting that float = LFT EST duration. Easy to forget the duration subtraction.
- Stating the shortest path as critical. The critical path is the LONGEST.
Speed tactics
CPA questions usually have a fixed format. Once you have practised the scanning routine, it should take - minutes for a - mark question. Drill the routine in Term 2 of Year 12, before HSC trials, so it is automatic.
What CPA does not cover
CPA assumes activity durations are known exactly. In real projects, activities take variable amounts of time, and project management uses tools like PERT (Programme Evaluation and Review Technique) to handle uncertainty. NESA Standard 2 does not test PERT.
CPA also does not handle resource constraints (e.g. two activities cannot use the same crane at the same time). Real project management software handles these; HSC Standard 2 does not.
Check your knowledge
Try these before checking the worked solutions. They progress from quick recall to a full network walkthrough.
- For an activity with EST , LFT and duration , what is the float?
- The forward scan of a network gives the project-end event an EST of days. What is the LFT of the project-end event?
- Three activities arrive at event : from event (duration , EST of event is ), from event (duration , EST of event is ), and from event (duration , EST of event is ). What is the EST of event ?
- Two activities leave event : (duration , ends at event with LFT ) and (duration , ends at event with LFT ). What is the LFT of event ?
- Activity has EST , EFT , LST and LFT . Is on the critical path? Justify briefly.
- A small project has activities (duration , no predecessors), (duration , predecessor ), (duration , predecessor ) and (duration , predecessors and ). Find the minimum project duration and the critical path.
- For the project in question , find the float of activity and state in one sentence what it means.
- A network has two paths from start to finish: path with durations and path with durations . Which is critical, and what is the minimum project duration?
These eight questions cover float calculations, EST and LFT rules, forward and backward scanning, and identifying the critical path. Work through each in order.
Step 1: Q1. Calculate float given LFT, EST, and duration
Float measures how long an activity can slip before it delays the whole project. The formula is Float .
The activity can be delayed by time units without pushing the project finish.
Step 2: Q2. Find the LFT of the project-end event
The backward scan always sets the LFT of the project-end event equal to the minimum project duration found by the forward scan. This ensures the project can finish on time.
Step 3: Q3. Compute EST(7) with three incoming activities
An event cannot occur until all its predecessors have finished. The EST is therefore the maximum over all incoming "EST of predecessor plus duration" values.
Step 4: Q4. Compute LFT(3) with two outgoing activities
An event must be early enough for all its successors to start in time. The LFT is the minimum over all outgoing "LFT of successor minus duration" values.
Step 5: Q5. Determine whether activity is on the critical path
Float = LST EST. If float is zero the activity is critical; if positive it has slack.
Float is , which is non-zero, so is NOT on the critical path and has time units of slack.
Step 6: Q6. Forward scan for a four-activity project
Identify the events: event (start), event (after , duration 3), event (after duration 5 and duration 4), event (project end after , duration 2). Propagate the earliest times from left to right, taking the maximum when multiple paths arrive.
Minimum project duration is days. The longest path is , so the critical path is .
Step 7: Q7. Backward scan and float of activity
Start from the project-end event (LFT ) and propagate rightward to left, taking the minimum when multiple paths leave. Then compute float as .
Activity can be delayed by up to day without delaying the project.
Step 8: Q8. Identify the critical path by comparing total path lengths
The critical path is the longest path from start to finish, because every activity on it must run in sequence and cannot be overlapped.
Length of path : time units.
Length of path : time units.
Final answer: path is longer, so is the critical path and the minimum project duration is time units.