How Should Authors Organize Manuscript Versions?

Use dated filenames and flag exactly one file as current. Something like TitleOfBook_2026-08-09_draft3.docx, with a single CURRENT marker — a folder, a prefix, or a note — identifying the live one. Never use the word "final." Authors rarely lose files; they lose track of which file is the real one, and that is the failure this prevents.

The longer version

The naming convention

BookTitle_YYYY-MM-DD_stage.docx

Thornfield_2026-03-14_draft2.docx
Thornfield_2026-06-01_beta.docx
Thornfield_2026-07-22_copyedit.docx
Thornfield_2026-08-09_PUBLISHED-paperback-1e.docx

Three properties that matter:

ISO dates (YYYY-MM-DD) sort chronologically in every file browser. 08-09-2026 does not
A stage word, so you know what a file is without opening it
No "final." final, final2, FINAL-real, final-USE-THIS is the universal joke because it is the universal failure

The one rule that does most of the work

Exactly one file is current. Everything else is history.

How you mark it matters less than that it is marked and that only one thing carries the mark. Options that work:

A _CURRENT/ folder holding one file per role
A 00_ prefix that sorts the live file to the top
A plain-text README.txt in the folder naming the current file

Do not rely on modification date. Opening a file to check something updates it.

What to keep, and what to keep forever

Keep forever:

The file corresponding to each published edition. When you produce a second edition, a boxed set, a translation or an audiobook, you need the exact text that shipped
The last draft before a major structural rewrite — occasionally you want the cut back

Keep for now: stage snapshots from the current project.

Delete freely: autosaves, conflicted copies, Document (1).docx.

Snapshot at the milestones

Take a dated snapshot at each real transition: finished draft, out to beta readers, back from developmental edit, out to copyedit, sent to formatter, published. Six or seven files per book, each meaningful.

Continuous versioning is unnecessary for prose. Milestones are what you actually revisit.

If you use tools with built-in versioning

Scrivener snapshots, Word version history and Google Docs history are all useful and none is a backup — they live inside the same file or account that can be lost. Treat them as convenience, and keep the dated exports as the record.

Common exceptions

Co-authored projects need a single shared source of truth and an explicit rule about who edits when, or you get divergent branches.
Series bibles and continuity notes should be versioned alongside the manuscripts.
Formatted files (EPUB, PDF, print interiors) are outputs — keep the version that shipped, but the source document is the thing to protect.
Some authors use git for prose. It works well if you already know it and is overkill if you don't.

Sources

ISO 8601 date format; general file-management practice.

Verified 9 August 2026.