Gantt chart and dependencies
Phases, tasks and subtasks on a timeline with the dependencies between them. Moving a task shows what it drags along.
Project planning
Phases, tasks and subtasks with a Gantt chart, dependencies, assignments and an hour model that makes the gap between plan and reality visible.
The problem it solves
A project plan is easy to draw and hard to keep honest. Effort gets estimated once and never compared with what was actually booked; someone is assigned for a week they are on leave; a task moves and nobody notices which three others depended on it.
- Structure — phases, tasks and subtasks with dependencies
- People — assignments that account for skills and absences
- Hours — estimated, planned and booked side by side
Plainova keeps structure, people and hours in one model, so a change in one of them is visible in the others.
What it does
Plan versions
Several versions per project, exactly one of them active. Compare them, activate one, delete the rest — this is also where AI proposals land.
Hour model
Estimated, planned and booked hours per task. Time is booked in the same place the plan lives, so the comparison is never a separate report somebody has to build.
Assignment with skills and absences
Tasks are assigned to employees against recorded skills and known absences, instead of against an empty calendar.
Per-employee view
The same plan from the other side: what does one person actually have to do, across projects.
Utilisation
How heavily people are booked over the plan period — the first step towards full resource planning.
Risks and scenarios
Risks are ordinary objects with probability, impact, mitigation and status, linked to the project — so they inherit the same attributes, search and workflows as everything else.
At a glance
- Structure
- project → phase → task → subtask
- Views
- Gantt, task grid, per employee
- Hours
- estimated, planned, booked
- Versions
- as many as you like, one active
- AI
- complete plan proposal as a new version
- Risks
- probability, impact, mitigation, status
What it does not do
The parts worth knowing before you plan a project on it.
It does not invent capacity
The schedule is only as good as the skills and absences recorded against your people. An employee whose holiday nobody entered will be planned straight through it.
It will tell you a plan is impossible
If no schedule satisfies every constraint at once, the run says so rather than quietly dropping one. That answer is information — usually a missing skill or more work than there is time — but it is not a plan.
It does not decide priorities for you
Which work matters more is a judgement, and it stays yours. The solver respects the priorities you set; it does not form them.
The AI proposes, it does not commit
A plan proposal arrives as its own version. Nothing in your active plan changes until you activate it — which also means nothing improves until somebody looks at it.
Where the AI comes in
This is the solution the plan assistant works on. You hand it existing unsorted tasks, or just a list of titles the way it came out of a meeting; it proposes phase placement, dependencies, effort estimates, required skills and concrete assignments.
The proposal never overwrites your plan. It is materialised as a new, independent plan version — a full copy with the proposal applied on top — which you open in the normal Gantt view and then activate or delete like any other version.
See it on your own project?
Bring a project you are planning right now — that tells us more in twenty minutes than any demo dataset.