Perch is a lightweight Chrome extension for in-class, teacher-supervised quizzes. It removes the lowest-effort shortcuts — a quick tab switch, casual Googling, copy-paste — and keeps a tamper-evident record. The teacher in the room stays the real control.
Ask about piloting Perch Currently in classroom pilot · for school ITAfter every session the student hands their teacher a plain-English, verifiable record. Observations, never accusations — each weak signal carries its benign explanation.
Perch report — Ch. 4 Cellular Respiration
These are observations that need a teacher's judgment — not a determination that anyone cheated.
Ran 40 min of 45 min expected; 1 attention signal,
all recovered promptly; 20s away from the quiz in total.
12:55:06 Clicked away to another window or app for
20 seconds — came back after the warning
12:58:41 Tried to open a blocked page — returned to quiz
Verification code: G3GA-FJIR-WB ✓ record intact
Reports are hash-chained on the student's device and carry a verification code the teacher can check in bulk — casual edits show up as a broken chain.
Most classroom assessment is low-stakes. Perch scales its posture instead of treating every warm-up like a final exam.
The adoption wedge: once-per-class pledge, fullscreen with log-only exits, no escalation ladder. Ten seconds of friction for ten minutes of quiz.
Navigation off the quiz site is blocked and recorded. Leaving the quiz escalates gently — grace period, warning, then a lock the teacher's PIN (or a class-wide live code) releases. Other extensions — AI sidebars, translators, answer helpers — pause for the duration and restore automatically.
An allowlist instead of a lockdown: only the sites the teacher names, website notifications muted, a countdown on the extension icon. Nothing closes, nothing locks; early endings simply show on the summary.
The caveats aren't fine print. They're the design.
If you need those things, you need a different (heavier, more invasive) product — and Perch's docs say so.
On managed Google profiles, force-install by user OU makes Perch non-removable and pre-grants its site permission — no student prompts, and the policy follows students onto BYOD laptops where they sign in with the school account. Two standard Chrome policies (Incognito availability, DevTools for consumer accounts) close the widest bypasses no extension can close from the inside; the deployment guide walks through both.
Data stays on the device. There's no Perch server collecting student activity — reports live locally until a student chooses to hand one in, and contain a self-entered name and a behavioral timeline, never page content.