AWRA OpsHub Search

AWRA Help Center

Copy link
Help Workflow Support
01 Agile Delivery Projects & Tasks 02 Time, Budget & Flexibility Projects & Tasks

Planning & Gantt

Turn a list of tasks into a schedule you can defend: milestones, dependencies, a Gantt timeline, and an automatically computed critical path that shows what actually drives your finish date.

Open a project and choose Timeline to see the Gantt view. Task bars are scaled across the project's date window with a live "today" line, and each bar shows how many dependencies it has. Milestones appear along the timeline as fixed points to plan toward.

Milestones

Add milestones to mark the moments that matter — a beta, a go-live, a hand-off. Each has a due date and an open / met / missed status, shown on the project detail and along the timeline.

Task Dependencies

On any task, add a finish-to-start dependency — "this can't start until that finishes". The task page shows a Blocked by and Blocks view so the chain is explicit. The dependency graph is guarded: a link that would create a cycle, directly or transitively, is rejected before it is saved.

The Critical Path

AWRA runs the classic critical-path method over your dependencies — a topological order, a forward pass for earliest start/finish, a backward pass for latest, then slack per task. Tasks with zero slack form the critical path, highlighted in red on the timeline: delay one and the whole project slips.

TermMeaning
Early start / finishThe soonest a task can start/finish given its dependencies.
Late start / finishThe latest it can start/finish without delaying the project.
SlackHow long a task can slip before it moves the finish date.
Critical pathThe zero-slack chain that determines the finish date.

Baseline & Variance

Use Set baseline to snapshot the current plan. The timeline then shows a ghost bar and an ahead/behind day count per task, so slippage becomes visible instead of hidden. See also Agile Delivery for an iteration-based cadence over the same tasks.

Need help with this topic?

Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.

Open support guide