Revision History

Built for teachers - show students' history of edits in a Google Doc

Revision History Chrome Extension for Teachers

Revision History is a Chrome extension designed for teachers to monitor students' writing process in Google Docs, including edits, time spent writing, copy/pasting, and a video replay feature. It aims to guide students through revisions and prevent plagiarism from AI and other sources.

Download

Extension stats

By: https://revisionhistory.com

Users: 100,000+

Rating: 3.57

(56)

0.06

Version: 1.3.5 (Last updated: 2024-09-22)

Creation date: 2023-08-09

Risk impact: Low risk impact

Risk likelihood:

Low risk likelihood

Manifest version: 3

Permissions:

storage
identity

Size: 1.58M

Email: in*****@revisionhistory.com

URLs: Website ,Privacy policy

Ranking

# 2,211 ▼ 7

Other rankings

#26 in Education ▲ 2

#4 in history keyword 28 ▼ 1

#27 in document keyword 32 ▲ 2

#33 in google docs keyword 30 ▲ 2

#68 in student keyword 18 ▼ 2

Upgrade to see more rankings

Other platforms

Not available on Android

Not available on Firefox

Revision History (v1.1.1)

5.00

(2) 504

Want to check extension ranking and stats more quickly for other Chrome extensions? Install Chrome-Stats extension to view Chrome-Stats data as you browse the Chrome Web Store.

Extension summary

Analyze keywords

Revision History helps teachers see students' process when they write essays in Google Docs. It is meant to help teachers guide their students through revisions as well as to ensure that students are not just copy/pasting text from AI/LLMs/ChatGPT or other sources.

With Revision History, you can see:

How many edits students made to their essays
How long they spent writing
What snippets they copy/pasted
Watch a video replaying the document being written

It also works with documents submitted to Google Classroom (as long as they were drafted in Google Docs).

User reviews

These summaries are automatically generated weekly using AI based on recent user reviews. Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate, spammy, or outdated.

Pros

Valuable for teachers to track students' writing process and revisions
User-friendly interface that simplifies reviewing documents
Provides detailed information on deletions and copy/pasting behavior
Effective tool for gaining insights into student work quality
The ability to see a visual playback of the writing process helps streamline grading

Cons

Concerns regarding student privacy and potential data breaches
Inaccurate tracking of editing times and behaviors
Instances of malfunction with extra characters appearing during playback
Accusations of the extension functioning as a keylogger
Doubts about its effectiveness against advanced students who may bypass it

Most mentioned

Privacy concerns related to student data
Inconsistencies in revision history tracking
Value as a grading and evaluation tool for educators
Functionality issues related to playback accuracy
Desire for expansion to other Google applications, such as Google Slides

User reviews

All of the negative reviews I've read are from students that got caught cheating. This works like Draftback, but gives useful summaries as well. It helps me pinpoint where in the revision history I need to go looking for the specific things students have done. This is super valuable for teachers with the increase in AI use by students.

Anthony Calandro, 2025-01-17

better than draftback. one of the best extensions

Geo Digital Marketing, 2025-01-14

This is a very useful tool for teachers. While all the categories of tools such as Deletions, Large copy/pastes, etc are easy to use and provide insightful information, it will be more helpful to explain what the "Active writing time" means and how it is calculated. Sometimes I see, for example, active writing time is only 12 seconds, but the copy/paste was 6 times and deletion was above 50 times, which causes a confusion because even just completing the 6 times of copy/paste and above 50 times deletion, I doubt if 12 seconds was possible. So how should I understand that?