---
id: KB-TL-019
url: https://app.codecontract.io/help/trackline/when-you-do-not-need-a-process
idioma: en
categoria: trackline
subcategoria: empezar
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TL-001, KB-TL-014, KB-TL-028]
citadoPor: [KB-SC-018, KB-TL-028]
---

# When you do not need a process

_Turning everything into a process is the second-month mistake. Some requests are settled with a message._

**Responde a:** when to use a process and when not · setting up a process for a single document · this is too much for what I need · asking for something one-off

When something works, the temptation is to use it for everything. A month in, single-step processes start appearing, with one person and one document — which is exactly a well-written message's job, with three configuration screens in front of it.

## What fits where

| Situation | A message is enough | Worth a process |
| --- | --- | --- |
| One document, one person, once | Yes | — |
| The same thing to several people at once | — | Yes: the follow-up runs itself |
| Something that will repeat every year | — | Yes, even if today it is one |
| Several items to review and approve | — | Yes, that is where the difference lies |
| An urgent favour from someone you trust | Yes | — |

> [!IMPORTANT]
> The distinction that orders all this is not size: **it is whether someone will have to chase it**. A document that either arrives today or does not needs no structure. One that has to be chased three times, that expires, that someone else must approve or that you will be asked for again next year does — and building it then costs the same as building it now, except that now you have not chased anybody yet.

## What you lose by doing too little

**En corto**

- The trail: who asked for what, when, and what they answered.
- The reminders, which is what prevents next week's phone calls.
- And being able to repeat it without thinking it through again.

> [!WARNING]
> And what you lose by doing too much, which gets flagged less often: **a single-step process asks the other side to go somewhere to hand over one thing**. For an outsider that is more friction than replying to an email, and friction is paid for in answers that never arrive. If the goal is for them to send something today, what matters is that it is easy for the sender, not comfortable for the filer.

## The rule that works in practice

1. **One-off and nothing to chase: message** — And filed in the right place on arrival.
2. **Repeats, expires or needs approval: process** — Even if today it affects one person only.
3. **And if it started as a message and you are on the third chase** — That was already a process: convert it before the fourth.

> [!NOTE]
> Turning a one-off into a process later is not starting over: what you already received gets folded in. What cannot be recovered is the trail of the times you chased it outside the system.

**What if I do not know whether it will repeat?**

Start simple. The third time will tell you.

**Is a one-step process a mistake?**

Not if it buys a trail and reminders. Yes, if it only adds clicks.

**Can I ask by email and still file it?**

Yes, but filing by hand depends on someone remembering.

## Ejemplos

**A company builds a full process to ask a trusted client for a one-off certificate.**

- Asks by message and builds the process for the annual renewal, which does repeat

→ The document arrives the same day and the repeating part is set up where it matters.

**A process is built to request one document from a colleague.**

- Asks them by message and they upload it

→ Processes are reserved for what repeats.

**A process is built for something that happens once a year.**

- Handles it by hand this time and decides next year

→ No template is maintained for an annual case.

**Something urgent is needed and building it would delay the request.**

- Requests it directly and records it afterwards

→ The urgency is served without losing the trail.

**A process is built and nobody uses it again.**

- Archives templates that are not launched

→ The list reflects what is actually used.

**What began as an exception is now requested weekly.**

- Turns it into a process once it repeats

→ The decision is revisited against real usage.