September 25 PD Day

Recognizing & Responding to Suspected AI Use

AI Committee · Session Introduction

AI Committee Framing Question

“Who is doing the thinking?”

That’s still the question underneath everything today. Detecting AI use is step one — it doesn’t tell you whether it was a problem.

The day opened with a conversation led by Ann, Jeff, and Greg on what is working for teachers, followed by a two-part introduction and three 50-minute breakout rotations.

Part 1

Review: Our Protocol

AI use is rarely provable outright; the protocol establishes likelihood, not proof. Many students don’t yet know where the line is, so use the moment to show them, not just to catch them.

1

Approach with Curiosity

Start with a conversation, before anything formal. Ask the student to explain their process.
2

Observe & Document

Use the evidence checklist. One flagged paragraph is a data point — not a verdict.
3

Next Steps

Loop in families or admin only when the evidence and the conversation both point that way.

Not: “Did you cheat?” Instead: “Walk me through your process.”

Part 2

Beyond Detection

Why detection alone doesn’t hold up, and what to design instead. Full tell-tale signs and detector research are on the Detecting AI Writing page.

74%

of lightly-paraphrased AI text goes undetected by AI checkers

61%

of non-native speakers’ essays wrongly flagged as AI-generated

15%+

false-positive rates found in independent studies, against the <1% vendors target

Bottom line: treat any flag as one data point. Never proof. If we can’t out-detect it, we design so it doesn’t matter.

Design it differently

  • Clear syllabus policy — define permitted and prohibited AI use per assignment
  • Redesign assessments toward personal reflection and course-specific content
  • Collect process evidence — drafts, outlines, version history — as part of grading

Watch the process, not just the product

  • Scaffold in checkpoints so the developmental trajectory is visible
  • Add brief oral checks or in-class writing to confirm independent work
  • Build a culture of trust — connect struggling students to tutoring, not just enforcement

Key Takeaways

Detection isn’t proof.

Treat any flag as one data point.

Process evidence beats detectors.

Drafts, checkpoints, oral checks.

Specificity is the lock.

Generic prompts are the ones AI finishes alone.

Prevention beats policing.

Design it before you ever need to suspect it.

Breakout Sessions

Five sessions, pick three. 50 minutes each, hands-on with the tools.

Led by Greg

Designing a New Unit or Course with AI

Bring a real idea and use AI as a design partner — draft it, question it, refine it into something classroom-ready.
Led by Jen

Data, Decisions, and Time Back: AI for the Other Half of Teaching

The invisible half of teaching — data, emails, paperwork — is exactly where AI saves the most time.
Led by Bill

AI-Resistant Course Design

If an assignment can be finished by pasting it into a chatbot, that’s worth knowing before a student discovers it first.
Led by Sean

Meeting Students Where They Are: Differentiation & Tutoring with AI

Differentiating a text and tutoring a student come from the same instinct — meeting them exactly where they are.
Led by Diardra

AI Literacy in Any Class

Time and space to think through how AI tools help — and hinder — students’ academic and personal growth.