Run one assignment without turning evidence into a grade.

Preflight the workflow, make an assignment link, then review voluntarily shared records. Without a class code, nothing new is stored; with one, see the class drop box.

The pilot rule: a Receipts record may support a student. Its absence, sparse history, unusual timing, technical failure or incomplete history never counts against them. No signal or score enters the rubric.

Preflight. Test the browser, proof opening and private hand-in route before students use it.
Label the assignment. Make one assignment link in My records and send it through the usual class route.
Review fairly. Read recorded facts, inspect a moment, and keep missing or unusual records neutral.

1. Run a ten-minute preflight

Test the app on the exact managed device, browser and school network students will use.
Type, paste, download the essay, create a proof link, download a proof file and open both on a second device.
If using Google sign-in, Drive backup, short links or Google Docs capture, confirm the school's Google Workspace policy allows the required consent and Drive operations.
Use personal or isolated school browser profiles. Do not use a shared browser profile, because signed-out drafts are stored in that browser.

2. Paste this into the assignment

Receipts is optional evidence of how it was written for this assignment. It is never required for credit and it is not an AI verdict. If you choose to use it, draft in Receipts at receiptsproof.com/app. Recording begins when you type. Submit your essay through the normal class system and privately attach either the proof link or the .receipts.json proof file.

If you do not use Receipts, submit normally. You do not need to explain why. A missing, incomplete, unusual or broken record will not lower your grade or count against you. Other evidence of how it was written may include ordinary drafts, Google Docs revision history, paper notes, a short oral conference or what the teacher saw in class.

3. Give students the privacy warning

A proof link is a bearer credential: anyone holding it can replay the writing history, including deleted passages. Send it only through the private assignment submission channel, never a public board, class chat or group email. A copied full proof link cannot be revoked. Do not record sensitive personal writing unless your teacher has approved the topic and submission route.

4. Use the reliable hand-in path

Short records: use Copy proof link.
Long records: sign in with Google and use Copy short link, or attach the proof file. Chat and LMS fields can truncate long URLs.
If anything fails: treat it as a technical status, not an academic signal. Ask for the proof file or use the student's ordinary alternative evidence.
Always submit the essay separately. The proof artifact is supporting context, not the assignment itself.
Label the records before they exist. In My records, under "For teachers", make an assignment link and send it to the class. A student who opens it starts a document carrying the assignment label, and every proof link they send back carries it too. A link without a class code stores nothing on Receipts servers.
Read the class in one place. In the same section, "Review a class" takes full proof links, Drive short links or proof files and shows one row per record, red first, then amber, yellow and green, so you know where to start; records at the same level stay in the order they arrived. Open any row to read its Summary and Replay. The colour is a reading order; nothing compares students with each other.

5. Read the facts first, then the replay

The shared viewer places Recorded facts before the animation and selects up to three Review moments for direct inspection. When it was written, what came from outside the keyboard, and how it was revised are reported as context. Missing or unusual numbers stay neutral or unmeasured.

The record comes from the student's own browser. It does not by itself prove who was typing. Fingerprints help compare copies but are not proof by themselves. Browser-identified page scripting is rejected and silent text changes are removed before export; device-level automation can still appear keyboard-like.

6. If a dispute remains

Review the record with the student, not about them in their absence.
Ask neutral questions about the thesis, sources, one revision and any discarded passage.
Allow the student to explain dictation, accessibility tools, phone input, paper drafting, collaboration and any AI use permitted by the assignment.
Use the school's existing due-process policy. Receipts supplies context and never makes the decision.

7. Judge the pilot

Track teacher review time, technical failures, accessibility gaps, student opt-out, privacy concerns and whether any student felt pressured. Stop the rollout if a missing record is treated adversely or if an accommodation path is not equivalent.

Talk through the pilot Contact Receipts

The public school terms govern the free pilot. The pilot is free. If a school later wants a wider rollout, the yearly licence published on the schools page applies, and only under a signed order form that names the exact scope and price.