Receipts writing process record
Writing process record
More facts
02 · Moments
Review moments
You do not need to watch the whole replay. Start with a moment below. Colours identify event types, not authorship or misconduct.
If you need more context, ask the student about a specific moment or source.
03 · Document
The document
Document preview
04 · About
About this record
A program pressing keys at a human pace looks like a person to any browser. The receipt shows the shapes automation leaves: speed, remote control, no pauses, no revision. It cannot promise to catch every one.
Record fingerprints now cover what the browser reported about being started by a test tool, so a record made before 8 September 2026 prints a fingerprint different from the one it printed then. Nothing in the record itself changed.
All record details
Working document
The link holds the record. Nothing is sent anywhere. 0 words 0 characters
Submit your work
Send your work through the usual route, then send the process record privately if your teacher asked for it.
- 1. Submit your workDownload the document and submit it the normal way.
- 2. Send your private process recordCopy a proof link or download a proof file. Anyone with the link can replay it.
- 3. What your teacher will seeThe facts below are what a reader receives. The reader's page also sorts them into a follow-up level so a teacher knows what to open first.
Link or file help
For a long record, use a proof file or short link where available. Keep the record private and send it only through the route your teacher gave you.
Replay
Pasted from outside the record, highlighted while it survives
All timeline events
All record details
Your documents
Tools and backup
Educator tools
For teachers: make an assignment link
Students who open the link start a document labelled with your assignment, and every proof link they send back carries that label. Receipts stores no school roster or assignment list in this mode. The label is provided by the student and is not verified.
For teachers: review a class
Paste the proof links your students sent, one per line, or open their proof files. Records are read in this browser only and are listed by follow-up level, so you know which to open first; records with the same level stay in the order received. This list is a reading order, not a comparison of students. A record that cannot be opened needs a resend, not an interpretation.
Plans
Recording, replay, proof links, Drive backup, Google Docs import. The main list shows 40 days; older records stay openable and downloadable.
Your current plan
Everything in Free, plus every record kept for as long as Receipts runs, the Google Docs cross-check, a printed copy and a letter for your teacher.
Every record kept for as long as Receipts runs, a printed copy, a letter for your teacher and the Google Docs cross-check. One payment with no automatic renewal.
The writing, replay, proof and Drive-backup workflow is live for students. A scoped implementation service can configure and test that workflow with staff under a signed order. Individual paid features remain bound to the purchaser's Google account.
- ✓ One class and one real assignment
- ✓ Voluntary, grade-neutral participation
- ✓ Private proof hand-in test
- ✓ Adult staff setup and training
- ✓ No roster or essay on our servers
- ✓ No shared accounts or licence keys
The pilot and current limits are stated plainly at receiptsproof.com/pilot.
Premium and Defense Pack checkout is handled by Polar, the merchant of record. Individual plans are bound to the Google account used to pay and cannot currently be gifted or transferred to another account. Never share a Google account or licence key.
Second source
Your record and Google Docs revision history describe different parts of the same document process.
Google saves periodic copies of a Doc as it is edited. Receipts can fetch those copies and their times for the one document you choose, then compare them with this record. They are periodic, may be incomplete and do not say who was at the account, but they are a separate source of timing context.
The printed copy is a paid featureThe printed copy is not included with a class link
Your record is available without charge under the current terms. Open the Replay tab to see it, or copy a proof link to share it. The printed copy comes with the Defense Pack or Premium.
Untitled document
This record describes editing events captured in this browser. It does not identify the writer or the source of ideas.
All record details
Recorded facts
Record details
Share this record so the reviewer can inspect the editing timeline and its stated limits.
What this does and does not prove
It shows: that this record describes text accumulating over time, with revision, pauses, and non-linear editing, the shape of composition. Pasted blocks are shown, not hidden.
It does not prove: that a person did not read material on a second screen and retype it. The record cannot observe another screen or establish identity.
Where this record came from: the student's own browser reported it. That does not by itself prove who was typing. The fingerprints are computed by the same page that displays them. They identify the content currently being shown; they do not establish when it was made or whether anybody independent witnessed it. A determined person can hand-author a record like this one. A direct Google Docs cross-check can add separate context from Google's available revision snapshots and timestamps, but those snapshots are periodic and may be incomplete. Record fingerprints now cover what the browser reported about being started by a test tool, so a record made before 8 September 2026 prints a fingerprint different from the one it printed then. Nothing in the record itself changed.
How to use it: review the timeline alongside the assignment context, then ask the student about specific revisions or sources. This record adds inspectable process context but does not settle authorship on its own.