How Do I Write a Course AI Policy and Communicate It to Students?

You have one syllabus, one assignment sheet, and a room full of students who have already written their own private rules about generative AI. Whatever you publish has to be fair to the student who plays by the rules and to the one who does not, and has to be something you can actually apply to forty submissions without becoming either a pushover or a police officer.

The bottom line: write fewer rules than you are tempted to, tie each one to the specific thing you are assessing, name a single standard place where students declare AI use, and make your enforcement route evidence you can see with your own eyes rather than a detector score. A policy that explains itself is doing assessment design and communication work at once — which is why it takes an afternoon and saves a semester of arguments.

This page covers the course-level document for one module, course or program strand. The assumption throughout is that you have decided what you are assessing; the question is how to say so and make it stick.

What course policies actually look like right now

A content analysis of 116 institutional GenAI policies from 131 US R1 universities and 98 computer-science syllabi from 54 of them found institutions broadly pro-use — 63% encourage GenAI use, 41% offer detailed classroom guidance, 27% discourage it — while half the syllabi (50%) outright prohibit it, 41% permit partial use for specified activities and 7% communicate encouragement. Ganguly et al. (2026) call this the top-down versus bottom-up gap: 92% of syllabi give explicit guidelines, but instructors write local rules that may not align with institutional guidance, and only 47 institutions had both levels detectable. Citation is the one thing both levels agree on, required by 83% of syllabi. Your local rule is the one students meet first, and being stricter than your institution is normal — but it is a commitment you take on alone.

Chirikov (2026) tracked over 31,000 syllabi at a large public research university in Texas from 2021 to 2025: regulation rose from near zero before ChatGPT to 55% of courses by Fall 2025, while the share of fully restrictive policies fell about 5 percentage points a year. By Fall 2025 instructors most commonly restricted drafting and revising (79%) and reasoning and Problem Solving (65%), and most commonly permitted editing and proofreading (83%), study support and synthesis (80%) and coding (75%); ideation was the most contested use (46% permit, 54% restrict). Academic-integrity mentions fell from 63% to 49%, while references to AI's impact on learning rose from 1% to 29% and attribution requirements from 16% to 43%. Instructors are shifting from "don't cheat" language toward "here is why this boundary protects your learning" language.

Nash and Burriss (2026) analyzed 27 classroom AI policies written by preservice English language arts teachers: 26 of 27 permitted some AI use, almost always on teacher-specified terms, times and places, and one prohibited it entirely. Ideation was the most broadly permitted use (22 of 27) and the most ambiguous; 22 disallowed or left unclear the AI composition of sentences, paragraphs or papers; 16 permitted grammar checking and proofreading while 16 prohibited producing large AI-generated text; and 22 of 27 did not address reading at all. The recurring failure was operationalization: one policy allowed AI "to get your thinking started" and declared "this is where the line should be drawn" without saying where. That ambiguity is a defect, not a compromise — it leaves students unable to comply and you unable to apply a consistent standard.

What to write, and where to put it

Start from tasks, not from philosophy. The clearest worked method is McCorkle (2025), who replaced a blanket prohibition students did not believe applied to them. The problem was misalignment, not defiance: students did not see themselves as behaving dishonestly. The method was to inventory every task in the semester project, ask of each "what, specifically, am I assessing?", pair each task with a plausible professional GenAI use, and decide task by task, weighing the need to assess a capability against the value of building a workforce competency. The resulting policy is deliberately uneven: brainstorming permitted but composing specific and measurable learning objectives not, image curation permitted but slide-level message design not, scripts and narration permitted with required evaluation of the AI output.

On the syllabus: the short summary — the tasks, the permitted use for each, how disclosure works, and the consequence of a crossed boundary. On the assignment sheet: the call-out, because one summary is too coarse for a complex project — McCorkle's writing worked because it gave a rationale addressed to students in the second person, naming the assessment that justifies each restriction. In class: say the rule out loud once, at the moment it first applies, and tie it to the work in front of them — a rule a student first meets alone is one they interpret alone.

Disclosure mechanics deserve their own syllabus paragraph: students who co-designed a course policy through guided inquiry prioritized training for students and instructors, standardized disclosure procedures, stronger institutional support and greater involvement in decisions about AI (Hingle and Johri (2026)). Say how, where and in what form a student declares AI use, and say it once. Pisan (2026)'s equivalent move was to make the prompt log the graded artifact: when a model does the production, the prompt and interaction log are the thing worth versioning.

