Nobody on your team is really full-time on one project. Axioplan puts fractional FTE allocation directly on the Gantt — 30% architects, shared QA, support rotas — so the end date reflects the availability you actually have.
Assign people or roles to tasks with an allocation percentage, and let the schedule do the arithmetic. The failure mode this prevents is the oldest one in project management: a plan that assumes uninterrupted focus from people who are 40% elsewhere.
Allocate anyone at any percentage. A 40-hour task takes a week at 100% and two and a half weeks at 40% — Axioplan schedules from allocation, so the bars stretch to match reality.
Attach a required role and a rate to each task. Get timeline and cost forecasts while the team is still hypothetical, then swap in real people without rebuilding the plan.
See only the architect's lane, or everything QA touches. Capacity conversations get much shorter when everyone is looking at the same filtered view.
Once allocation lives on the Gantt, capacity questions become schedule operations instead of week-long email threads.
Drag the milestone. The Gantt shows which allocations break — and P85 shows what the compressed date does to your delivery confidence.
Change one allocation. Every task she touches stretches, dependent tasks shift, and the new end date appears — while you're still on the call.
Model it against the same team. Overallocation shows up as a number, not as a surprise resignation two months in.
The estimates behind those confidence dates come from PERT three-point estimation — try the math yourself with the free PERT calculator, or read how dependencies, resources and costs fit together in one plan.
Common questions about resource allocation on Gantt charts.