Documentation drift happens when the same piece of information lives in several places and the copies stop matching, and AI now exposes it by blending every version into one answer, choosing the wrong one, or just plain hallucinating. This first Q&A Kitchen uses a restaurant kitchen and a 100-document manufacturing case study to show three provenance checks for catching drift and where to stop it.
This issue of Q&A Kitchen is sponsored by Precision Content, which helps enterprise teams structure their content for people and AI.
Picture two cooks at two stations, both mixing the house spice blend.
One is working from the current recipe card. The other is working from last month’s, from before the chef swapped smoked paprika for chipotle and doubled the cumin.
Both blends go out, and each one tastes fine on its own. But a regular who orders the same dish every Friday knows something’s different the moment it hits the table.
Now the kitchen has a question it can’t answer. Which blend is right, and who changed what?
Documentation works the same way.
A product spec lives in a help article, a training deck, and a sales one-pager.
Someone updates one of them, and the other two keep serving last month’s recipe, even though each page reads fine on its own.
That’s documentation drift.
For years, the only people who noticed were the regulars ... a customer comparing two pages, a new hire getting conflicting answers.
Now there’s a new regular at the table. An AI system pulls from every page at once, blends them into one answer, and has no way to tell which recipe is current.
As Precision Content puts it, “AI does not fix content problems. It exposes them.”
I’m Lance Cummings, and welcome to Q&A Kitchen, a new monthly format here at Cyborgs Writing. Each issue takes one question content professionals are asking and pulls together what I’ve been learning, testing, and writing about it into a single answer.
Every section answers one question, so you can jump to the one you need. And if you’d rather watch than read, there’s a video version too.
And now that AI can scale your small business, or just your own personal knowledge base, documentation drift is an important concept for everyone!
So let’s start with this month’s question. How do you stop drift before AI finds it for you?
Why does documentation drift?
Documentation drifts because the same information has to live in more than one place.
That part is normal.
A process model tells a manager what should happen. A checklist tells a quality inspector what to check right now. A training video walks a new hire through it.
Rhetoric scholars Clay Spinuzzi and Mark Zachry call this a “genre ecology,” or different documents doing different jobs around the same work.
The trouble starts when nothing connects them.
In 2016, researchers spent eight weeks inside the procurement department of a Dutch food manufacturer, one of the five largest in its industry, with more than 20,000 employees across 25 countries.
A new tool doesn't prevent drift ... it often starts the clock.
They traced a single process, approving a purchase, and found roughly 100 documents describing it:
30+ written work instructions
30+ slide decks
15 videos
20+ hybrid documents
a handful of process models, spreadsheets, and e-learning modules
I’ll admit, the number that stuck with me wasn’t the hundred documents. It was the 120 obsolete ones a recent cleanup had already thrown away.
Meanwhile, one employee used an outdated specification to create purchase orders. The orders went out with the wrong supplier reference numbers, and the company paid for it.
That study is nearly a decade old and predates generative AI entirely.
But that’s what makes it useful. The authors traced the drift to three causes:
Different audiences needed different levels of detail.
Different purposes needed different formats.
Nobody had a standard for capturing the information.
None of those causes came from technology, and AI hasn’t removed any of them.
Precision Content sees the same pattern in its work with enterprise teams. Drift tends to start right after new tools and training roll out.
A new tool doesn’t prevent drift ... it often starts the clock.
How do you know when content has drifted?
When the regular sends the plate back, the chef retraces the blend before she blames anyone.
First she checks the shelf. Is there one container of house blend, or are there three jars, each mixed from memory at a different station?
Then she checks the recipe. Which card did the cook use? Is it the current one, or last month’s still taped to the wall?
Then she checks the prep log. Who mixed this batch, when, and from which card?
Content professionals call this provenance, and the chef’s three checks are the same three questions:
Is this fact stored once?
Can you trace it back to what defines it?
Can you prove you followed your own process over time?
Now go back to the food manufacturer.
The employee who sent out the wrong supplier numbers was working from one of roughly 100 documents.
Was that number stored only once? Could anyone trace that document back to the approved specification? Was there a record of who last changed it?
The answer to all three was almost certainly no. The organization only found the problem after the orders went out, the same way the kitchen only found the drifted blend after the regular tasted it.
Most teams know the first question as a “single source of truth.” It often gets read as one giant system for everything.
Every inconsistency turns your reader into an auditor ... and most readers won't do the audit. They'll just stop trusting the page.
Mark Baker’s Structured Writing describes something narrower, one source per fact. Pricing can live in one system and specs in another, as long as the same fact never lives in two places. That discipline is the foundation Precision Content builds before any AI goes on top.
Every inconsistency turns your reader into an auditor ... and most readers won’t do the audit. They’ll just stop trusting the page.
Where do you stop drift?
A kitchen stops drift at the stations, where ingredients change hands.
Content works the same way. Facts move from a subject matter expert to a writer, from a writer to a reviewer, from a reviewer to a translator, and now from all of them to an AI system.
Most drift starts at one of those handoffs, when someone copies a fact instead of pointing to it.
"AI does not fix content problems. It exposes them."
If you are working as a small business or developing a personal knowledge base, then draft happens when you hand off work to your AI agents.
That’s the content supply chain. It’s the path a piece of information travels from the source to the reader or user.
Not every ingredient spoils at the same rate, though. Precision Content teaches teams to sort information by type to help triage content.
Their tax-filing example shows why that matters here:
A concept like “a tax deduction is an amount subtracted from your income before tax is calculated” almost never changes.
A reference fact like “the agency reviews filings within five business days” can change next quarter.
The concept is dry rice. The reference fact is fresh herbs.
You don’t need to watch both with the same intensity, but you do need to know which one you’re holding.
I sort my own teaching materials this way. Definitions and course policies live once in a shared folder and rarely change. Due dates and schedules are the fresh herbs, so those are the ones I check every week.
That’s where provenance comes in. Store the volatile facts once, trace them to whoever owns them, and log every change, because that’s the information the new regular at the table will pull first.
An AI system doesn’t taste the difference between last month’s blend and this month’s. It just serves both … or makes something up.
What can you check this week?
Pick one piece of information your team publishes in more than one place. A price, a deadline, a supported version number.
If you are a small business or working with personal knowledge base, think of something you use often, but in different places.
Then run the chef’s three checks on it. Is it stored once? Can you trace every copy back to whoever owns it? Is there a record of the last time it changed?
If any answer is no, you’ve found where your next drift will start ... before a customer, or an AI system, finds it for you.
Next month, Q&A Kitchen takes that third question further. How do you prove where content came from?
Got a question from your own content kitchen? Leave it in the comments or hit reply.
I’m Lance Cummings. Until next time ... watch those recipe cards.
About Precision Content
Precision Content helps enterprise organizations turn scattered documentation into structured, reusable content that people can trust and AI systems can retrieve accurately. Their methodology, standards training, and content transformation services give teams a single source for every fact.
