5 items
See how a Google Doc was written: writing timeline, flagged pastes, and typed-vs-pasted view. By Classroom Ready AI. You can't tell from a finished essay whether a student wrote it or pasted it. DraftTrack shows you how the document was actually written. Open any Google Doc you have access to, click one button, and DraftTrack reconstructs the writing process from the document's own revision history: • Writing timeline — watch the text accumulate. Steady typing looks like a ramp; a paste looks like a cliff. • Flagged pastes — every large paste from outside the document, with its size and a preview. Cut-and-paste reorganizing inside the same doc is recognized as normal editing, not flagged. • Typed vs. pasted — the finished essay, color-coded by where each part came from. • Writing sessions — how many sittings it took, and how long each one lasted. • Playback — replay the document being written, and literally watch a paste land. DraftTrack is built for honest conversations, not gotchas. Every flag is a reason to ask a question — never proof of cheating. The report explains what each signal does and does not mean. Private by design: • No accounts. No sign-up. No student install. • No server — everything runs in your browser using your own Google access. • Nothing is collected, transmitted, or stored. Close the tab and the analysis is gone. Built by a teacher. DraftTrack is a free tool from Classroom Ready AI, made by a working K-12 literacy specialist. It helps answer the question teachers keep asking: "Is there any way to tell how students are really using AI in their writing?" A demo report is included, so you can see exactly how the analysis looks before you analyze a real doc. Note: DraftTrack reads only the revision history Google keeps for a document, so documents with little edit history show less detail, and it works on Google Docs only. Some normal ways of working-voice-typing, or drafting on another device and pasting your own work — also show up as pastes, so DraftTrack explains what each signal does and doesn't mean. It raises the cost of cutting corners and opens the conversation — it is not a lie detector, and we're upfront about that.
Jun 12, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.