---
id: KB-TD-003
url: https://app.codecontract.io/help/day-to-day/tasks-and-reminders
idioma: en
categoria: trabajo-diario
subcategoria: tareas
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TD-001, KB-CF-005]
citadoPor: [KB-TD-006, KB-CL-005]
---

# Tasks: what the system will not do for you

_For what depends on a person rather than a document._

**Responde a:** create a task · reminder to call a supplier · assign work to a colleague · so i do not forget to do something

The platform chases documents on its own. What it cannot do is make a phone call, negotiate a deadline, or decide whether a supplier is still worth keeping. Those are tasks, and unwritten tasks get forgotten.

## What deserves to be a task

| Yes | No |
| --- | --- |
| Phone the supplier who has not opened the notice in a month | Remember to request a document (the process does that) |
| Review approval criteria with the team | Remember something expires (the alert does that) |
| Decide whether to close a dead case | Check whether someone signed (the case shows it) |

_If the system can do it or warn you, do not make it a task: it will duplicate what already works._

## The three things that make a task get done

**En corto**

- A concrete verb: "phone", not "Muñoz matter".
- One person, not a team. What belongs to everyone gets done by nobody.
- A real date, not "as soon as possible".

> [!WARNING]
> A task list that grows and never shrinks stops being read, exactly like a full alert inbox. If something has sat three weeks, either do it today or delete it: keeping it there only generates guilt.

> [!NOTE]
> Tasks arising from a case are best created from it: whoever opens it then sees the context without hunting.

**Can I assign a task to someone else?**

Yes, and they are notified.

**Do they close when the case completes?**

No: the task is yours, the case belongs to the process. Close it by hand.

**Are they good for recurring work?**

For anything that repeats, a process or an expiry alert is better.

## Ejemplos

**A manager notes on paper who to phone and loses it.**

- Creates the task from the case itself, with a name and a date

→ Whoever opens it sees the context without hunting, and calls stop being forgotten.

**Some things the system cannot do get noted in a personal notebook.**

- Records the task in the file itself
- Assigns an owner and a date
- Checks pending tasks alongside the file's status

→ What depends on a person stops living outside the file.

**A task is agreed in a meeting and nobody notes it.**

- Creates it there and then with an owner

→ The agreement is not lost on leaving the room.

**Tasks pile up and nobody knows which are real.**

- Reviews and closes those no longer relevant

→ The list becomes credible again.

**One task waits on another and nobody knows.**

- Notes what it depends on

→ The blockage is visible without asking.

**Somebody leaves and their tasks stay in their name.**

- Reassigns the open tasks

→ None is orphaned.