Google Classroom workflow
The assignment looks perfect in your Classroom gradebook. You still cannot vouch for it.
It is sitting there, turned in on time, clean prose, the right answer. And you have no honest way to tell whether the student wrote it or pasted it. A similarity score will not tell you. An AI-likelihood badge will not tell you. Both guess at where the text came from, when the question you actually need answered is whether the student understands it.
Tolus answers that question inside the same workflow. After a submission lands, it runs a two-to-four-minute oral defense for AI cheating in Google Classroom and writes the rubric-based verdict back to your gradebook. Below is the round trip, start to finish.
In the Classroom gradebook
The round trip
Out of the gradebook, through the defense, and back in.
The same submission you could not vouch for leaves Classroom, gets defended in the student’s own voice, and returns as a score you can stand behind. Four stops, one continuous workflow.
- 01
Connect your Classroom course.
Sign in with your Google account. Tolus reads the courses, assignments, and roster you select. No district IT setup required.
- 02
Choose the assignment to defend.
Pick any assignment in Classroom. Set the rubric weights you already grade with. Tolus uses the submission text as the defense source.
- 03
Students take the defense from Classroom.
Each student gets a private defense link. Two to four minutes by voice. Works on phone or laptop, mic only.
- 04back in gradebook
Scores write back to your gradebook.
Tolus posts the rubric-based score back to Google Classroom and attaches the transcript so the verdict is auditable from the assignment view.
What changes for the student
A receipt instead of a suspicion.
Students who use AI to study and genuinely understand the material defend their work fluently and earn a high score. Students who handed in something they cannot explain receive a low score and a transcript that shows why. There is no false-accusation moment, no parent meeting that hinges on a probability.
For students, the experience is closer to a quick conversation with a TA than to an interrogation. For teachers, it is a citable record they can defend.
Classroom-specific questions
What Classroom-using teachers ask first.
How do teachers actually catch AI cheating in Google Classroom today?
Most teachers use a mix of intuition, similarity reports, and AI-likelihood detectors. None of them produce a defensible verdict. Tolus moves the workflow from detection to verification by asking the student to defend the work in their own voice.
Does Tolus need district IT to install anything?
No. A teacher signs in with Google, selects the courses to connect, and Tolus uses the standard Google Classroom API. No browser extensions, no LTI integrations, no district SSO required for a pilot.
Will the score appear in the Classroom gradebook?
Yes. Tolus posts the rubric-based score back to the Classroom assignment, and attaches the defense transcript so teachers can re-read the receipt before posting.
Is student data shared back to OpenAI?
Tolus uses OpenAI for question generation and scoring under their API terms, which exclude API data from training. Submission text is sent to OpenAI in real time during the defense; nothing else. See our privacy page for the full data flow.
Can students take the defense from a phone?
Yes. The student needs a microphone and a modern browser. Most students use a phone or a school-issued Chromebook.
What if a student does not have a mic?
Tolus falls back to text input when a microphone is unavailable, so the student can still complete the defense. The fallback is logged for the teacher.
Run the round trip
Point Tolus at one Classroom assignment and watch the score come back.
Connect a single course, pick the assignment you cannot vouch for, and let the defense write a verdict you can stand behind into your Google Classroom gradebook. Free for one course through the term, wired up in about 30 minutes.