The tasks system
The task that knows where it came from
What kills action items is rarely laziness — it is the absence of an owner: a written item nobody owns is never done and never asked about. The task system here is built on the premise that every item has a name, a date, a status, and a context you can return to.
What works today
-
A kanban board
Columns by status, drag and drop, and an order that stays exactly where you left it.
-
A list view with filters in the URL
You filter, then copy the link, and your colleague lands on that same view rather than a generic list.
-
A "My day" board
What is overdue and what is due today on one screen you can read in a minute, on mobile too.
-
Spaces and projects
A committee, a department or a project — and permission follows the place rather than being granted task by task.
-
Comments and mentions
Mentioning a colleague makes them a watcher, so what happens reaches them without asking and without being added by hand.
-
Quick capture
Write the task as one sentence containing the owner, the date and the priority, and Diwan reads it without a form full of fields.
Decisions this screen was built on
A task stays attached to its source
An item born in a set of minutes carries the link to those minutes for as long as it exists. So when someone asks "why are we doing this at all?" three months later, the answer is one click rather than an investigation through email.
Filters live in the URL, not in the session
View state is part of the link, so it can be shared as-is, bookmarked, and returned to unchanged. A view that lives only in the browser session cannot be shared, so it gets rebuilt from scratch every time.
Nobody demotes themselves, and no project is left without an owner
Permissions are built on the premise that the risk is in demotion, not promotion: a guard prevents an organisation or a project from being left without an active owner, checked on both routes — removing the role and suspending the account.
The thread that makes it one product
Separate tools force you to be the thread: you copy an item from the minutes into the task app, upload the file to a third folder, then hold the connection between them in your head. And when the person who remembered leaves, the connection leaves with them.
- Meetings An agenda written before the session, minutes recorded during it rather than a week later, and a decision log that stays searchable long after everyone has forgotten the details.
- Knowledge Center A file does not live alone: it is linked to the meeting where it was discussed, the decision it produced and the task it was attached to. Whoever joins a year from now finds the context, not just the file.
- Capabilities Exactly what works in Diwan today: three systems on one record — the meeting knows its tasks, the task knows its minutes, and the file knows its decision.
Questions about tasks
Can we use tasks without meetings?
Yes, they work perfectly well on their own. But what most distinguishes them is their link to the minutes they were born in, and that starts at the meeting.
Is there a limit on the number of tasks?
No. What is limited is the number of committees and projects on the free plan alone, and the number of active users. Tasks themselves have no cap on any plan.
Do notifications arrive for every event?
No. A notification for what concerns you — an assignment to you or a mention of your name — and an email digest for the rest. Flooding people with notifications trains them to ignore notifications.
Ask us about your specific case
We run one session with you in under an hour, and we will tell you plainly if Diwan is not right for you.
Start free