---
id: KB-GL-015
url: https://app.codecontract.io/help/glossary/words-that-get-confused
idioma: en
categoria: glosario
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-GL-001, KB-GL-005]
citadoPor: [KB-GL-003]
---

# Words that get confused

_Pairs of terms that look alike and are not, with the difference that matters._

**Responde a:** difference between signing and certifying · validating or verifying a document · are approving and accepting the same · difference between a file and a folder

Many misunderstandings with suppliers, clients and auditors come from using as synonyms words that mean different things. These are the ones that cause the most confusion.

**Signing and certifying** — Signing expresses a will about a content: I accept it, approve it, acknowledge it. Certifying fixes that a file existed and has not changed since a date. You can certify something nobody signs, and sign something without certifying it.

**Verifying and validating** — Verifying checks that something is what it claims to be (the file has not changed, the signature is genuine). Validating decides that it serves your purpose. A certificate can verify perfectly and be useless to you because it has expired.

**Approving and accepting** — Accepting is receiving something as delivered. Approving is signing off on its content. When a process mixes them, someone ends up endorsing what they had merely received.

> [!IMPORTANT]
> The pair that causes most trouble is the second. "It is verified" and "it is validated" sound alike and mean different things in an audit: the first is a technical property of the file, the second is your decision, which you answer for.

## Three more, more briefly

| Pair | Difference in one line |
| --- | --- |
| Document and data | The document is the file; the data is what was extracted from it |
| File and folder | A file has status and process; a folder only groups |
| Expired and superseded | Expired is stated by its date; superseded is decided by you |

> [!WARNING]
> And one that is not a pair but a trap: "certified copy" does not mean the same in every context. When someone asks for one, ask exactly what they need before sending anything — often a verifiable document is enough.

## Why it is worth using them properly

**En corto**

- With an auditor, the right word avoids an extra request.
- With a supplier, it avoids them delivering something else.
- And within the team, it stops someone approving what they only had to receive.

> [!NOTE]
> If one of these words is used differently in your company, write that down. That your sector says "validate" for what here is "verify" is not a problem as long as it is clear somewhere.

**Does it matter day to day?**

Usually not. It stops not mattering as soon as there is a third party or a dispute.

**What is the commonest mistake?**

Using "validated" to mean the file is intact.

**Are there more terms?**

Yes, in the general glossary and in each concept's own entry.

## Ejemplos

**A client asks for "validated documentation" and the supplier sends verifiable files.**

- They ask what exactly is needed
- It turns out they wanted quality sign-off, not a file property

→ The right thing is delivered first time instead of two rounds of emails.

**An «original» document is requested and a scan arrives.**

- Clarifies whether paper is needed or a copy suffices

→ A whole courier round trip is avoided.

**Signing is confused with giving approval.**

- Distinguishes who approves from who signs

→ The circuit reflects what actually happens.

**«Current» and «valid» are used interchangeably.**

- Checks what each one refers to

→ You ask for the date or the check, as appropriate.

**A client asks for «traceability» and expects a report.**

- Asks what they want to be able to demonstrate

→ What is delivered addresses their actual need.

**«Expired» is mixed up with «never provided».**

- Distinguishes what lapsed from what never arrived

→ The chase is aimed at the right thing.