Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
See what actually drives your finish date.
Set milestones, wire up task dependencies, and read your whole plan on a Gantt timeline — with the critical path highlighted automatically and a baseline that shows how far you’ve drifted. Scheduling that answers the only question that matters: what has to happen next?
Milestones
Mark what matters
Dependencies
Finish-to-start, cycle-safe
Gantt timeline
Today line + variance
Critical path
Computed for you
What's shipped
Planning that a delivery lead can trust.
Every capability below is live and runtime-verified.
Milestones
Mark the moments that matter — a beta, a go-live, a hand-off — each with a due date and an open / met / missed status, shown on the project and along the timeline.
Task dependencies
Declare finish-to-start links (“this can’t start until that finishes”). A “blocked by” and “blocks” view on every task makes the chain explicit.
Cycle protection
The dependency graph is guarded: a link that would create a loop — directly or transitively — is rejected before it’s saved.
Gantt timeline
Task bars scaled across the project’s date window, a live “today” line, and a per-bar dependency count so you read the plan at a glance.
Critical path
A full forward/backward pass computes early/late start and finish and slack, then highlights the zero-slack path in red — the tasks that actually move the finish date.
Baseline & variance
Snapshot the current plan as a baseline; the timeline then shows a ghost bar and an ahead/behind day count so slippage is visible, not hidden.
Not just pretty bars
The critical path is calculated — not guessed.
Most Gantt views just draw bars. AWRA runs the classic critical-path method over your dependency graph: a topological order, a forward pass for earliest start/finish, a backward pass for latest, then slack. Tasks with zero slack are the critical path — delay one and the whole project slips.
- Early start / early finish from a forward pass along dependencies.
- Late start / late finish from a backward pass from the project end.
- Slack per task — how long it can slip without moving the finish.
- Zero-slack tasks highlighted as the critical path on the timeline.
Illustrative. Red bars are on the zero-slack critical path.
From plan to control
Four steps to a plan you can defend.
Schedule
Give tasks start and due dates and set milestones.
Sequence
Add finish-to-start dependencies; cycles are blocked.
Baseline
Snapshot the plan so drift becomes measurable.
Track
Read the timeline, watch the critical path and variance.
Questions
The practical details.
What dependency types are supported?
Finish-to-start — the most common and clearest link. A task can be blocked by many others, and cycles (including transitive ones) are rejected before they’re created.
Do I have to fill in dates for the Gantt to work?
Bars are drawn from task start and due dates; tasks without dates simply don’t plot on the timeline. The critical-path calculation uses whatever schedule you’ve entered.
What is a baseline for?
It freezes the current plan so you can measure drift. After you set a baseline, the timeline shows a ghost bar and an ahead/behind day count per task.
Are the dependency arrows drawn on the chart?
Dependencies are shown as a count on each bar and as full “blocked by / blocks” lists on the task page; literal arrow-drawing on the chart is a visual polish item on the roadmap.
Does this need a special plan?
Planning & Gantt is part of the Projects & Tasks pillar, available from the Basic plan up.
Where does this sit in the roadmap?
It’s live, alongside Task Management, Agile Delivery, and Time, Budget & Flexibility — see the Projects & Tasks overview.
Help Center
Need a quick answer while you read?
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.