---
id: KB-TD-006
url: https://app.codecontract.io/help/day-to-day/sharing-work-across-a-team
idioma: en
categoria: trabajo-diario
subcategoria: tareas
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TD-003, KB-TD-001, KB-TD-017]
citadoPor: [KB-TD-008, KB-TD-014, KB-CL-017, KB-TD-018]
---

# Sharing work across a team

_Giving every case an owner, and what happens when that owner is away._

**Responde a:** assign an owner to a case · who handles each process · a colleague's work while they are on holiday · distributing cases across a team

A case with no owner is a stalled case. Not because nobody can touch it, but because everyone assumes someone else has it — and that only surfaces when somebody asks about it three weeks later.

## The rule

**One person per case, always.** Not a team, not an inbox: a named person. What belongs to everyone gets done by nobody, and in documentation it shows sooner than anywhere because whoever is waiting is outside.

| Situation | Who owns it |
| --- | --- |
| Onboarding a supplier | Whoever will buy from or contract them |
| A site's documentation | That site's manager, not the office |
| A signature request to a client | Whoever handles that client |
| A mass annual renewal | One person, even if the batch is three hundred |

> [!IMPORTANT]
> The owner has to be whoever can resolve it, not whoever created it. If the person who built it has neither the supplier's phone number nor any dealings with them, the case will stall at the first chase required.

## When the owner is away

1. **Reassign before leaving** — Planned holiday: hand over whatever can move in those weeks.
2. **If unplanned, look at what is stuck** — The age filter immediately shows what was left ownerless.
3. **If they leave the company, hand everything over** — That same day, not at month end.

> [!WARNING]
> Reassigning restarts nothing: the case keeps its history and the third party does not learn that whoever handles it has changed. The only thing that changes is who receives the notices.

> [!NOTE]
> If nobody wants to own a case, it usually should not exist. That is a good signal to close it with its reason.

**Can there be two owners?**

Technically yes; in practice it is the same as none.

**Does the third party see who owns it?**

They see who they are dealing with, which is what matters to them.

**Can I filter by owner?**

Yes, and it is the most useful Monday view.

## Ejemplos

**A manager takes three weeks off and returns to nine cases that never moved.**

- Hands over the ones that could progress before leaving
- Leaves the rest marked as hers

→ Returns to two stalled instead of nine, and none for lack of someone to handle them.

**Three people handle supplier onboarding and two write to the same one on the same day.**

- Assigns each file to an owner
- Works on the shared file rather than on copies
- Checks who has what before allocating more

→ The supplier receives one request, not two, and the split is visible without asking.

**Work is allocated verbally in Monday's meeting.**

- Records the assignment

→ Nobody doubts what is theirs.

**One person carries twice the load of the rest.**

- Checks the load per owner

→ The split is adjusted with data.

**Somebody goes on holiday with open files.**

- Reassigns before they leave

→ No file is left waiting.

**Nobody knows which files have no owner.**

- Checks the unassigned ones

→ Orphaned work becomes visible.