A Revision History alternative when a replay is not enough

Why teachers search for a Revision History alternative

Revision History is a Chrome extension from TabWrite LLC that replays the history of a Google Doc or Slides file so a teacher can watch it being written. It claims more than 200,000 teachers. The free tier covers 150 documents a month, Plus costs $32 per year, and districts buy by quote. For a teacher whose students all draft in Docs, it is a cheap and pleasant way to look at process.

Source: revisionhistory.com, checked 2026-09-08.

The search that brings people here is usually some version of “Revision History Chrome extension not verifying.” That phrasing is exactly right, and the extension’s own copy agrees: it disclaims being proof of authorship. It replays a history. It does not verify one. Two facts explain why.

• The student controls the history. Google history can be turned off by the student. A Doc with a thin or missing history might belong to a student who pasted a generated draft, to a student who wrote in Word and pasted the finished piece, or to a student whose settings were changed. The replay cannot tell those apart.
• The history can be manufactured. Google Docs version history records document states, not keystrokes, and does not distinguish typed text from pasted text. “Human auto typer” tools such as Phrasly Human Auto Typer, Undetectable.ai, TypeX and naturaltypist.com replay pasted text as keystrokes into Docs or Word so the history looks natural. In a May 2026 r/Professors thread, commenters were naming naturaltypist.com specifically. A replay of a fabricated history looks like a student writing.

Source: revisionhistory.com; learn.microsoft.com Q&A on Word version history; phrasly.ai/human-auto-typer; r/Professors, May 2026; all checked 2026-09-08.

What Revision History does well

For its intended job, the extension is good. The free tier is generous. It handles Slides as well as Docs. It needs no setup on the student side, because it reads a log Google already keeps. In a Google Workspace district where students write on managed Chromebooks and the question is whether a student worked on the essay across the two weeks they were given, a replay answers that, and the disclaimer about proof does not matter much because nobody is taking the replay to a hearing.

K-12 and higher education want different things from a record

The disclaimer starts to matter when the stakes rise. In a K-12 classroom, the teacher usually knows the student, has seen their writing across a year, and is using the replay to open a conversation. In higher education, the instructor may have 120 students they have never met, the student may write in Word or a phone app rather than Docs, and an integrity finding can end in a formal proceeding with an appeal. A record the student can switch off, or that an auto-typer can fabricate, does not survive that appeal. A record the instructor cannot show existed independently of the student’s cooperation invites the argument that a missing history proves nothing, which is true.

The court records on this site make the point from the other side. In Newby v. Adelphi University, a New York court found a Turnitin-based finding “without valid basis” and ordered the record expunged. In Kato v. Palo Alto Unified School District, the family’s filing ran to 1,162 pages and included the Google Docs revision history. In both cases the history, where it existed, helped the student. An institution in the opposite position, trying to show a history was manufactured, would have nothing to point at. Evidence that only works in one direction is not verification.

Source: Newby v. Adelphi University, 2026 NY Slip Op 26021, via Justia; Kato v. Palo Alto Unified School District, N.D. Cal., filed May 5, 2026; both checked 2026-09-08. The lawsuits list has the rest.

What to want in a record that verifies

• Made at the time, not read later. Events recorded while the student writes, with server-side timestamps, so a history cannot be assembled afterward.
• Independent of the student’s settings. Recording that runs because the assignment runs, not because a setting was left on.
• Typed and pasted kept apart. A paste marked as a paste, and kept marked through later edits.
• A cross-check against replay. Some way to tell a stream of keystrokes from a script that emits keystrokes. Periodic snapshots of the document, compared against the event stream, do that.
• A record on the instructor’s side, with a retention window and a report a chair can read.

Side by side

Source: revisionhistory.com; draftback.com; phrasly.ai; all checked 2026-09-08; EssayGuard pricing at /pricing.

How EssayGuard fits

EssayGuard records the session rather than replaying a log. The instructor creates an assignment, sets a retention window, and shares one link. Students open the link in any browser and write; nothing is installed and no account is created. While they write, EssayGuard records every keystroke, revision, pause and paste with a server-side timestamp, and takes periodic snapshots of the document that are checked against the event stream. Pasted text stays marked for the rest of the session. When the student submits, the replay is waiting in the instructor’s account, and a printable evidence report can be produced if the paper is questioned. Classes that already draft in Docs can use the EssayGuard extension, which records the document the assignment points at and only that document.

A keystroke-level record shows what a document history cannot. It shows whether a paragraph was typed or arrived in one paste. It shows the pause before a hard sentence, the thesis rewritten three times, the paragraph moved from the end to the opening, and the order in which the argument formed. A version history shows states of the document at intervals and nothing about how the text got there.

The record has limits, and the report says so. It shows how text entered the editor, not whether the ideas were the student’s own or what happened in another window. EssayGuard does no stylistic analysis and issues no verdict. It is evidence for a conversation, not a finding. The rest of this semester is free for every course you teach with unlimited students; after that the Educator plan is $99 per year, and the DPA is published at /dpa.

Who should still use Revision History

Keep it if you teach in a Docs-first classroom, the free tier covers your volume, and what you want is a window into how students work rather than evidence for a proceeding. It does that job well and at the right price. Move to a session recorder when a record has to exist for every student regardless of their settings, has to cover writing done outside Docs, or has to hold up when the student says the history proves nothing.