One board, your workflow

One board, grouped by status

Tasks sit grouped under the statuses you configured, in your order. It is not a kanban that fans out into columns — it is sections in the same list you use everywhere: terminal sections start folded, and sorting orders rows within a section, never across them. You filter by client, project, assignee, status, label, free text and by deadline (overdue, today or this week), and you choose which columns are visible (labels, assignee, priority, due date, checklist), saved per person. Under the list is the same pager as everywhere else: never the first two hundred rows with an apology attached.

Statuses, labels and priorities on your terms

The set of statuses is not a fixed list in code but tenant data under Instellingen → Taakstatussen: rename, reorder, recolour and extend it. Labels are managed under Instellingen → Taaklabels, org-wide and with their own colour, and you can create one without leaving the task. A high-priority task reads in loud red everywhere. So the board speaks your studio's language, not the one we happened to ship.

• Default status: where a new task lands.
• Terminal status: marks the task finished and stamps its completion time.
• Required contact moment: a status can demand a linked interaction, so 'done' can be made to mean 'discussed with the client'.

Checklists, comments and the client looking in

Every task carries checklists; progress shows as n/m on the card and in every list, turning green once everything is ticked. Items have a title and a markdown description, so the how sits with the what, and ticking the last one prompts you to finish the task there and then. A checklist you reuse goes into the org-wide library and drops onto the next task in one click. In comments you mention a colleague or a client's contact with @ and reference another task with #; editing and deleting are allowed, with an "edited" marker attached. A task can even be assigned to the client's contact person when they are the one you are waiting on, and "Zichtbaar voor klant" (off by default) lets a portal contact of that client see the task and comment on it. Links and real file attachments belong to it too.

Templates: define once, apply anywhere

Recurring work (onboarding, a monthly delivery) is captured as an org-wide task template under Taken → Sjablonen: tasks with a priority, a relative due date, a time budget, a checklist and, where you want one, a required contact moment. Apply it to a client by hand, let it fire automatically the moment a client enters a given status, or attach it to a subscription type, so the first activation of a new retainer puts the onboarding on the client itself. So every engagement starts complete, not from a blank board.

• Apply by hand, or automatically on a client status or a first subscription activation.
• Due dates count from the apply date, plus so many days.
• Assignment follows the client's current responsible, not a name fixed when it was written.

Work that comes back, and work you plan

A task may repeat itself: daily, weekly, monthly, quarterly or yearly, in one of two modes. "Na afronden" creates the next one only when you tick this one off, which suits work that follows on; "Op schema" creates it on the interval whether the last is finished or not, which suits a monthly report that has to go out regardless. Labels and checklists move along to the next one. And a deadline is not a plan: "Taak inplannen" puts one or more real time blocks on the calendar (date, start time, duration, note), for yourself or, with the right permission, for a colleague. Those blocks sit in the shared Agenda, drag to another day, mirror to your own Google Calendar, and a block that has passed offers "Uren registreren", which is where the real time entry comes from. Beside the per-task time budget, which reads against logged time as "x left" or "x over budget", a daily check announces what is overdue and what falls due within each colleague's own threshold.

Overdue is loud, and everything lands in the trail

Work past its date is loud red everywhere: on rows, in counts and on the dashboard widgets, so it never fades into the list. Pushing a deadline back asks for a reason, and that reason goes into the trail alongside the new date. Every meaningful change lands there: created, moved status, commented, checklist item ticked, attachment added, spawned from a recurrence or a template. The actor's name is a snapshot, so a departed colleague's work never quietly becomes "the system", and whoever was signed in on someone else's behalf is named beside it. The ✎ in the toolbar changes status, assignee, priority, project, client or deadline across a whole selection; a row that may not be touched (someone else's task, a status that first demands a contact moment) is reported rather than failing the batch. Export always works; import deliberately only creates, because task titles legitimately repeat and an invented key would overwrite the wrong row.