Table of Contents
TL;DR: AI drift is the slow bending of long AI outputs away from the original ask. Section one is on target. Section three is mostly on target. Section eight is talking about something the prompt never asked for, and section twelve has wandered into territory the user wouldn’t have approved if they’d seen it framed plainly. Drift is the silent killer of long AI projects because nobody catches it. Each section reads fine on its own. The bend only becomes visible if you map the through-line end to end. Here’s the mechanism, here’s how to spot it, here’s the defense. Build the defense before you have to discover the drift the way most consultants discover it, which is when the client implements a recommendation and it turns out the supporting analysis didn’t actually support the recommendation.
The symptom
You give the AI a clear prompt for a long document. Draft a 50-page strategic analysis. Write a chapter-by-chapter book outline. Generate a comprehensive technical specification. The output arrives, you skim the first few sections, the structure looks right, the tone is consistent, and you ship it.
Three weeks later somebody who has to actually use the document points out that section 22 contradicts section 4. Or that the conclusion of the executive summary doesn’t match the conclusion of the actual analysis. Or that the chapter outline you got was for a book about leadership and somehow ended up halfway through being a book about marketing. Or that the technical spec, which was supposed to describe a payment system, has gradually drifted into describing a CRM.
Nobody noticed because each individual section was internally coherent. The drift only became visible when somebody traced the through-line.
This is the failure mode I see more than any other in AI-generated long-form work. It’s silent, it’s hard to catch, and it produces the highest-cost failures because the documents that suffer from it are exactly the documents nobody reads end to end before publishing.
What drift actually is
Drift is the gradual divergence of an AI output from the original ask, accumulating across the length of a long generation. The system handles section one based on the prompt. It handles section two based on the prompt and section one. By section ten, the system is handling the next section based on the prompt and sections one through nine, and the prompt is increasingly far away in the context window.
Each section is technically still on topic. It’s also responding to whatever was in the section just before it, more than to the prompt that set up the whole document. So if section three made a side observation that slightly redefined the scope, section four picks that up. By section eight, the side observation has become the implicit scope, and the original prompt’s framing has been quietly demoted.
This isn’t a bug. It’s the mechanism working as designed. Language models attend most strongly to recent context, because that’s how you produce coherent paragraph-to-paragraph prose. The same mechanism that keeps the writing coherent at the local level is what produces drift at the document level.
Why nobody catches it on review
Three reasons.
The first is that drift doesn’t produce errors. It produces a different document than the one you asked for. Errors are easy to spot. A document that’s competent but on the wrong subject is harder, because nothing on the page is obviously wrong.
The second is that humans review long documents the way they were written, section by section. You read section one and check that it’s on topic. You read section two and check that it follows from section one. You don’t, usually, read section twelve and ask whether it still answers the question you asked back in the prompt. The drift hides in the gap between local coherence and global coherence, and your review process is mostly local.
The third is that AI prose is fluent. Every sentence reads like a sentence somebody would write. So as the document drifts, it doesn’t sound like a document that’s losing the thread. It sounds like a document that’s making subtle, perhaps even sophisticated, additions to the original scope. The reviewer’s instinct is to trust that the writer had a reason, because that’s the instinct calibrated against human writers. The AI didn’t have a reason. It was just responding to its own previous output.
Where drift shows up worst
The longer the document, the worse the drift. Output under 500 words rarely drifts at all. Output between 500 and 2,000 words drifts occasionally, in ways that are usually catchable on review. Output above 2,000 words drifts often, and the drift compounds with length.
Anywhere you ask the AI to generate something where the structure is sequential, drift becomes a structural risk. Book outlines, strategic analyses, technical specs, training curricula, multi-section reports, long-form research synthesis. The system handles the first section against the prompt and then drifts away from it across the remaining sections, and by the end you have a document that started in one place and ended in another.
The worst case I’ve seen, working with clients on long-form ghostwriting projects, is when a consultant uses AI to draft a strategic deliverable for a Fortune 500 client. Eighty pages. The executive summary lays out three recommendations. The body of the report contains the analysis supporting those recommendations. Somewhere in the middle of the analysis, drift sets in. By the time the analysis reaches its conclusion, it’s no longer fully supporting the recommendations in the executive summary. The reader who reads the executive summary and the conclusion side by side notices the gap. The reader who reads the document section by section never sees it. The client implements a recommendation. The analysis turns out not to actually support it. The consultant doesn’t get hired again.
I covered this scenario in Six Places AI Will Break Your Work. Drift is the most common reason long-form AI deliverables fail in professional services.
How to spot drift in your own AI output
Three checks. None of them are optional if you’re publishing the document.
The bookend check. Read the first 200 words and the last 200 words of the document side by side. Do they answer the same question? Do they assume the same scope? Do they treat the same subject as the central one? If the first 200 words say the document is about A and the last 200 words say it’s about B, the drift between them is what you need to investigate.
The section-title check. List the section titles in order. Do they tell a coherent story from start to finish? Does each section title follow logically from the section before? Or do you see a jump halfway through where the topics start drifting in a different direction than the early sections were promising?
The thesis check. Pick the document’s central claim. Read every section and ask whether that section actually supports the claim, contradicts it, or addresses something tangential. If you find sections that support a different claim than the document’s main one, you’ve found where drift took the document.
None of these checks take more than 20 minutes on an 80-page document. None of them are happening on most AI-generated long-form work right now, which is why drift keeps surfacing in deliverables three weeks after they ship.
How to defend against drift while generating
The fix is structural. Don’t generate the whole document in one pass.
Generate in short sections. Have the AI generate one section at a time, with the section’s specific objective in the prompt for each generation. Pass the previous section as context if you need continuity, but re-anchor the prompt to the document’s central question every time.
Re-state the thesis in every section prompt. The AI’s attention bends toward recent context. If you re-state the thesis at the top of every section’s prompt, the recent context now includes the thesis, and the section is more likely to stay on it.
Generate the outline first, and lock it. Don’t let the AI generate the structure of the document at the same time as the content. Have it draft the outline. Edit the outline yourself, with your own judgment about what each section needs to cover. Then generate the content of each section against the locked outline, not against an open-ended “continue the document” prompt.
Review the through-line before you review the prose. Once the full draft is assembled, do the three checks above before you do any other editing. If the through-line is broken, fixing the prose is wasted work because the document is going to need restructuring anyway.
The cost of skipping the defense
The cost of catching drift before publication is small. Twenty minutes of through-line review. Maybe a section that needs to be rewritten because it drifted somewhere unhelpful.
The cost of catching drift after publication scales with where the document ended up. A drift in an internal memo is a moment of confusion in a meeting. A drift in a strategic deliverable is a client implementing the wrong recommendation. A drift in a published book is a chapter that contradicts another chapter and a reader who notices. A drift in a technical specification is an engineering team building the wrong thing.
Drift is the most preventable failure mode in AI workflows, and it’s the one most consistently shipping in production. The defense is cheap. Skipping it is expensive. Most projects skip it anyway because the section-by-section review process feels rigorous, and the rigor of that process is exactly what hides the failure.
This is also the broader failure mode The Death of Thinking is about, what happens to a profession or a culture when the loudest output in the room has been generated by a system that quietly stopped answering the original question several sections ago, and nobody noticed.
Frequently Asked Questions