Short answer: You usually can’t show after the fact that a manuscript existed before an accusation; you show it with records made at the time. The strongest set is a trail of dated drafts, notes and outlines, ideally each one timestamped independently (for example with TimeBinder®, which anchors each file’s SHA-256 fingerprint to the Bitcoin blockchain). Each timestamp shows that an exact file existed no later than a recorded time and still matches its fingerprint. A timestamp shows when a file existed, not who wrote it or whether AI was used, but a steady trail of earlier versions gives anyone reviewing your work something concrete to look at.
Disclosure: I’m Inna Hall, co-founder of TimeBinder, the file timestamping tool this guide uses. This page is general information, not legal advice.
Table of Contents
Why the date matters now
Writers are increasingly asked whether a manuscript, essay or article was written with AI. Sometimes the question comes from a detector score, sometimes from a reader’s hunch. Either way, the question is really about process: did this work develop the way a person’s writing develops, over time, through rough versions?
Your finished manuscript can’t answer that on its own. Your earlier versions can, if you can show when they existed.
Records that help, and how strong each is
- Version history in Google Docs or Word online. Useful and detailed, but held by one company in your account, and older versions can be lost when files move. See cloud version history as proof.
- Daily word counts and fingerprints. Keeping a daily draft log (Draft Streak) shows the work growing day by day, but its dates come from your device’s clock, so TimeBind the milestones for a recorded time.
- File dates on your computer. Easy to change, so they carry little weight. See whether a file’s date created can be changed.
- Emails to yourself or to an editor. Better, because a third party holds them, but the date depends on the provider’s records. See emailing yourself as proof.
- Submission receipts and messages with beta readers. Good context, held by other people.
- Independent timestamps of each draft. A record of each exact file that isn’t tied to your account or your computer’s clock. Pooled TimeBinds are checked through TimeBinder; ASAP TimeBinds can also be checked independently from the certificate and the Bitcoin blockchain.
No single record settles it. Together, they tell a consistent story.
Build a draft trail from today
- Keep separate files for each milestone: outline, first draft, each major revision, the version you submit.
- Seal each milestone as you finish it, together with notes or research files from that stage. One Pooled TimeBind covers up to 10 files.
- Never re-save a sealed file. Work on a copy; even an unchanged re-save can alter the fingerprint.
- Keep each Proof of Time Certificate next to the files it covers.
If you use Word or Scrivener, see how to date a Word document or Scrivener project. For the wider picture, see manuscript timestamping.
Build a dated draft history. Timestamp each draft, note and manuscript as you go, so you can show when each version you timestamp existed. See how it works →
The free plan includes 1 Token a month (no rollover). Files are hashed locally on your computer and are never uploaded.
If you are accused
Stay calm and stick to records. Share the drafts and their certificates, explain how you work, and offer to walk through the versions. If you used AI as a tool for some tasks, say so plainly; showing your own work is easier when you are open about it. If a contract, degree or publication is at stake, get advice from someone qualified. If your book is already published, see what to do when an author is accused of using AI.
For the wider picture, including what detectors can and can’t tell you, see how to prove you wrote something and not AI.
What a timestamp does and doesn’t do
TimeBinder anchors each file’s SHA-256 fingerprint to Bitcoin and gives you a Proof of Time Certificate. It records when a file existed: the certificate shows that the exact file existed no later than the anchor date, and if the file is changed later, it no longer matches its fingerprint. Pooled TimeBinds are checked through TimeBinder; ASAP TimeBinds can also be checked independently from the certificate and the Bitcoin blockchain. Your file is hashed in your browser and never uploaded.
It doesn’t show who made the work or who owns it, it doesn’t stop copying, and it doesn’t cover a version you didn’t timestamp. A trail of timestamps strengthens your account; it does not decide the question for anyone.
Frequently Asked Questions
Can I timestamp drafts I wrote months ago?
Yes, but the timestamp will show today’s date, not the date you wrote them. It still helps: from then on, you can show those files existed no later than today and still match their fingerprints. From here on, seal each new draft as you finish it.
Does a timestamp show I didn’t use AI?
No. No record can show a negative like that. A timestamp shows that a specific file existed by a specific time. A series of drafts showing your work developing over weeks is the kind of record that answers an AI accusation better than any single file.
Will my manuscript be uploaded to TimeBinder?
No. Your browser calculates a fingerprint (a SHA-256 hash) of each file, and only that fingerprint is recorded. The text never leaves your computer.
What should I send someone who questions my work?
Usually the drafts themselves, the Proof of Time Certificates for each one, and a short note explaining your process. They can re-check each file against its certificate: Pooled TimeBinds through TimeBinder’s Verify page, and ASAP TimeBinds independently from the certificate and the Bitcoin blockchain.
Plan details were checked against timebinder.io/pricing on 29 October 2026.
