---
id: KB-TL-022
url: https://app.codecontract.io/help/trackline/i-dont-understand-which-document-they-want
idioma: en
categoria: trackline
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TL-003, KB-PR-017]
citadoPor: [KB-TL-023, KB-PR-028, KB-PR-030]
---

# I don't understand which document they want

_Just ask. It takes a minute and avoids sending the wrong paper, which is what actually holds everything up._

**Responde a:** i dont know which document they are asking for · asked for a certificate and dont know which · what does this request mean · i dont understand the document request

**Ask before sending anything.** Sending «something that looks like it» is what turns a two-day request into a three-week one: it gets reviewed, rejected, re-requested, and by then nobody remembers what it was about. Nobody will think less of you for asking exactly what they want.

## Why you do not understand it (it is rarely your fault)

| What is happening | What to do |
| --- | --- |
| They call it by an internal name of theirs | Ask for an example or what they need it for |
| The same paper has three names across sectors | Describe the one you hold and ask if it works |
| They ask for something that does not exist in your case | Say so: that is useful information for them |
| It was asked by someone who copied the list elsewhere | More common than it looks. Ask anyway |

> [!IMPORTANT]
> **Saying «I don't have that» or «that doesn't apply to me» is a valid answer and takes the problem off your desk.** What blocks a file for weeks is not a missing document: it is silence. The moment you say it, the ball is in their court — they either substitute it, drop it from the list, or explain why it does apply.

## How to ask so you get a quick answer

1. **Say what you hold, by its exact name** — «I have an X certificate issued by Y in March» gets further than «I don't know which one you want».
2. **Ask what they need it for** — That usually lets you work out which one it is yourself.
3. **And ask through the link, or by replying to whoever sent it** — That keeps it beside the request instead of lost in a separate email.

> [!WARNING]
> One detail that saves rounds: **if you hold several similar documents, send the one they asked for, not all three**. Attaching everything «just in case» looks helpful and does the opposite: whoever reviews has to decide which one counts, gets it wrong, and you have also handed them documents they never needed and now have to store.

**Can I send something similar and let them pick?**

That is what delays things most. Ask first; it is faster.

**What if I do not have that document?**

Say so. It is an answer, and it unblocks.

**Who do I ask?**

Whoever sent the request: their name is in the message.

## Ejemplos

**They ask for «the quality certificate» and you hold three documents that could be it.**

- Writes out which three, with names and dates, and asks which they want

→ The right one goes first time instead of all three plus a rejection round.

**They ask for a document that does not exist in your line of work.**

- Replies «this doesn't apply to me, and here's why» instead of leaving it blank

→ The file moves because the request gets corrected, rather than sitting there waiting.

**A similar document is sent rather than asking.**

- Asks exactly which document before uploading

→ A whole rejection and resend cycle is avoided.

**The document name uses the client's jargon.**

- Asks them to describe it in other words

→ The right document is identified.

**Several are requested and one is unclear.**

- Uploads the clear ones and asks about the other

→ The file moves while the doubt is cleared.

**The requested document does not exist at their company.**

- Says so and proposes the equivalent

→ The client decides with real information.