Projects
Kalends has what you expect from a project tool: a board, phases, dependencies and status reports. The difference is that the project sits beside the routines the same people have to keep up with, so collisions show in time.
30 days free · 40% off until year-end · Watch-only members always free
Sound familiar?
The plan lives in the project tool, the recurring commitments in calendars and spreadsheets. Each tool works on its own, but nobody sees both at once. The collision only shows when a control is missed or a close runs late.
The migration was planned in the project tool and the year-end close in someone's calendar. Nobody noticed they landed in the same weeks.
With Kalends
The phases sit on the same timeline as the closes and the year-end freeze.
The plan and the status lived in one person's head and inbox. Three weeks of sick leave became three weeks of standstill.
With Kalends
The project has an owner and a deputy, and its status lives in the project rather than in one person's inbox.
Every month someone rebuilds the same slide deck, and it is out of date before the meeting starts.
With Kalends
The owner reports the status in the project, and the steering group reads it themselves as watch-only members, at no cost.
How a project works in Kalends
Board, timeline, results and status reports in one project. Everyone works in the view that suits them and sees the same thing.
Tasks
Each project decides its own columns, such as Waiting for supplier. Move the cards as the work progresses and filter by person, label or phase.
Timeline
Group the tasks into phases and link what waits for what. Holidays and the organisation's closures show right on the timeline, so nobody plans a migration in the middle of the year-end freeze.
Results
Add what the project must achieve: deliverables, metrics and conditions. Everyone can see what is done and what remains, and when the project closes you assess what it led to.
Status reports
The owner reports the status in the project: on track, at risk or off track, with a few lines on what has happened. The steering group reads the report in Kalends instead of in a slide deck, and questions go to the discussion beside the work.
What a standalone project tool cannot see
A project tool knows what needs doing in the project. Kalends also knows what else the same people are responsible for, who takes over and which goal the project is meant to reach.
The project's period, the closes, the audits and the board meetings appear in the same view. Collisions show before they happen.
Tasks without an owner of their own fall to the project owner until they are delegated. If someone leaves, the project responsibility is handed over instead of left behind.
Connect the project or individual tasks to a goal's results, so the work meant to get you there is visible.
Ask Kalends
Describe the change and the assistant suggests phases, tasks, dependencies and measurable results. Untick what you don't want and confirm.
As the project runs, it can move a date together with everything waiting for it, or draft this week's status report.
More about AI in KalendsThe assistant uses your own AI provider.
Get started
Start with what you know and fill in as you go. Dates and results can wait until you are ready.
Choose the area, the owner and a deputy. Type the time frame as q4, 6w or 5/10–18/12.
Add the tasks on the board or the timeline and group them into phases.
Add the deliverables, metrics and conditions the project will be measured on.
Report the status and update the results while the project runs.
Kalends suits the projects that change the organisation. Some work still belongs in other tools.
A good fit for
Belongs somewhere else
Software development in sprints
Keep your development tool for pull requests and issue flows. Kalends becomes the place for the initiatives and goals above them.
Time reporting
Tasks have estimates, but Kalends does not record time.
Documents
Kalends is not a document archive. Link to the material where it already lives.
Common questions
Cannot find the answer?
For projects that change the organisation, yes: a board, phases, a timeline with dependencies, labels, estimates, results, status reports and discussion. If you build software in sprints, keep your development tool for that work.
No. Watch-only members are free and unlimited on every plan. They see what a member sees but cannot be assigned tasks or change anything.
Yes. Connect the project or individual tasks to the goal's results. The contribution shows which work is meant to get you there, but never updates a result automatically.
You see which tasks are waiting for it. When you move it, the waiting tasks can be pushed back as far as needed, moved by the same number of days or left where they are. If they stay, the conflict shows in red.
Yes. A project can have subprojects that inherit its area, and phases that group the tasks with a time frame of their own.
The project responsibility is handed over to someone with access to the area. Tasks without an owner of their own follow the project, and the history stays.
Yes. The project belongs to an area and follows its permissions. Anyone without access to the area does not see the project.
No. The Kalends plan has no limit on the number of projects and goals.
More in Kalends
Start with one project
Try Kalends for 30 days with one of your own projects and see it beside the routines and goals it affects.
30 days free · 40% off until year-end · Watch-only members always free
