Where tasks come from
Three sources, and one rule that keeps the board from filling with noise.
Three sources
A post marked as a task
A note you deliberately marked with the composer's task icon. A plain note creates nothing.
An assistant proposal
After you approve it, and carrying the machine mark.
An indicator breach
When an indicator crosses its threshold, a task is raised for its owner naming the worst case.
Why a plain note creates nothing
If every note created a task, the board would fill within a week with things nobody intended to do — and a board full of noise is a board nobody looks at.
A voice note creates none either, because until the transcript lands it has no body. Nor does a document, because a reference to a file is not a description of a task.
An action inside a meeting is not yet a task
In the record Pulse builds from a meeting, actions render with the same task card you see everywhere else in the product — but read-only.
That row lands on nobody's board and cannot be ticked. If something is actually going to be done, it has to be created in its own place.
Every task has exactly one scope
A task belongs to an organisation, or an engagement, or a contact — never to two.
That is structural rather than a convention: the door that creates a task offers no way to name two scopes.
Read this next
- Contacts & engagementsNotes, replies and decisionsThe three things you write into a feed, and how they differ in practice.
- Work, tasks & PulseThe task boardEveryone's tasks, with filters that answer the questions people actually ask.
- IndicatorsBreaches and what happens nextOnce per period, on the card of the work it is about, and only for the person accountable.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.