Capacity across projects
One person’s total commitment, regardless of which project each piece of it came from.
Resource planning
Capacity, utilisation and conflicts across projects. This solution is in development — here is what exists today and what is coming.
What already works today
Resource planning does not start from zero. Project planning already carries most of the raw material it needs:
- Assignments — tasks assigned to employees, per project
- Skills and absences — recorded, and honoured when the AI assigns work
- Utilisation view — how heavily people are booked over a project’s plan period
What is missing is the cross-project view: one person, all of their commitments, in one place.
What is coming
Scope is not frozen yet — which is exactly why input from teams with the problem is worth more than our guesses right now.
Overbooking made visible
Where assignments add up to more than the available time — before the missed deadline points it out for you.
Skill-based staffing
Who can actually do a task, not just who happens to have time.
Absences as part of capacity
Leave and other absences as a first-class input to the calculation, not a footnote next to it.
Where the AI will come in
Within a single project the plan assistant already assigns people while accounting for their skills and absences. Extending that to a cross-project capacity view is the natural next step — on the same principle: it proposes, you decide.
Is this your problem?
Then it is worth telling us now, while the scope is still open. Concrete requirements from a real team weigh more than our assumptions.