Feature · Tasks

A work breakdown that comes from the plan

A large project is only manageable once it is broken down. Projektiassistent derives the tasks from the project plan and lets you split them into subtasks as deep as you need — so every activity is tied to an objective rather than floating on its own.

01 / What you get

A task is more than a line on a list

Every task carries its context: who owns it, what has to be finished first, and how long it is expected to take.

🧩

Subtasks and WBS

A hierarchical structure — every task can contain subtasks, producing a work breakdown structure you can actually track.

🎚️

Priorities

Four levels: low, medium, high, critical. Important work stands out from the list immediately.

👤

Owners and deadlines

Every task gets an owner and start and end dates. Clear division of work without a separate spreadsheet.

⏱️

Estimate vs actual

Estimated time next to what was actually spent. Every project makes your next estimate sharper.

02 / Connectedness

Tasks do not live in a separate file

The same work appears in the Kanban board, the Gantt chart and the report. Change it in one place and the rest follow.

  • Comments on the task

    Team discussion stays in context instead of an email thread. The background is still there later.

  • Linked to milestones

    Tasks can be tied to milestones — a clear line between daily work and the big checkpoints.

  • Buffers and lag time

    Lag and buffer periods between tasks make the schedule realistic rather than optimistic.

Work breakdown12 / 18
1. Preparation — done
2. Analysis — done
3.1 Prototype — done
3.2 Testing → in progress
4. Handover → pending
03 / Views

The same breakdown, in the view that suits you

A list, a board or a timeline — the choice of view does not change the work itself, only how you see it.

WBSSubtasksPrioritiesOwnersEstimatesCommentsBuffersMilestones
04 / FAQ

Frequently asked questions

What is a work breakdown structure (WBS)?

A WBS splits a project into hierarchical parts where each level refines the one above: project → phase → task → subtask. The goal is to reach a level where each piece of work can be estimated, assigned and tracked.

How deep can tasks be nested?

As deep as the project requires. In practice two or three levels is enough for most projects — go deeper and you spend more time on administration than on the work.

Are tasks created automatically?

Yes. From the project description the AI drafts a first task list with phases, priorities and estimates. You edit it from there — faster than starting from a blank page.

Do I have to enter estimates?

Not required, but worth it. Comparing estimated with actual time is the only way planning for the next project genuinely improves.

Get started

Break your project down

14 days free — all Pro features, no card required.

Start for free →