A writer’s manuscript workflow: drafts plus a dated record

Flat illustration of a manuscript with a pen, a pile of books and an outgoing submission email, with a timestamp badge

A novel, a thesis, a script or a long reported piece is built in layers: notes, a first full draft, a revision, a submission file, and sometimes a proof. What often goes missing is a clean copy of which layer existed when. This guide is a practical writing workflow that keeps milestone drafts and a dated record of each one, whether you work in Scrivener, Word, or a plain text tool. A TimeBind is a dated, checkable record that an exact file existed no later than a recorded time and still matches. The fingerprint is made in the browser, and the file stays on your device. It does not prove authorship, it does not register a copyright, and it does not detect AI. This is general information, not legal advice.

Some links to other tools on this page are affiliate links, marked “affiliate link”. If you buy through one, TimeBinder may earn a commission, at no extra cost to you. Tools are chosen on merit, with caveats. See our affiliate disclosure.

Table of Contents

Why a living project file is a poor archive

Scrivener projects, Word documents and Google Docs are built to be edited. That is their job. It is also why the file on your disk at the end of the year is a bad stand-in for the file you submitted in March.

Common problems:

  • Autosave and compile settings change the bytes even when the wording on the page looks the same.
  • Snapshots and tracked changes live inside the project. They are useful while the project is intact, and hard to show to someone who does not have your software, your account, or your uncorrupted file.
  • A later “File > Save As” or a Google Docs export is a new file with new metadata.
  • If a publisher, an agent, a university, or another writer later questions a passage, you need the milestone you actually sent, not a reconstructed memory of it.

For the file-type basics, see how to prove a Word document or Scrivener project existed before a date and how a writer can prove a manuscript existed before submitting. This article is about the surrounding workflow: when to snapshot, when to compile, and when to date an export. It is not a replacement for those how-tos.

If the question you are facing is an AI-use accusation, dated drafts are still what you can actually produce. They are not a detector score. See prove a manuscript existed before an AI accusation and working drafts and timestamps vs AI detectors. TimeBinder does not detect AI.

A milestone workflow you can keep up

You do not need to date every evening’s work. You need a habit that is light enough to survive a busy month.

1. Write in the tool that helps you finish. Scrivener is built for long-form structure: binder, snapshots, and compile. Word, Google Docs, LibreOffice, or a plain-text workshop are all fine. The record is about the files you export, not about loyalty to one app.

2. Snapshot or back up at natural breaks. In Scrivener, a snapshot saves the state of a document (or a selection of documents) so you can compare or roll back later. Official Literature & Latte guidance describes naming snapshots, comparing them, and rolling back, and also describes File > Back Up > Back Up To… with an option to zip the project. Use those features. They are an internal history. They are not a third-party dated record.

Two honest limits, from Scrivener’s own model: snapshots belong to the documents they were taken from, so splits, merges and deletions can make an old “full draft” hard to reconstruct from snapshots alone; and Compile uses the current Draft folder, not a snapshot. If you need a shareable copy of a milestone, compile or export it at the time, or zip a backup of the whole project and keep that zip.

3. Compile or export a milestone file you could send to a stranger. A PDF, a .docx, or a plain-text export will still be openable in a decade. A zipped .scriv backup is worth keeping as well, but it is not the best file to hand to an agent who does not use Scrivener.

4. Name the export after the milestone, not after your mood. working-title-draft-2-2026-03-14.docx will still make sense if the title changes.

5. Date that exact export. Fingerprint it with TimeBinder, then do not edit that file again. Click here to start. How to timestamp a file covers the steps. Your first Pooled TimeBind is free; after that, TimeBinds start from US$5, and an ASAP TimeBind is US$15.

6. Keep the certificate next to that exact file, in a backups folder you also copy off-site. A provider’s version history is useful and is still not a dated record — see is Google Drive or Dropbox version history proof a file existed?.

7. When you submit, keep the submission pack. The file you attached, the date you sent it, and the TimeBind certificate belong together. If a later revision is requested, that revision is a new milestone.

Sensible moments to export and date: the first complete draft; a revision you are proud enough to show a trusted reader; the file you send to an agent, publisher, contest, or supervisor; and the version accepted or published, if it differs. For a longer trail, Draft History and the Draft Streak tool can help you keep the habit. The manuscript timestamping page and the creator hub collect the related guides.

What to do with comments, co-writers, and proof pages

If an editor returns a file with comments, save that file as its own version. “Accept all” and a clean export are a further file. Date the ones you may need to point to — often the file you sent, and the file that came back.

If you co-write, agree where the canonical draft lives, and date the pack you circulate. A shared Google Doc history is better than nothing and still sits on an account you do not fully control. An exported milestone plus a TimeBind is easier to hand to a third person.

Proof pages from a typesetter are new files. If a wording dispute later turns on what went to press, keep the proof PDF as well as the manuscript.

In the United States, copyright exists when an original work is fixed in a tangible form, and registration with the U.S. Copyright Office is a separate, formal step with its own rules and benefits. In the UK and across the EU, there is generally no official copyright register of the US kind; protection is automatic when the legal conditions are met. A TimeBind does not replace registration where you choose to register, and it does not create a copyright. For the comparison, see copyright registration vs a timestamp.

If a US or UK publisher asks what you used a writing assistant for, a trail of dated drafts can show how the file developed. It cannot, by itself, prove that no assistant was used, and it is not an AI detector. Keep notes, if you need them, in a form you could stand behind later, and date the manuscript files you actually deliver.

Mistakes that leave you with a draft you cannot show

  • Never compiling, then losing or corrupting the project. You will wish you had a PDF.
  • Dating the project, then continuing to write in the same file. The fingerprint is for the bytes you submitted.
  • Relying on snapshots alone to reconstruct a whole earlier draft. Export at the time.
  • Submitting from a copy you then overwrite with typo fixes. Keep the submitted file immutable and date the typo-fix as a new version if you need to.
  • Treating a TimeBind as a copyright registration or as proof you are the author. It dates a file. It does not decide authorship.

Frequently Asked Questions

  1. Do I need Scrivener for this workflow?

    No. Export milestone copies from whatever you write in, and date those files. Scrivener’s snapshots and backups are helpful if that is already your tool.

  2. Should I timestamp the `.scriv` project or the compiled PDF?

    If you can, keep both: a zipped project backup and a compiled PDF or .docx you could send to someone else. The compiled file is usually the one other people can open.

  3. How often should I date a draft?

    At milestones you would want to point to later — a complete draft, a submission, a significant revision — not every daily session. You can still back up daily.

  4. Will this help if someone says I used AI?

    It can show that particular drafts existed by particular dates. It cannot prove how a sentence was produced, and it is not an AI detector. TimeBinder does not detect AI.

  5. Does a TimeBind register my copyright?

    No. Registration, where it exists, is a separate official process. A TimeBind dates a file and lets you check that it still matches.

Date the next milestone draft free

Your first Pooled TimeBind is free, with no credit card required. After that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. Click here to start, or see plans and pricing.

Related: Office for Students AI assessment guidance: what students should keep.

Related: Substack’s Scan for AI text: what writers should keep.