---
id: KB-CF-004
url: https://app.codecontract.io/help/use-cases-by-capability/sending-the-same-thing-to-many-people
idioma: en
categoria: casos-por-funcionalidad
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CO-001, KB-TL-005]
citadoPor: [KB-TL-013, KB-CS-013, KB-CS-014, KB-CF-012, KB-CR-009]
---

# Sending the same thing to many people

_Forty amendments or three hundred requests without doing them one by one._

**Responde a:** send a document to many people at once · bulk contract signing · send the same amendment to all staff · batch sending

An amendment for the whole workforce, the annual documentation request to two hundred suppliers, renewing an agreement with every client. It is the same problem three times, and it is solved the same way: one list, one document, one send.

**En corto**

- Each person receives their own version with their own details, not a generic email.
- You track the batch, not three hundred separate sends.
- A failure on one recipient does not stop the rest.

## How it works

1. **Prepare the list** — With names and a way to reach them. It comes out of your own system as is, without editing.
2. **Choose the document** — One only, with gaps filled from each person's details.
3. **Send and watch** — Tracking shows how many opened, how many signed and who has not.

> [!WARNING]
> Check the list before sending. Three hundred sends with the name field wrong is three hundred awkward conversations, and they cannot be pulled back out of anyone's inbox.

## Worth checking first

- No duplicate addresses: the same person would get two.
- Nobody who has already left.
- Enough balance for the whole batch.
- That the wording makes sense to someone with no context — by testing on one person first.

> [!NOTE]
> Sending to five trusted people first and waiting a day catches nearly every glaring error. It costs a day and saves redoing three hundred.

**Can I stop halfway?**

Yes. What has gone continues; the rest does not go out.

**What if someone has no email?**

They are sent by SMS or WhatsApp within the same batch.

**Can I repeat with only the ones missing?**

Yes, by filtering on those who have not responded.

## Ejemplos

**HR sends the collective agreement amendment to 340 employees.**

- Exports the list from their payroll system
- Tests on five people on Monday
- Sends all 340 on Tuesday

→ By Friday 310 are signed and there is a concrete list of 30 to phone.

**The same annex must go to two hundred suppliers and it is done in manual batches of twenty.**

- Prepares the list and launches the send at once
- Excludes those who already have it signed
- Checks progress per recipient rather than per inbox

→ The campaign is prepared in an afternoon and follow-up is one screen.

**It goes to everyone and a hundred identical questions come back.**

- Includes the context and the date in the notice itself

→ Query volume drops from the first send.

**The list holds old addresses and a third bounces.**

- Cleans the contacts before launching

→ The campaign does not start on bounces.

**It launches in August and twenty per cent reply.**

- Picks the date against the sector's calendar

→ Response rates rise without changing anything else.

**Nobody knows who to chase after a week.**

- Checks who is still outstanding

→ Those missing are chased rather than all two hundred.