---
id: KB-TL-007
url: https://app.codecontract.io/help/trackline/adding-to-a-running-case
idioma: en
categoria: trackline
subcategoria: procesos
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TL-002, KB-TL-004, KB-GL-018, KB-GL-019]
citadoPor: [KB-TL-011]
enLaApp: https://app.codecontract.io/trackline
---

# Adding something to a running case

_Request a document you had not planned for without rebuilding anything._

**Responde a:** add a document to a running process · ask a supplier for something extra · add a participant to an open case · modify a process already launched

Halfway through an onboarding you discover something is missing: a certificate nobody planned for, a new person from the subcontractor, a whole phase that did not exist. There is no need to cancel and start again.

**En corto**

- You can add a request, a participant or a phase with the case open.
- The notice reaches only whoever it affects, not everyone.
- The change belongs to that case: the template is untouched.

## What you can add

| You add | Who finds out | When the notice goes |
| --- | --- | --- |
| A request to someone already involved | Only that person | Immediately |
| A new participant | Only the new one | Immediately |
| A whole phase | The people in that phase | When the phase opens |

> [!WARNING]
> If you add something mandatory to a case that was about to close, it becomes incomplete again. That is correct, but worth knowing before you click.

## What does NOT change

- The original template, unchanged for future cases.
- Anything already delivered, which keeps its date.
- Notices that already went out.

**Can I remove a request instead of adding one?**

Yes, or mark it non-mandatory if it no longer blocks.

**What if the person had already finished?**

They get a new notice about what is missing, using the same link as before.

**Is it recorded that it was added later?**

Yes, with the date and who did it.

## Ejemplos

**Halfway through a subcontractor onboarding, two new workers join the site.**

- Adds both as participants on the open case
- Each receives their own health and safety request

→ They start on site with a complete file without redoing the company onboarding.

**A client adds a requirement with the file half done.**

- Adds the document to the file in flight

→ Nothing is rebuilt and nothing already delivered is re-requested.

**A document nobody foresaw turns out to be missing.**

- Adds it and gives notice only of that addition

→ The supplier clearly sees what is new.

**It is added to the template expecting open files to change.**

- Also adds it to the in-flight files that need it

→ What is open reflects the new requirement.

**A document is added to fifty files by hand.**

- Adds it in bulk to the relevant ones

→ The change applies in minutes.

**Something is added and the supplier is unaware.**

- Checks the notice for the addition goes out

→ The addition does not sit waiting in silence.