What exactly did we send?
Months after a proposal goes out, someone will ask what it said and what it was based on. Most organisations can only answer the first half.
A tender is disputed. A client queries a figure in a report you delivered in March. An insurer asks what advice was given, and on what basis. The question is always some version of the same one: what exactly did we send, and why did it say that?
Finding the document is usually possible. There is a PDF in someone’s sent items, or a file called Final_v3_revised in a shared folder. Finding the reasoning is harder. Which version of the pricing schedule was it built on? Who approved section four? Was the safety statement the one legal signed off, or the earlier draft someone pasted in a hurry?
AI makes the gap wider
When documents were written slowly, by hand, the people involved could often reconstruct the story from memory. AI changes the pace. A first draft that took a week now takes an afternoon, and it draws on dozens of sources nobody consciously chose. If the only thing kept is the final file, the organisation has sped up the writing and lost the record.
The answer is not to slow down. It is to treat anything that leaves the building as a record, not a file, and to keep that record as a side effect of doing the work, rather than as a filing task at the end that nobody has time for.
Four things a record should hold
The inputs, as they were. The brief, the evidence and the structure the document was written against, fixed at the time, so later edits to the source material don’t rewrite history.
The approved versions. Approval belongs to a specific version of a specific section. If the text changes after approval, it is a new version that needs approving again.
The sources behind each claim. Every figure and statement can be traced back to the excerpt it came from, so “where did this come from?” has an answer in seconds.
Every export, kept. Sending a revised copy adds a new entry; it never replaces the old one. The history shows every version that went out, and when.
If you can’t say what was sent and why, you didn’t send a document. You sent a liability.
Organisations that keep records like this find the benefit long before any dispute. Reviews are quicker, because reviewers can see what changed and what it rests on. New staff learn from approved work, not from whatever happens to be in a shared drive. And when the hard question finally arrives, the answer is a screen, not a search. That is what we mean by governed work: speed, with the receipts kept.