A novelist friend told me last month that her editor asked, casually, if she could send over her working files. Not the manuscript. The scratch pads. The abandoned openings. The voice memos she made walking her dog. The editor phrased it as curiosity. Everyone understood what it was. If you write with tools like YouWrite's Story workflow, or without any AI at all, the question is coming for your inbox.
The Wall Street Journal and The Atlantic have both covered the rising anxiety around proving human authorship, with teachers, editors, and hiring managers demanding some form of receipts. The tone in that coverage is mostly grim. I want to argue the opposite. Documenting process is one of the oldest craft practices in writing, and reclaiming it now, on your own terms, will make you a better writer regardless of who is watching.
The quiet shift
Universities started it. Turnitin rolled out AI detection in April 2023, and by fall, English departments across the US and UK were requiring students to submit draft histories through Google Docs version tracking. The publishing side followed. Literary agents at Writer's Digest events in 2024 began mentioning, offhandedly, that some houses now ask debut authors for evidence of the writing process. Freelance markets moved fastest. Contently and other content marketplaces added workflow verification to their contributor agreements.
This is uneven. A staff writer at a magazine has institutional cover. A freelancer pitching cold does not. A grad student in a funded program has the software licenses and the training. An adjunct teaching four sections at two schools has neither. The people most burdened by proving they wrote something are usually the people with the least time to build the systems that would prove it.
The honest response is not to pretend this is fair. It isn't. But refusing to build any process at all is a kind of self-harm, because the writers who do build these systems are producing visibly better work, and not because of the paper trail.
What documentation actually does to the writing
Here is the part nobody talks about. When you know your process is legible, your process improves. This is not surveillance theater. It is the same reason a chef who plates for photographs starts cooking more carefully.
Mary Karr keeps yellow legal pads dated in the top right corner going back decades. Zadie Smith has talked, in her Rules for Writers, about writing on a computer disconnected from the internet, and about keeping her notes in physical form. Neither of them does this to prove anything to a court. The record of thinking is the thinking. A draft you cannot retrieve is a thought you cannot revise.
What AI-era documentation adds is timestamps and version granularity. Those are gifts. You can watch, in Google Docs' version history, the exact moment a paragraph you had been struggling with cracked open. That is teachable data about your own mind.
The practical habits
Timed freewrite saves
Open a document. Set a timer for twenty minutes. Write without editing. Save it with the date and a two-word tag: 2024-11-14_lighthouse-opening.md. Do not delete these files. Ever. They cost nothing to keep and they are the strongest evidence, both to yourself and to any skeptical reader, that thinking happened in your hands.
This practice predates AI. Peter Elbow wrote about it in Writing Without Teachers in 1973. What is new is that the saved artifact is now valuable in a second way.
Annotated outline files
An outline is not a table of contents. A useful outline has your reasoning next to each beat. Why does this scene come before that one? What is the reader supposed to feel by the end of section three? Write those notes to yourself, in the same file, in a different color or in brackets. When you revise the outline, do not overwrite. Duplicate the file and increment: outline_v1.md, outline_v2.md, and so on.
The version numbers matter less than the notes. A file called outline_v4.md with a bracket that says [cut the flashback, it was doing narrative work but killing pace] is a document that could only have come from a person wrestling with the material.
Voice memo idea logs
Most phones have a voice recorder. Use it in the car, on walks, in the shower aftermath. Record thirty seconds when a line comes to you. Do not transcribe immediately. Let the audio pile up. Once a week, listen back and pull what still works into a running notes file.
The audio itself is dated, biometric, and difficult to fake. Your voice memos will also teach you which ideas actually survive a week. About eighty percent will not. That is useful information you were not getting before.
Versioned drafts in Docs or Notion
Google Docs keeps version history automatically, but it compresses aggressively over time. Once a week, use File, Version history, Name current version, and give it a real name: draft 3, cut the mother subplot. Notion has similar functionality under Page history for paid tiers. Scrivener users can use Snapshots, which is the same idea, better executed.
The habit is not the tool. The habit is naming versions so future-you, or a curious editor, can read the arc of the decisions.
Where this gets uncomfortable
Process documentation can become procrastination. I have watched writers spend two hours on version notes and fifteen minutes on prose. If your systems are more elaborate than your output, you have built a museum, not a workshop.
It can also flatten discovery. Some of the best writing happens when you throw out everything and start over in a fugue state at 2 a.m. If your process is too legible, you may resist the moves that do not fit the record. Leave room for that. Not everything needs to be shown.
And YouWrite should say plainly: our Story tool generates drafts fast, which is exactly the workflow that raises the documentation question in the first place. We are working on better in-product version notes and export options for process history. We are not there yet. A writer using YouWrite today should keep their own external notes files. The tool does not replace the practice.
The pivot
Most trade press treats process documentation as defense. Prove you wrote it. Fend off the accusation. That framing loses. It puts the writer in a permanent crouch.
The better framing is older. Show your work. Not because someone demanded it, but because the shown work is where craft lives. Anne Lamott's shitty first drafts. William Stafford's daily morning pages. Ta-Nehisi Coates publishing his revision notes on his old Atlantic blog. These were not defensive postures. They were the writing.
Build the files. Date them. Keep the voice memos. When the editor asks, send whatever you want to send. But the real audience for those files is the writer you are becoming.