Nothing gets lost

The situation

You have spent six weeks getting the weekly exceptions report down from three hours to twenty minutes. Standing instructions in your workspace. One connected sheet. An output your manager stopped editing. Then you take a job somewhere else, and IT closes your account on your last Friday, which is what the policy says to do.

On Monday the report takes three hours again. Nobody can say what the instruction said, because there is no file — it only ever existed in a settings panel inside an account that no longer exists.

The principle

Everything worth keeping from an AI tool is plain text, and text that exists only inside a vendor account is not something your organisation owns.

Three things come out of a tool and they are not equally portable. The instruction — the job, the standing context, the standard. Pure text, always copyable, and the actual asset. The configuration — which sources are connected, what was uploaded, which settings differ from default. This one has no export button, so it gets written down by hand, as prose. The outputs — the files it produced, downloadable one at a time, and close to worthless without the first two.

Almost nobody keeps the configuration. Almost everybody keeps the transcript, which is the least useful of the three: a conversation records how you found the instruction, not the instruction.

Worked example

Shown here in Claude.

Structure first. One folder, in whatever your team already uses — a repository, a shared drive, a wiki. Five plain-text files:

weekly-exceptions/
  INSTRUCTION.md       the brief: job, inputs, output shape, standard
  SETUP.md             what was configured, in prose, step by step
  SOURCES.md           what it reads, who grants access, how current
  CHECKS.md            what gets verified before it goes out, in order
  runs/2026-07-30.md   one finished output per run, dated

Then the move that makes this four minutes instead of forty — ask the tool to write its own handover record:

Job: Write the handover record for this project so someone with no access
to my account can rebuild it from scratch in a different tool.

Inputs: Everything in this project — the instructions I set, the files I
uploaded, and the last three outputs.

Output: Four Markdown files — INSTRUCTION.md, SETUP.md, SOURCES.md,
CHECKS.md. SETUP.md describes the configuration in prose, step by step,
naming what I set rather than where I clicked.

Standard: No references to this product's menus or button names. Where you
are describing something you cannot inspect — a connected source, a
permission, who owns a credential — say it is unknown instead of guessing.

Two lines in that standard carry the weight. Name what I set rather than where I clicked is what makes the record survive the next interface change. Say it is unknown instead of guessing stops the model inventing a connection it cannot see.

Paste the result into the folder, read it, and fix the access questions — it can describe a source but not who holds the credential. Run the whole-account export once a quarter as a backstop.

In your tool

What matters is not the menu name but which of the three layers comes out as text you can paste elsewhere.

Product surfaces checked 2026-08-04.

Try it

Take the build you just finished. Five minutes.

1. Make the folder somewhere your team already owns. Not your desktop, and not storage owned by the tool you are trying to outlive.
2. Paste the instruction in verbatim, including the parts you think are obvious.
3. Write six lines of setup notes, by hand or with the instruction above.

You are done when someone who has never seen your account could rebuild the thing from that folder in a different tool. Test it cheaply: hand it to a colleague and ask what they would still have to ask you. Every question is a missing line.

Common failures

• Keeping the chat instead of the instruction. People bookmark the conversation that finally worked. A transcript records a search, not something anyone can run, and it is the first thing an account closure takes with it.
• Screenshotting the settings panel. It looks like documentation and behaves like nothing: not searchable, not pasteable into another tool, and wrong the next time the product moves a menu.
• Exporting once. The instruction drifts every time you fix it in the tool and do not copy it back, so the folder becomes a record of a build that no longer exists. Make copying back the last step of editing.