Skip to content
Classwork Lab
All tools

Process Flow

Process Flow reads a Google Doc’s own revision history and shows how the writing came together: separate writing sessions, an estimate of active time, pacing, and any large single insertions. It works the same way for a teacher reading work they’ve been handed and for a writer reading their own draft. The analysis runs in your browser.

Before you download

The extension is free and there is nothing to configure: no Google Cloud project, no OAuth client, no API key, no account. You need Chrome on a computer and edit access to the documents you want to read. Nobody on the other end installs anything.

Free ZIP download · Chrome on a desktop, laptop, or Chromebook · Manual installation

Install in Chrome

  1. Download and unzip. Save the Process Flow download, then extract the ZIP into a folder you can keep on your computer.
  2. Open Chrome’s extensions page. Type chrome://extensions into Chrome’s address bar.
  3. Turn on Developer mode. Use the switch in the upper-right corner of the extensions page.
  4. Load the extension. Choose Load unpacked and select the extracted folder containing manifest.json.
  5. Pin Process Flow. Open Chrome’s puzzle-piece menu and pin the extension so you can find it during class.

If Developer mode or Load unpacked is disabled on a school-managed device, ask your technology team to approve installation. Downloading the ZIP alone does not install the extension.

Installed an earlier copy? Remove it on chrome://extensions before loading this one. The new copy installs as a separate extension. Nothing is lost: reports are built fresh from the document each time you run them.

Read a document you’ve been handed

  1. Open the document from where you collected it. A Google Classroom assignment or a shared folder you own leaves you as an editor, which is what the extension needs. Open the student’s file itself, not a copy of it.
  2. Click the Process Flow icon. The popup gives you three lines — the shape of the process, anything notable, and how much of the document the revision history actually covers.
  3. Open the full report. Every finding is split into four parts: what was observed, a hedged reading of it, a confidence level, and a question worth asking the writer. The replay plays the document back so you can see the moment behind any claim.
  4. Print it if you need a record. Printing the report gives a clean one-page black-and-white PDF. The conversation cards print one question per card for a ten-minute talk across a table.
  5. Treat it as a starting point. A long insertion can be a quotation, a move from another draft, or dictation. The report is written to prompt a conversation, not to settle one.

See your own process

You do not need a teacher to run this for you. Open a document you wrote: you own it, so you are already an editor, so it works today with nothing to ask for.

The report is a mirror rather than a grade. How many sittings did the draft really take? Did it arrive in one night or across a week? Where did you stop and start over? The question on each finding is one you can answer for yourself. If you ever want to show how a piece of writing came to be, the printed page is the record: sessions, dates, pacing, and the honest notes about what revision history cannot show. The report says “the writer”, never “the student”, on purpose — it reads the same either way.

What it needs, and what it can’t do

Edit access is required. Google only exposes a document’s version history to people who can edit it. You can open a document, read every word, and still get “no access” from Process Flow, because it reads the same history the document’s own File → Version history menu reads, and that menu is not there for viewers or commenters either. A “share it with me” link usually arrives as view or comment access and will not work.

A copy has no history. Making a copy of a Google Doc starts a brand-new, empty revision history. The copy shows one revision — yours — not the original writer’s process.

Revision history is not a recording. Google keeps a summary of edits, not a keystroke log, and it can thin out or merge older detail. Active time is an estimate from the gaps between edits. Writing done elsewhere and pasted in appears as one insertion with no way to tell where it came from. Work on paper, in another app, or on another device is invisible. Google Docs only; this version does not read Word or other formats.

What leaves the browser?

Nothing. Process Flow asks Google for the revision history of the document in your tab, using the Google session you are already signed into, and does the analysis in the browser. There is no Classwork Lab server, no account, no sign-in, and no analytics. The report exists only on your machine until you print or share it yourself. Details are in the Process Flow privacy policy.

Need a hand? Email hello@classworklab.com. Include what the popup said and the kind of access you have to the document, without student work.

Read the teacher guide