How to Write an AI Use Policy for Your Classroom (With a Template)

Most AI misconduct disputes come from a rule students never saw. Here's a classroom AI policy you can adapt, plus the four decisions behind it.

Almost every AI academic-integrity dispute we hear about has the same root cause, and it is not detection accuracy. It is that the student was never told, in writing, what was permitted, so the argument becomes retrospective, adversarial, and impossible to resolve fairly.

A policy fixes more of this than any tool does. Here is how to write one.

Four decisions to make first

A policy that says "don't use AI" is unenforceable in 2026, because your students' word processors, phone keyboards and browsers all contain generative features. You need to be specific about stages.

1. Research and idea generation. May students use AI to explore a topic, find directions, or explain a concept they are stuck on? Most educators land on yes, this is closer to a tutor than a ghostwriter. Worth stating that model output is not a citable source.

2. Outlining and structure. May they ask for an essay structure? More contested. If your learning objective is argument construction, this matters; if you are assessing subject knowledge, it may not.

3. Drafting prose. The core question. Most policies prohibit generated prose submitted as the student's own, with or without a disclosure exception.

4. Grammar, spelling and clarity editing. Almost always permitted, and worth saying so explicitly, because students who write English as a second language rely on these tools and will otherwise be anxious about a tool everyone else uses freely. Note that heavy paraphrasing tools are a different thing from spellcheck; draw that line clearly.

The template

Adapt freely. The bracketed choices are the decisions above.

### AI Use Policy, [Course Name], [Term]

>

Why this exists. Generative AI tools are part of your working environment. This policy sets out where they help your learning and where they replace it. Ask me if anything is unclear, asking is always safe.

>

Permitted without disclosure

- Spelling, grammar and punctuation checking

- Asking an AI tool to explain a concept, term or reading you found difficult

- Translation support for understanding source material

>

Permitted with disclosure

- Brainstorming topics, questions or angles

- [Generating an outline you then substantially revise]

- [Using AI to suggest rephrasing of sentences you wrote yourself]

>

To disclose, add a short note at the end of your submission: which tool, what you used it for, and roughly how much. One or two sentences is enough. Disclosure is never penalised. It is not a confession; it is documentation.

>

Not permitted

- Submitting AI-generated prose as your own writing

- Using AI to produce analysis, argument or conclusions you present as yours

- Citing AI output as a source

- [Running your draft through a paraphrasing or "humanizing" tool]

>

How work is reviewed. Submissions may be checked with AI detection software. A detection score is never on its own the basis for an allegation. Detectors produce probabilities, and they flag some honest writing, particularly writing by multilingual students. If a submission raises questions, I will ask you about your work and your drafting process before any formal step.

>

What protects you. Keep your drafting history. Google Docs and Word both retain version history automatically, leave it on. A visible drafting timeline is stronger evidence of your authorship than any score is against it.

>

If you are unsure, ask before you submit rather than after. There is no penalty for asking.

Why the review paragraph matters most

That "how work is reviewed" section is the one that prevents the worst outcomes, and it is the one most policies omit.

Detection software estimates how machine-like prose looks. It does not identify which tool wrote something, and it cannot distinguish AI-assisted editing from AI drafting. Most importantly, its errors are not evenly distributed: multilingual writers are flagged at higher rates than native English speakers, because second-language writing tends toward the consistent sentence structure and conservative vocabulary that detectors read as machine-like. The same applies to students taught rigid essay templates, which is to say, students who followed instruction well.

Committing in advance to a conversation before an allegation costs you nothing and protects students from a genuinely unfair process. It also protects you: an allegation resting on a percentage does not survive scrutiny.

Background reading: why AI detectors falsely flag non-native English writers and what a 20% AI score actually means.

Designing assessments that make the policy easier

The policy does less work if the assessment invites generated prose. Adjustments that help:

• Ask for process artefacts. An annotated bibliography, a research log, or a one-paragraph reflection on what changed during drafting. Cheap to produce honestly, tedious to fabricate.
• Anchor in specifics models cannot reach. Course discussions, a named local context, this term's set reading, a dataset you provided.
• Assess in stages. Proposal, outline, draft, final. A drafting trail makes authorship visible without surveillance.
• Include one short in-class writing sample early on. Not as a trap, as a voice baseline that helps you and protects the student.

Letting students check their own work

Something worth telling students explicitly: they can see what a detector sees before submitting. This turns detection from a hidden threat into a transparent standard.

GPTOne's AI detector is what we suggest for this, mainly because of the sentence-level output, a student who sees which sentences flagged learns something about their own prose, where a bare percentage just produces anxiety. It covers ChatGPT and GPT-4, Claude, Gemini, Grok, DeepSeek, Llama, Mistral and Qwen, has no per-scan word limit on any tier including free, and gives 20,000 credits with no card required, one credit per word, so roughly a 20,000-word allowance. For departments checking at volume, plans start at $7.99/month.

Students working on longer pieces may also find the word counter useful for planning against a limit, and a grammar check is the safer alternative to a full-paragraph rewrite tool.

Getting it in front of students

• Put it in the syllabus and at the top of each assignment brief. Syllabi are skimmed once.
• Spend five minutes on it in week one, including the disclosure mechanic. Students routinely assume disclosure is self-incrimination.
• Give one worked example of acceptable use and one of unacceptable use. Abstract rules generate edge-case questions; examples do not.
• Say plainly that you would rather answer a question now than run a misconduct process later.

The bottom line

The policy is the intervention; the detector is just triage. Be specific about stages rather than banning a category, make disclosure genuinely costless, and commit in writing to a conversation before any allegation. Then let students check their own drafts so the standard is visible to everyone it applies to.