---
id: KB-TL-026
url: https://app.codecontract.io/help/trackline/three-clients-ask-us-for-the-same-thing
idioma: en
categoria: trackline
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TL-023, KB-PR-029]
citadoPor: [KB-TL-021]
---

# Three clients ask us for the same thing

_Build your folder once and answer from it. The work is in gathering, not in uploading._

**Responde a:** several clients ask for the same paperwork · sending the same documents to everyone · how to organise the paperwork clients request · every client asks for their own version

**Almost everything you are asked for is the same handful of documents, so the work is done once.** What differs between clients is rarely the content: it is the name they give it and the form it has to go into.

## Your folder, built once

| What to keep | With what beside it |
| --- | --- |
| The documents always asked for | Their expiry date |
| The ones that lapse yearly | An alert beforehand, not on the day |
| The ones a third party issues | How long they take to issue |
| The ones that are hard to obtain | Who to ask and how, so you never rediscover it |

> [!IMPORTANT]
> **The column that really changes things is the last one: how long each document takes to obtain.** A certificate that takes three weeks is not requested when someone demands it, it is requested beforehand. And that information exists nowhere unless you noted it the first time you had to ask for it — which is exactly when nobody notes it.

## What saves more time than it looks

**En corto**

- Naming files so they explain themselves: what, whose, and from when.
- Keeping the current version and the previous one, not a history of twelve.
- Noting who you have already sent them to, and when.
- And reviewing the folder once a year instead of every time someone asks.

> [!WARNING]
> A nuance that prevents sending the wrong thing: **being asked for the same document does not mean it is wanted for the same purpose**. One client wants it to onboard you, another because a third party requires it, a third because an audit is due. When someone asks for something outside your usual folder, the useful question is not «why do you need this?» but «what do you need to be able to demonstrate?» — because what you already hold often serves just as well.

**Can I send the same folder to everyone?**

The content yes; each will want it through their own route and naming.

**Is it worth keeping it tidy?**

If more than two clients ask each year, yes, by a distance.

**What about documents that expire?**

Those are exactly the ones to hold with an alert: that is where the time goes.

## Ejemplos

**Three clients request the same paperwork in one month and it is hunted down from scratch each time.**

- Builds a folder with the usual set, expiry dates and who issues each item

→ The second and third requests are handled in minutes rather than days.

**A certificate that takes three weeks is requested the day a client demands it.**

- Notes beside each document how long it takes to obtain and requests it with margin

→ Requests stop being answered late because of a lead time that was never yours.

**Three clients ask for the same thing and it is prepared three times.**

- Keeps its own file current

→ Every request is served from the same place.

**Each client asks in a different format.**

- Keeps the original and adapts on sending

→ The underlying work happens once.

**A document expires and three clients must be told.**

- Renews once and resends to all three

→ Renewal does not multiply by clients.

**An old version is sent to a client by mistake.**

- Always sends from the current file

→ Everyone receives the same version.