A grammar and style tool can make a manuscript, a pitch, a report or a long email easier to read. It can also change the file. If a publisher, an agent, a supervisor, a client, or another writer later asks which text you actually sent, “the version in my editor” is a weak answer. The useful habit is to edit in the tool that helps you finish, then keep an unedited copy of the exact file you submitted, plus a dated, checkable record of that file. 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
Editing changes the bytes, even when the page looks familiar
Every accepted suggestion, every “rephrase”, every typo fix after you thought you were done, produces a new state of the file. That is the point of an editor. It is also why the living document is a poor archive of the draft you sent in March.
Common gaps:
- A Word document, a Google Doc, or a Scrivener project keeps being edited after the submission email goes out. A month later, nobody can be sure which sentences were in the attached file.
- In-app history, tracked changes, or a cloud version list lives inside an account or a project file. That is useful while the account is intact. It is harder to hand to someone who does not have your login, your software, or your uncorrupted file.
- A later “Save As”, a fresh compile, or a Google Docs export is a new file, often with new metadata. See what happens to file dates when you copy, zip or download and is Google Drive or Dropbox version history proof a file existed?.
- If the later question is about AI use, a tool report or a detector score is the wrong kind of answer. Dated drafts can show that particular files existed by particular dates. They cannot prove how a sentence was produced. TimeBinder does not detect AI. See working drafts and timestamps vs AI detectors and prove a manuscript existed before an AI accusation.
The file-type steps for Word and Scrivener are in 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 editing layer that sits on top of those tools: how to use a checker without overwriting the submitted file.
A workflow that keeps the submitted file intact
You do not need to date every evening’s edits. You need a clean copy of the milestones you would want to point to later.
1. Write and edit in the tool that helps you finish. Microsoft Word, Google Docs, LibreOffice, a plain-text workshop, or a long-form app such as Scrivener are all fine. A grammar and style checker can run inside those apps or in a web editor. The record is about the file you export, not about loyalty to one checker.
2. When a milestone is ready, export a copy you could send to a stranger. A PDF or a .docx is usually easier for someone else to open than a project file. If you work in Scrivener, compile at the time; official Literature & Latte guidance is that Compile uses the current Draft folder, not a snapshot, so a snapshot alone is not the submission file.
3. Name that export after the milestone. working-title-submission-2026-11-11.docx will still make sense if the title changes. Keep typo-fixes and later revisions out of that file.
4. Date that exact export, then send that exact file. Fingerprint it with TimeBinder before you attach it or upload it. 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. Do not open the dated file to “just fix one typo”. If you must fix a typo, save a new file and, if the typo-fix is what you actually send, date that one instead.
5. Keep the certificate next to that exact file, in a backups folder you also copy off-site. The email or submission form, the dated file, and the certificate belong together. If you only want a quick local check later, the free SHA-256 file hash checker can show whether two copies still have the same fingerprint. A hash on its own is not a dated record. A TimeBind is.
Sensible milestones: a complete draft you will show a trusted reader; the file you send to an agent, publisher, contest, editor, or supervisor; a requested revision; and the accepted version, if it differs. Draft History, manuscript timestamping, and the creator hub collect the related guides.
What a writing editor can and cannot show later
A style tool is good at its own job. Official feature lists typically cover grammar, punctuation, spelling, readability, repetition, and, on some products, longer manuscript-level reports. Those reports can help you decide what to change before you submit.
They do not replace a dated copy of the file you submitted.
A writing editor typically does not:
- Record, in a form you can hand to a third person, that a particular export existed no later than a given time and still matches.
- Prove that you are the author, or that no assistant was used. If you use a rephrase or a manuscript-analysis feature, that is part of how the text was produced. A TimeBind of the finished file will not hide that, and it will not prove the opposite either.
- Act as a copyright registration. 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 official step. 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. See copyright registration vs a timestamp.
- Stand in for a plagiarism process a publisher or university already uses. A checker’s plagiarism report, where one exists, is that product’s own analysis, with its own limits. It is not a TimeBind, and TimeBinder does not offer a plagiarism or AI-detection score.
If you paste or upload a manuscript into a web editor, read the vendor’s own privacy terms. Official ProWritingAid help, as checked on 11 November 2026, states that the company does not use your text elsewhere or to train AI. That is their published policy, not a substitute for keeping the canonical copy on your machine.
After you submit: comments, typo-fixes, and proofs
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 notice a typo after you have already submitted, do not silently edit the dated file. Send a clearly named typo-fix if you need to, and date that fix if it becomes the new canonical copy.
Proof pages from a typesetter, or a publisher’s house-styled file, are new files. If a wording dispute later turns on what went to press, keep the proof PDF as well as the manuscript you first submitted.
Co-writing follows the same rule: agree where the canonical draft lives, export the pack you circulate, and date that pack. A shared Google Doc history still sits on an account you do not fully control.
Mistakes that leave you with a draft you cannot show
- Submitting from the living document, then continuing to accept editor suggestions in the same file. The fingerprint, if you make one later, will be for a different text.
- Dating the project or the checker’s web-editor copy, then compiling a different export to email. Date the file you actually attach.
- Relying on Scrivener snapshots or Word’s version history alone. They are useful while the project is intact. Export and date a shareable milestone as well.
- Pasting the only copy of a chapter into a web editor and treating that site as the archive. Keep the canonical file on your machine, and back it up.
- Treating a TimeBind as a copyright registration, as proof of authorship, or as an AI-detector result. It dates a file. It does not decide how the sentences were written.
Frequently Asked Questions
-
Should I timestamp the draft before I run a grammar checker, or after?
If the question is “what did I submit?”, date the file you actually sent — usually the export after you have finished editing. If you also want a record of an earlier, unpolished complete draft, export and date that earlier milestone too. Do not date a file and then keep editing it.
-
Does using a style tool stop me from dating the file?
No. Use the tool, then export a clean copy and date that copy. The TimeBind is for the bytes you submit, including any changes you accepted.
-
I write in Scrivener and edit with a checker. What should I date?
Compile or export a PDF or
.docxat the milestone, and date that file. A zipped Scrivener backup is worth keeping as well, especially if you want the full project, but the compiled file is usually the one other people can open. Snapshots stay inside the project and are not what Compile uses. -
Will a trail of dated drafts prove I did not use AI?
No. 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.
-
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 draft you are about to send, 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.