Write only rules you can enforce

A rule requiring per-task monitoring, or a judgment call about when an assessment "begins", will be applied inconsistently, and inconsistency is itself an equity problem. Detector-based regimes bring a surveillance cost that lands unevenly and raise proctoring and data-retention questions. Chirikov's finding of substantial disciplinary and task variation argues for frameworks that grant instructors autonomy within their domain rather than one-size-fits-all mandates.

There is an equity dimension here: opaque policies assume shared background knowledge about authorship, attribution and the norms of academic work, so they fall hardest on students who arrive without it. McCorkle's argument is that transparency dismantles part of that hidden curriculum and reduces the chance that a policy failure becomes a disciplinary matter. The cheapest version of all this is fewer and more specific rules — the tasks you assess, the uses permitted for each, the disclosure mechanics, and the consequence of a crossed boundary — with the reason for each boundary stated.

How to say it so students comply

Disclosure rules do not work as compliance mechanisms on their own; assuming they do is the most common design error. In a mixed-methods study of 409 undergraduates, Qu and Wang (2026) found non-disclosure was strategic adaptation to perceived peer norms and low interpretive Trust in instructors, not moral negligence: perceived peer disclosure and comfort with instructors were the strongest predictors of students' own disclosure, while moral disengagement had weaker effects. Relational climate is a designable variable, and mandates alone are insufficient: what students believe their peers are doing, and whether they trust you to read a disclosure fairly, predicts their honesty better than the severity of your wording.

Kim et al. (2026) identified five distinct sites where a course's real policy lives — faculty intention, formal policy, student interpretation, student self-policy and student practice — with systemic gaps between them, plus 23 rationalizations in six classes students used to justify AI use in academic writing, from "no human victim" to "instructor indifference." Those rationalizations were ad hoc and post hoc: students explained behavior that had already happened rather than reasoning beforehand, which is why clearer wording and harsher detection do not close the gap by themselves. One participant who wanted to obey a strict no-AI rule kept using AI and reported the prohibition "is creating conflict for me, because I'm breaking the rules" — the ban intensified moral conflict rather than preventing use. If a rule produces guilt without compliance, it is not doing work; it is eroding the relationship you need for disclosure.

Watch what you model: because most assignments in Pisan's course disclosed the prompt used to generate them, one student read transparency as permission: "the dependency on ai from the teacher for grading and creating assignments also made it difficult to not use ai for assignments in the same way." Modeling a norm is part of the policy as students experience it, whatever the syllabus says.

A model statement you can adapt:

AI use in this course. I want you to leave this course able to do X yourself, so I assess X directly. You may use AI for [permitted uses] on [task list]; you may not use it for [restricted uses], because those are what I am grading. If you use AI anywhere in your work, tell me in the [single named place — e.g. a disclosure line on each submission] what you used it for and paste the prompts. Declaring it will never lower your grade; not declaring it will. If you are unsure whether a use is allowed, ask me before you submit, not after.

That last sentence moves the decision point to before the work.

The four conversations that generate conflict

The student who used AI and did not say so. Handle this as a process question, not a character question. Mohamed and Temimi (2026) model assessment as a problem of imperfect information: the student knows how the work was produced and the institution sees only the artifact and partial traces. Their response-region model compares three responses — no AI use, disclosed use, and hidden use — and asks which each mechanism makes most attractive. Prohibition defines the formal boundary but leaves hidden use attractive when students perceive detection as weak; monitoring raises the expected cost of hidden use without increasing disclosure; students become cautious without becoming transparent. Permission with disclosure makes honest reporting viable only when the cost of honesty is low. Practically: ask what the work was meant to assess, ask the student to account for their process, and treat a late declaration as information, not a confession.

The student who cites AI for everything. This is usually a skills gap wearing a compliance costume. Attribution requirements in syllabi rose from 16% to 43% while academic-integrity mentions fell from 63% to 49% — the field is asking for citation, not confession. Specify the format once, in one place, on the assignment sheet rather than in a syllabus footnote. State what counts as adequate attribution for your discipline, and give one worked example. Where the real problem is that the student cannot yet do the underlying work without the model, the answer is the task design, not the rule.

