Resource & capacity
Plan people against the work that actually exists.
Capacity planning fails when demand is guessed. Aria builds demand from the plans, assignments and tasks already in the system, then shows it against real working patterns so over-allocation is visible before it becomes a delivery problem.
Schedule, capacity and people
Three connected views: a schedule showing who is on what and when, a capacity view showing where demand exceeds available hours, and a people view for the detail behind an individual.
Demand comes from committed project work — assignments and tasks with estimated effort — measured against each person's working pattern rather than a flat assumption about a working week.
Demand
- Project assignments
- Task-driven demand from estimated effort
- Optional tentative demand from the pipeline
- Forward view across coming weeks
Supply
- Working patterns per person
- Available capacity
- Utilisation
- Over-allocation, surfaced rather than buried
See tomorrow's problem before it becomes today's shortage
Committed work is only half the picture. Aria can overlay tentative demand from expected work so operations can understand the shape of the next few weeks before something becomes a signed commitment.
The overlay is a toggle, not an assumption: turn pipeline demand off to see only what is committed, on to see what would happen if expected work lands. Aria does not recommend who to hire — it shows where the pressure sits so a person can decide.
Connected to delivery, not separate from it
Because capacity is built from the same project records as delivery, moving a phase changes the capacity picture, and a capacity conflict is traceable back to the projects creating it.
That is also what makes reassignment decisions realistic: the question is not only whether someone is free, but whether the work they would leave behind is itself at risk.
Where this connects
See it against your own work
A short walkthrough using a project you recognise beats any feature list.