How to read a writing replay
A replay shows how a piece was typed. Reading one well takes a couple of minutes, and the most useful thing it gives you is a better question to ask the writer.
Open it
Go to the reader page and choose the .writing-replay.json file, or follow the link the writer sent. The file is read in your browser and isn't uploaded. Nothing needs installing, and there's no account.
Read it in this order
- The completeness check. A green line means replaying the edits gives exactly the final text the file claims. A red line means the file was altered or damaged after export; ask for a fresh copy.
- The four numbers. Length, how much came from the keyboard, how much was pasted, and writing time. Writing time leaves out pauses longer than a minute.
- What stands out. Plain statements about the recording, each with what it can mean. None is a verdict.
- The chart. Text length over writing time. Composing usually climbs unevenly, with flat stretches (thinking) and dips (deleting). A paste is a vertical jump with a dot. Click anywhere on the chart to jump the replay there.
- The replay. Play it at 32× or faster for an overview, then slow down where something caught your eye.
- The pastes table. Everything that arrived from outside the document, with what it said. Quotes and the writer's own notes are common and fine.
What ordinary writing looks like
- An uneven rhythm: bursts of typing, hesitations mid-sentence, longer pauses between paragraphs.
- Corrections: typos fixed, words swapped, sentences rewritten, sections moved.
- Work across several sittings for longer pieces.
- On phones: whole words at once from suggestions, swipe typing or dictation. The reader labels these as keyboard input, several characters at once.
What deserves a conversation
These are reasons to ask, not conclusions:
- Most of the text arrived in one or two large pastes. Ask where it came from. Some writers draft elsewhere and paste in; then that draft's history is the evidence to ask for.
- Long stretches typed with almost no pauses or corrections and a very even rhythm. This is what copying from another screen, or an auto-typing program, tends to look like. It is also how some fast, confident typists transcribe a handwritten draft.
- Text that changed without a key press. Usually a browser extension such as a grammar checker. Ask what they had installed.
What a replay can't tell you
It can't tell you who was typing, or what was on another screen. A determined person can make a convincing fake with an auto-typing program, and someone who understands the file format can fabricate one. The reader page says this to everyone who opens a replay. Use a replay to start a conversation about the work, not to end one. More on the limits
Asking for a replay with an assignment
You can copy this into an assignment brief:
Please write this assignment at https://theguysaccount.github.io/proof-of-human-writing/write/ and hand in the replay file with your final text. The replay shows how the piece was typed, including pastes, so I can see your process. It runs in your browser and isn't uploaded anywhere. If you draft elsewhere (on paper, in Google Docs), hand in that draft or its version history instead. Using quotes and pasting in your own notes is fine.
Give students another way to show their process if they need one: some write on paper first, and some assistive tools (dictation, word prediction) change how a recording looks.