Group work. Group tasks are where the five policy sites diverge fastest: five students can hold five different interpretations of one sentence and only one submission is graded. Decide and publish, for each group deliverable, whether AI use is permitted, who declares it, and what happens when one member goes outside the rule — before the project starts, not during the dispute. If you cannot state the individual contribution a member is accountable for, grade the task as group-only work rather than adjudicating authorship after the fact.

Disclosure you cannot verify. Some declarations will be incomplete and some omissions unfalsifiable. Do not build the rule around resolution you cannot achieve: Bassett et al. (2026) argue AI detection should not be used in education at all, on three grounds that bear on policy wording directly. Detector output is a probabilistic estimate that cannot be independently verified, because real-world text origin is unknown, so validation runs on circular reasoning. Detector scores do not meet the balance-of-probabilities standard an integrity investigation requires. And the human-versus-AI dichotomy is meaningless for work created with rather than by AI. Their conclusion is that detection "does not safeguard academic integrity; it undermines it." They also flag a drafting problem: rules restricting AI use "in assessment" fail to specify when an assessment begins, so AI-assisted research, planning or editing may or may not be a violation depending on who is reading. Instead, name process evidence you can observe — a submitted prompt and interaction log, an in-class exercise produced in the room, an oral explanation — and treat a declared AI use as context. Where your institution runs a detector anyway, the same authors' warnings about data storage, retention and commercial use of student work apply; the Privacy objection two preservice teachers raised is the objection your students will raise.

"But..." — the three objections you will hear

"Students will just hide it." Some will, and the design question is which students your rule tempts. Deterrence runs through a detector's discrimination between hidden use and legitimate work, not its raw catch rate, so when extra sensitivity produces more new false positives than new true positives, stronger monitoring can make concealment relatively more attractive — honest students are penalized faster than hidden users are identified. And permission and disclosure are different levers: permission moves the boundary of acceptable use, disclosure changes visibility. Diagnose where your task pulls the student most tempted to conceal, and design for that student, not the most conscientious one.

"I do not want to ban tools I cannot detect." You do not have to. Prohibition is only one of four design responses, alongside monitoring, permitted use with disclosure, and redesign. Redesign changes what the task rewards, and stays cosmetic if the rubric still grades mainly the final product. Pisan (2026) shows the options made explicit and graduated by level: AI use is barred in the introductory programming course, because outsourcing the first loops removes the thing being taught; encouraged on projects in data structures (Copilot permitted) but barred from pen-and-paper examinations; a study and review aid in the upper-division systems course; and required in the AI course itself, where one boundary carried most of the weight — the model may write code, but reflections must be the student's own voice. Assessment moved onto work a model cannot quietly ghost-write, with examinations removed entirely.

"My institution's policy already covers this." Less than you think. That top-down versus bottom-up gap runs both ways: 92% of syllabi give explicit guidelines while local rules drift from institutional guidance, and only 47 institutions had both levels detectable. Procurement, data and review cycles belong to How Do We Write and Implement an Institutional AI Policy?, but the classroom translation is yours. Nash and Burriss conclude that institutions must equip teachers to resist as well as adopt, providing the guidance and professional development that let an instructor decline a specific AI use without being framed as behind the times — their participants' technodeterminism contradicted their own pedagogical commitments. Having an institutional policy is not the same as having cover for your judgment call.

Your first week: an action list

• Inventory the graded tasks and ask of each, "what, specifically, am I assessing?" before deciding anything about AI.
• Decide task by task, and check which response that decision makes most attractive to the student most tempted to conceal.
• Do not make a detector the enforcement mechanism; name process evidence you can observe instead — logs, in-class work, an oral check.
• Say how and where students declare AI use, in one standard place, and treat a declaration as context rather than a confession.
• State each rule as a rationale, naming the assessment it serves, with reminders on complex projects.
• Write only rules you can apply consistently across a marking cycle, and cut the ones you cannot.

Where to go next

Governance, data policy, procurement and review cycles belong to How Do We Write and Implement an Institutional AI Policy?; mandated institutional and district rules sit with Educational AI Policy and AI Governance; rebuilding the task itself so a grade still supports a defensible inference sits with How Do I Redesign Assessment So That a Grade Still Tells Me Something Defensible About What the Student Knows or Can Do?.