For faculty

Syllabus language for writing on the record

Three policy blocks you can paste into a syllabus, and how to introduce them in week one so students hear a fair process rather than a threat.

Last reviewed September 9, 2026. Written by the EssayGuard team.

In short

A syllabus policy for recorded writing should say four things: that written work for the course is composed in a recorded editor, exactly what is and is not recorded, how long the record is kept, and that the record starts a conversation rather than deciding a case. Add a plain route for accommodation and a rule that no penalty rests on a single signal.

What a recorded-writing policy has to say

Most AI policies on a syllabus say what a student may not do. A policy for writing on the record says something different: where the writing happens, what the course keeps about it, and what the course does with that record when a question comes up. Students read those lines closely, because a recorder is an unusual thing to ask of them, and the wording decides whether the class hears a fair process or surveillance.

Every block below covers the same five points, in the same order.

  • Written work for the course is composed in a recorded editor.
  • What is recorded: keystrokes, revisions, pauses and pastes, with timestamps. What is not: no camera, no microphone, no monitoring of other tabs or applications, no scoring of prose for style.
  • How long the record is kept before it is deleted.
  • The record is evidence for a conversation, not an automatic finding, and no penalty rests on it alone.
  • How a student who cannot use the editor asks for another arrangement.

The retention figures in brackets are placeholders. EssayGuard lets you set 30, 90 or 365 days on each assignment. Put the number you actually chose in the syllabus so the policy and the setting agree.

Three blocks to paste

Each block is written for a different reader. Change the pronouns, the office names and the deadlines to match your course, and keep the sentence about the record not being a verdict. That is the sentence students remember.

High school

Writing for this class is composed in a recorded editor. The editor keeps a record of how your draft was built: what you typed, what you pasted, what you deleted, and when. It does not use your camera or microphone, it does not look at other tabs or apps, and it does not read your writing for style. The record is kept for [90 days] after the assignment closes and is then deleted. If a question ever comes up about a piece of writing, the record is where our conversation starts. It is not a verdict, and nobody is penalized on the record alone. If you cannot use the editor because of a disability, a device, or your internet at home, tell me by the end of the first week and we will arrange another way to write.

Sample syllabus language, high school

Community college and undergraduate

Written work in this course is composed in a recorded writing editor linked from the course site. The editor records the writing session: keystrokes, revisions, pauses and pasted text, with timestamps. It records nothing else. There is no camera, no microphone, no monitoring of other tabs or applications, and no analysis of prose for style. Records are retained for [90 days] after the assignment closes and are then deleted. The record exists so that a question about a paper can be answered with evidence rather than with a detector score or an impression. A record starts a conversation with me, not an automatic finding, and no integrity charge in this course will rest on a single signal. If you cannot use the editor, contact me or the accessibility office in the first two weeks and we will arrange an alternative.

Sample syllabus language, undergraduate

Graduate

All written assignments in this seminar are drafted in the recorded editor linked from the course site. The editor keeps a keystroke-level record of how each document was composed, including pastes and their length, and periodic snapshots of the draft. It does not access a camera or microphone, monitor other applications or tabs, or evaluate prose for style or likely authorship. Records are retained for [365 days] and deleted at the end of that window. The record is evidence for a conversation about your work. It does not produce a finding, and no allegation will be brought on the record alone: the program requires a second, independent signal. If you cannot use the editor, for accessibility or any other reason, write to me before the first assignment is due and we will agree on an alternative.

Sample syllabus language, graduate

Two independent signals before any penalty

Write this rule into the syllabus and hold yourself to it: no integrity charge rests on one signal. Instructors who have been through a contested case tend to arrive at the same rule on their own, because a single signal is exactly what falls apart in the meeting. A recorded session that shows a large paste is one signal. A detector percentage, if your institution still uses one, is at most one signal, and a weak one: the Stanford study by Liang and colleagues in Patterns (2023) found that detectors flagged 61.3 percent of TOEFL essays by non-native English writers as AI-generated. A second, independent signal is something like a conversation in which the student cannot explain the argument, a cited source that does not exist, or a drafting record that contradicts the student’s own account of how they wrote.

The rule protects students from a false accusation, and it protects you. In Newby v. Adelphi University (NY Supreme Court, Nassau County, 2026 NY Slip Op 26021), a student’s Turnitin flag of 100 percent was contradicted by other tools that read the paper as human. The court found the finding “without valid basis” and ordered the record expunged. A charge built on two independent signals, one of them a record of the session itself, is a different kind of case.

Source: Liang, Yuksekgonul, Mao, Wu and Zou, Patterns, 2023; Newby v. Adelphi University, Justia, checked 2026-09-08.

Introducing it in week one

The policy fails if students first meet it as a line in a document they never read. Spend ten minutes on it in the first class.

  1. Open the editor on the projector and write a sentence. Delete half of it. Paste something. Then open the replay and let the class watch what you just did. The recorder stops being abstract.
  2. Say out loud what it does not do. No camera, no tabs, no scoring of style. Students assume the worst about any tool that records them, and the assumption survives unless you correct it directly.
  3. Explain whose record it is. The student can see their own session and export it. If a paper is ever questioned, the record is their evidence as much as yours.
  4. State the two-signal rule and give one example of what a second signal would be.
  5. Tell them how to ask for an accommodation and by when, and mean it.

Then have every student write the first low-stakes piece in the editor that week, before anything is graded. Once they have used it once, the questions stop.

What the record shows that a document history does not

A Google Docs or Word version history stores document states. It does not distinguish typed text from pasted text, and the author can turn it off. A keystroke-level record shows the pace of the typing, the pauses, the passages deleted and rebuilt, each paste with its length and where it landed, and the order in which the argument formed. That is the difference between knowing a document changed and seeing how it was written, and it is why the syllabus can promise a conversation rather than a guess.

Source: learn.microsoft.com Q&A on Word version history, checked 2026-09-08.

Pitfalls

  • Do not describe the editor as an AI detector. It is not one, and a student who hears “detector” will expect a score. EssayGuard records the session and scores nothing.
  • Do not set a retention window in the syllabus that differs from the one in the assignment settings.
  • Do not promise to open every session. Most are never opened, and saying so lowers the temperature in the room.
  • Do not bury the accommodation route. A student who cannot use the editor and does not know how to say so will submit something written elsewhere, and now you have a case that should never have existed.
  • Do not present the record as proof of authorship. It shows how text entered the editor, not whether the ideas were the student’s. It is evidence for a conversation, not a verdict.

Questions people ask

Can I require students to write in a recorded editor?

That is an assignment design decision, and most institutions treat it the way they treat a required submission format or a required citation style. Check your own academic policy, state the requirement in the syllabus before the term starts, and provide a route for accommodation. The student always knows the recorder is running and can export their own record.

What if a student refuses?

Use the accommodation route in the policy. An in-class writing session, an oral component or a supervised draft are all reasonable alternatives. Do not treat a refusal as evidence of anything. A student who does not want to be recorded may have a good reason, and the point of the policy is a fair process, not compliance for its own sake.

Should the syllabus name the tool?

Yes, and link to the page that states what it records and what it refuses to record. Students take a policy more seriously when they can read the vendor's own limits. For EssayGuard that page is essayguard.io/security.

How do I adapt this for a department-wide policy?

The undergraduate block generalizes with the pronouns changed. The part worth making department-wide is the two-signal rule, so that sections taught by different instructors bring cases built to the same standard.

Try it with one assignment

The rest of this semester costs nothing. Setup takes three minutes.

Every course you teach, unlimited students. Students install nothing.