Inspect reconstructs the full revision history of any Google Doc — every writing session, paste event, and revision cluster — into a clear, documentable picture. Other tools charge for this. Inspect doesn't.
Inspect reads Google's revision history and surfaces it in a structure built for teachers. Everything stays in your browser — nothing is transmitted or stored.
See the complete arc of how the document came to be: when writing happened, how long each session lasted, and how much was written per sitting. A two-week assignment written in one overnight session tells its own story.
Every paste event is detected and logged — size, timestamp, and whether the source was internal or external to the document. All of this is surfaced clearly in the sidebar.
An at-a-glance summary of edit patterns: total writing time across all sessions, how much was deleted relative to what was typed, and a picture of revision behaviour across the document's entire history.
Watch the document being written from the first keystroke to the final version, at speeds from 1× to 200×. Paste events and struggle moments are marked on the playback timeline — jump directly to anything that caught your attention in the sidebar.
Playback opens in a dedicated window.
Navigate by step, or let it run at any speed.
Inspect is genuinely free — but it's the starting point, not the whole picture. Here's what you need StyleMatch or Verify for when the revision data raises a question it can't answer on its own.
Inspect shows how a document was built — but it can't tell you whether the writing style matches the student's known voice. That requires a controlled sample and a metric comparison across two documents.
Inspect reads metadata — it doesn't use AI. For sentence-level consistency scoring, internal coherence analysis, or suggested follow-up questions for a student conversation, you need Verify.
Inspect data lives in the sidebar. There's no formatted, printable report for documentation or sharing with an administrator. Reports are a feature of StyleMatch and Verify.
Revision history tells you how the document was built. When you need to ask whether the writing sounds like the student — or want AI-assisted analysis before a difficult conversation — PaperTrail goes further. Both tools unlock in the same extension.
Compare a controlled in-class sample against submitted work across eight stylometric metrics. Does this essay actually sound like them?
AI-assisted deep analysis — internal consistency within one essay, or ten-dimension comparison against a controlled sample. Generates follow-up questions for the student conversation.
Inspect reads revision metadata. Nothing is transmitted, stored, or logged. Everything stays in your browser.
Students never touch PaperTrail. No logins, sign-ups, or data collection of any kind.
Inspect reads revision events — timestamps, edit sizes, paste signals — not the text of documents.
Designed with North American school privacy requirements in mind. No ads, no data resale, no tracking.
Install the extension, open any student Google Doc you have access to, and run it. No account. No setup. No student interaction required.
⬇ Add PaperTrail to Chrome