---
id: KB-PS-016
url: https://app.codecontract.io/help/getting-started/what-this-will-not-solve
idioma: en
categoria: primeros-pasos
subcategoria: recursos
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-PS-008, KB-PS-013, KB-PS-012]
citadoPor: [KB-PS-019]
---

# What this will not solve

_Five problems people expect to vanish on rollout, and that do not vanish._

**Responde a:** what the platform does not do · limits of a document system · will this fix my chaos · realistic expectations for a rollout

A tool is judged by the gap between what was expected and what it does. These are the five expectations we see most often and that are worth discarding on day one, because discovering them in month two takes the whole project down.

## The five

| People expect it to… | The reality |
| --- | --- |
| Tidy the archive you already have | It tidies what comes in from today; old material is brought over and tidied separately |
| Make people reply | It makes chasing automatic, not a supplier willing |
| Decide what is acceptable | It checks presence and expiry; approving is your decision |
| Replace a process that does not exist | If nobody knows which documents to require, the tool does not invent them |
| Correct whoever will not use it | It reduces work for those who use it; it does not reach those who never log in |

> [!IMPORTANT]
> The fourth sinks the most projects and is the least admitted out loud. If in your company each person asks for different documentation by their own judgement, rolling this out unifies nothing: it reproduces the disorder faster and with a better appearance. That conversation — what is required and why — has to happen anyway, and it is cheaper first.

## What does change, so the comparison is fair

**En corto**

- Chasing stops being a job: it happens by itself, with a record.
- It stops depending on who was around: what was done stays where anyone can see it.
- And expiry surprises stop, which is what shows most in the first quarter.

> [!WARNING]
> The AI misunderstanding deserves its own point: **it reads, extracts and summarises, but it does not decide and does not answer for what it asserts**. An extracted value is a value you must be able to check, and a summary is a starting point, not a conclusion. Whoever signs is still a person, and that is not a temporary limitation: it is how it should be.

## What you decide and no tool should

1. **What documentation you require and from whom** — A business decision, not a configuration one.
2. **What happens when someone fails** — Block, escalate or accept the risk. Written beforehand, not in the heat.
3. **And who answers for each thing** — A file with no owner does not move, however automated it is.

> [!NOTE]
> If after reading this you still see the fit, that is a good sign: rollouts that go well start with adjusted expectations rather than enthusiasm. And if one of the five was exactly what you were hoping for, better to know today.

**So what is it for?**

So that what you already do stops depending on memory and on chasing people.

**What if our problem is not knowing what to ask for?**

Start there; the article on what your suppliers will ask you helps to begin.

**Is it worth it with teams that resist?**

Yes, if you start with the process that annoys them most, not the one that interests you most.

## Ejemplos

**A company rolls this out expecting its ten-year archive to be tidied.**

- Adjusts the expectation: new material is tidy, old comes over in stages
- Starts with supplier documentation

→ At three months it judges the result by the chasing it stopped doing, not by the old archive.

**You expect suppliers to start answering unprompted.**

- Automates the reminder while keeping the relationship

→ You chase less; you do not stop chasing.

**You expect automatic reading to be right every time.**

- Reviews whatever the AI flags as uncertain

→ The work shifts from keying to checking, which is far less.

**You expect arguments about who was right to disappear.**

- Keeps a dated trail of every step

→ The argument still happens, but it closes by looking rather than remembering.

**You expect it to decide which documents to request.**

- Writes the list once and reuses it

→ The decision stays yours, but it is taken only once.

**You expect it to sort the old archive on its own.**

- Sorts what is new from day one and brings the old in stages

→ The mess stops growing, even if the history stays where it was.