One board, your workflow

The board opens on 'when'

Tasks sit in the sections Over tijd, Vandaag, Deze week and Later (overdue, today, this week, later), with finished tasks folded underneath. Inside a section the earliest deadline comes first, and on the same date the highest priority; every deadline also states the distance, such as '4 days late'. Only overdue and today stand out in colour, so the board stays calm until something really needs you. Prefer statuses? That is one choice under Groeperen, and it lives in the URL. A repeating series shows as one row with '↻ +11' instead of twelve copies of the same title. You filter by client, project, assignee, label, deadline and free text, choose your own columns, and under the list is the same pager as everywhere else. Finish a task and you land back on the board you came from.

Dictated, mailed or typed

Nieuwe taak opens a small dialog that first asks what identifies the task: title, client, deadline and who is on it. Only then does it exist, so a half-thought task never sits on the board as an empty row. With Inspreken you say a task in one go, steps and all, and get a draft with client, project, deadline, priority, labels, time budget and a checklist that you read through whole before anything is saved. And whoever is on the road mails the task address you set under Instellingen → Taken: the subject becomes the title, '[Client]' or lines such as 'klant:', 'voor:' and 'deadline: vrijdag' fill in the fields, a forwarded client mail is filed on the task as a contact moment, and a mail with three jobs for two clients becomes three tasks. If the client cannot be determined, the mail waits under Taken → E-mailinbox and you get a notification.

• Client, deadline and an assignee are required at every door, the API and the import included.
• Dictation up to five minutes, with the transcript on screen so you correct a misheard name yourself.
• The task address is read through the sender's connected mailbox (Google or Microsoft 365): no separate mail server.
• Whatever an AI feature fills in is marked, and never overwrites what you wrote yourself.

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'.

One page, everything editable where you read it

The task page has no separate edit mode: you click the title, a property or the description and change it right there, and a pick from a list is saved at once. Every task carries checklists; progress shows as n/m on the card and in every list, and ticking the last item offers to finish the task. In the Aanpassen met schakl box you type or say what should change ('add a step for the DNS, deadline Friday'), and it is applied as you, under your name on the trail. You paste a screenshot with Ctrl+V, as an attachment or in the middle of the text. In comments you mention a colleague or a client's contact with @ and reference another task with #; a long conversation folds, and a notification about a comment opens exactly that comment. A task can also be assigned to the client's own contact person when they are the one you are waiting on: they then see it in the portal and get an e-mail about it. "Zichtbaar voor klant" (off by default) lets a portal contact see the task and comment on it, and per attachment you decide separately whether the client sees it.

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, optionally on a fixed day such as 'every month on the second Tuesday'. "Na afronden" creates the next one only when you tick this one off; "Op schema" lays out the whole coming year straight away, so you see a quarter ahead of what is coming and can hand work over before it arrives. Hand a task in such a series to someone else and schakl. asks whether that goes for this task or for this one and all following. And a deadline is not a plan: "Taak inplannen" puts real time blocks on the calendar, for one or several colleagues at once, and beside the form you see that day with what is already there, so a double booking shows before you make it. For a colleague you only see 'busy', unless you may read their planning. A recurrence can bring its own blocks along, several per occurrence. The blocks sit in the shared Agenda, mirror to Google or Outlook as 'Client: Task', and a block that has passed offers "Uren registreren".

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; confirming saves the date and the reason together, and the reason goes into the trail. 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 (set, never emptied); 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.