---
id: KB-DI-006
url: https://app.codecontract.io/help/documents-and-ai/document-versions
idioma: en
categoria: documentos-ia
subcategoria: subir
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-DI-005, KB-TZ-002]
citadoPor: [KB-DI-010, KB-PR-012]
---

# When a new version arrives

_Replace without losing the previous one, and know which was valid when._

**Responde a:** upload a new version of a document · the supplier sends the renewed insurance · view previous versions of a file · replace a document without deleting it

Insurance renews, a certificate is reissued, a contract gets an amendment. The natural move would be to delete the old and put up the new, and that is precisely what not to do: the old one is what proves what was valid last year.

**En corto**

- The new version becomes current; the previous one sits beneath it.
- Each version keeps its delivery date and who sent it.
- Expiry warnings recalculate against the new one.

## How it works

1. **Upload the new document in the same place, not as a separate one.**
2. **It becomes the current version automatically.**
3. **The previous one stays viewable, marked as superseded.**

## Why keeping the previous one matters

| Question that arrives | What answers it |
| --- | --- |
| Were they insured in March? | The version current in March, not today's |
| When was it renewed? | Each version's delivery date |
| Did anything change between them? | Both, side by side |

> [!IMPORTANT]
> Uploading a renewal as a separate new document instead of a version is the mistake that most clutters a case: you end up with six loose insurance policies and no idea which was valid on which date.

> [!WARNING]
> Replacing is not the same as correcting a misread value. If the document is fine and what is wrong is what was extracted, correct the value; do not ask for another document.

**Can I go back to a previous version?**

You can view and download it; the current one changes by uploading whichever should be.

**How many versions are kept?**

All of them, within your retention policy.

**Is anyone notified when a version is uploaded?**

Whoever has to approve it, if that request required approval.

## Ejemplos

**A supplier has sent renewed insurance every January for four years.**

- Each one is uploaded as a version over the previous

→ Faced with a 2024 claim, they can show exactly the policy in force on that day.

**A new version arrives and replaces the previous one.**

- Keeps both with their dates

→ You can say what applied at each moment.

**Nobody knows what changed from the previous version.**

- Compares the two versions

→ The change is visible without reading it through.

**Work continues on the old version.**

- Marks which one is current

→ The team uses the right one.

**A client asks for the version they were given.**

- Checks which version covered that delivery

→ The right one is provided.

**The new version arrives and nobody tells its users.**

- Notifies whoever has the previous one assigned

→ The change reaches whoever it affects.