---
id: KB-TL-013
url: https://app.codecontract.io/help/trackline/launching-one-process-for-many-at-once
idioma: en
categoria: trackline
subcategoria: procesos
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CF-004, KB-TL-005]
citadoPor: [KB-CO-014, KB-CF-010]
enLaApp: https://app.codecontract.io/trackline
---

# Launching one process for many

_The annual review of two hundred suppliers as a single operation._

**Responde a:** request documentation from all suppliers at once · annual supplier review · launch processes in bulk · refresh documentation across the whole base

Once a year you have to ask everyone for the same thing: renewed insurance, current certificates, updated details. One by one that is two weeks; in bulk it is an afternoon and some follow-up.

**En corto**

- One process, one list, one launch.
- Each person receives their own, with their name, not a group email.
- Tracking covers the whole batch and tells you who to phone.

## How to prepare it

1. **Choose who** — Filter: the active ones, one sector, those expiring this quarter. It need not be everyone.
2. **Choose the process** — The same for all. If some need something different, that is two batches, not one with exceptions.
3. **Test on five** — Before the two hundred. That is where a badly worded title shows up.
4. **Launch and leave it a week** — Reminders go out on their own; you look on day seven.

## What responds and when

| Point | What to expect |
| --- | --- |
| First 48 hours | Those who have it to hand |
| After the first reminder | The bulk |
| After the second | The stragglers |
| Beyond that | Phone; email adds nothing more |

> [!WARNING]
> Launching to two hundred with the process built wrong is two hundred conversations. Testing on five costs a day and is the difference between a campaign and an incident.

> [!NOTE]
> Running the annual review on a fixed date — always January, always September — means third parties expect it, and that raises delivery more than any reminder.

**Can I exclude someone from the batch?**

Yes, when choosing the list.

**What about someone who delivered a month ago?**

Filter them out: asking for what they just sent burns goodwill.

**Can it be stopped halfway?**

Yes. What launched continues; the rest does not go.

## Ejemplos

**A company reviews 210 suppliers' documentation every January.**

- Tests on five on 7 January
- Launches all 210 on the 8th
- Phones the outstanding ones on the 20th

→ 85% deliver on their own before month end; the real work is thirty calls, not two hundred.

**The annual review is done supplier by supplier.**

- Launches the same process to all at once

→ The campaign is prepared in an afternoon.

**Launching in bulk brings a hundred identical questions.**

- Includes the context in the notice itself

→ Query volume drops from the first send.

**Some suppliers are already fully current.**

- Excludes those with nothing to provide

→ Nobody who already complied is bothered.

**Nobody knows how the campaign is going.**

- Checks progress per supplier

→ Follow-up is a screen rather than a spreadsheet.

**It launches in August and nobody replies.**

- Picks the date against the sector's calendar

→ Response rates rise without changing anything else.