---
title: "Critical path"
canonical: "https://support.appfire.com/space/SPM/1918405060/Critical%20path"
format: markdown
---
> Macro (aura-html)

## About the critical path

The critical path is based on dependencies. It represents the longest sequence of tasks that determines the project duration.

This feature highlights all the tasks on the critical path with a red color. Tasks on the Critical path will also be listed in the Gantt Infobar.

To highlight the entire sequence, you must define dependency links between tasks. Only the strong links that impact scheduling will determine the tasks on the critical path.

See more about the critical path in the video.

Critical path is supported in own scope, sub-scope, and none-scope boxes.

Once you establish task dependencies, the App will automatically draw the Critical path.

To display it, click **View** > **Critical Path**.

![Visibility drop-down menu, Critical path option](media://4d16ca60-c54c-44f6-8c57-f033e6e8262f)

> Macro (excerpt)
> 
> The critical path is drawn for:
> 
> - tasks with start and end dates
> - tasks with one date (either start or end date)
> 
> When many tasks are linked by dependencies on the critical path, and one of the tasks loses start and end dates, the critical path may be disrupted. Once the task has dates assigned again, the critical path will appear.
> 
> ![critical-path-row.png](media://f160c1f8-5752-4b0e-9e79-437eab130693)

### Dependency path calculation

<span style="color: #455264">Use strong dependencies</span><span style="color: #455264">** **</span><span style="color: #455264">to determine the correct order of task</span><span style="color: #455264">**s**</span><span style="color: #455264">. </span>

- The path is calculated from the end (the last task(s) in the project).
- The algorithm works backward, looking for strong links connecting tasks.
- The most direct path (without a time gap between tasks) is highlighted.
- A gap between tasks is allowed only if an ASAP link has the [lag time](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918406747) added.

![critical-path-diagram.png](media://e5a15791-2cde-4c9a-90f3-ed54e213183b)

## <span style="color: #455264">Non-working days</span>

<span style="color: #455264">The non-working days do not affect the critical path calculation. This means that if there are two tasks with a dependency on the critical path and the predecessor ends before a non-working day, the App will move the successor to start on the first working day, and both will remain on the critical path:</span>

![critical-path-dependencies.png](media://d59580b3-8ad4-40ec-b441-6a9cfc97b1a2)

## <span style="color: #455264">Critical path tab</span>

<span style="color: #455264">Tasks that are a part of the critical path are listed in the </span><span style="color: #455264">**Infobar**</span><span style="color: #455264"> > </span><span style="color: #455264">**Critical Path**</span><span style="color: #455264"> tab.</span>

![Critical path - Infobar tab.mov](media://6ea9da9b-3793-4f52-bb87-3c397f50260d)

### Export

> 📝 Requires [BigTemplate](https://appfire.atlassian.net/wiki/spaces/BTc).

The critical path can be exported to an XLSX file from the Infobar tab. 

![image-20251119-182758.png](media://212baee2-2916-41df-9078-9c27279fd6e8)

![image-20251119-183258.png](media://5b1c0e49-aec3-42df-897c-8ce2208db0a0)