How communities use tasks

In most groups the jobs get agreed in a chat — someone says they will book the hall, three other messages arrive, and a fortnight later nobody is sure whether it happened. Tasks exist to stop that. A job gets a name against it, a date, and somewhere to report progress that is not buried in conversation.

Every task belongs to a community. That is not an administrative detail — it is what makes the whole thing work. Because the task sits inside the community, the people you can assign it to are that community's members, the job appears in the community's list rather than in someone's private to-do app, and it stays visible when the person who created it goes on holiday.

• A task can be narrowed to one sub-group — so the fundraising committee's jobs stay with the fundraising committee.
• A task can be attached to an event, which is how most groups organise who is doing what on the day.
• Whoever is assigned has to accept, so nothing is silently dropped on someone who never saw it.
• Costs are recorded against the job that caused them, which makes the treasurer's life considerably easier.

A typical pattern for a community running an event looks like this:

1. 1

   The committee agrees the event in a sub-group chat, as usual.

2. 2

   An admin creates the event, then creates a task per job — book the hall, order the food, print the badges — each attached to that event.

3. 3

   Each task is assigned to one person with a due date. They accept, and it appears under For me on their Tasks tab.

4. 4

   As work happens, people post updates. Expenses are logged with the amount and a photo of the receipt.

5. 5

   The organiser watches For others and can see at a glance what has moved and what has not.