Stanford University.
- Detection status
- "Stanford currently does not support any campus-wide plagiarism detection tools," per Teaching Commons guidance updated Nov 17, 2026; individual schools, departments or units may adopt a tool such as Turnitin at their own cost, and "[r]elying solely on plagiarism detection tools to identify if students have not complied with an AI-related course policy is not advised." No AI-text detector is confirmed deployed campus-wide in either direction
- Office in these sources
- Office of Community Standards (OCS) · 650.725.2485 · email via the "Email the OCS Here" link on its About page (the address itself is not shown as page text) · communitystandards.stanford.edu — About
- Ombuds or advocacy office
- Stanford's University Ombuds, confirmed as a resource for "OCS questions" among students specifically, describes its own services as "Independent," "Impartial," "Informal" and "Confidential" in its published Ethics and Standards of Practice, and "serves faculty, staff, students and postdocs at all Schools and Centers other than the School of Medicine" · 650.497.1542 · ombuds@stanford.edu · ombuds.stanford.edu — Why contact the Ombuds
- Sources last checked
- Nov 18, 2026
- This record
- Assembled from 6 linked documents on 3 hosts · change log below: 1 dated entry, Nov 18, 2026 · human review confirmed Nov 18, 2026 · the change record across every page · the collection in numbers
Reproduced from the institution's own pages quoted below — potentially relevant official sources, not a determination of which one governs any case.
Stanford University's published sources on AI detection and academic integrity, quoted and linked below. These are potentially relevant official sources, not a determination of which one governs any case — the Board on Conduct Affairs's default generative-AI policy applies "[a]bsent course-specific or assignment-specific" rules, so a course syllabus is also a relevant source for your own situation. The process described here is the Stanford Student Conduct Charter of 2023, which governs cases filed May 2, 2023 or after. Confirm applicability with the institution. Any dates are quoted from the sources, not a deadline calculation performed for you.
No campus-wide detector; Stanford's own guidance declines to adopt one and cautions against relying on one alone
A named-vendor sweep (Turnitin, Turnitin AI writing indicator, SimCheck, Originality, Copyleaks, iThenticate, GPTZero, Originality.ai, Winston AI, Crossplag, ZeroGPT, Packback, Grammarly Authorship, Honorlock, Proctorio, Respondus, Examity) and a category sweep (Teaching Commons' technology-and-integrity guidance, the Office of Community Standards' policies and BCA guidance pages, and the Generative AI Policy Guidance for Academic Use) found no AI-text detector confirmed deployed university-wide in either direction. Teaching Commons' guidance (updated Nov 17, 2026; retrieved Nov 18, 2026) states:
The same page names Turnitin, Unicheck, and Grammarly only as examples of the kind of tool a department could choose to adopt, and notes "[s]ome departments have already adopted tools, notably the Computer Science department, for checking the originality of student work in programming languages" — a scoped, code-originality use distinct from AI-text detection in written coursework. Source: teachingcommons.stanford.edu — Guidance on technology tools for academic integrity.
For suspected unauthorized AI use specifically, the same guidance separates detection from the reporting duty: "For suspected unpermitted aid from generative AI tools, verification through plagiarism detection tools is not required before contacting OCS." This is instructor-facing guidance and is the closest first-party statement located on the evidentiary role of a detector score; no statement was found describing a detector score at Stanford as, in substance, not the sole basis for a finding, because no detector is confirmed deployed to generate one.
What Stanford's own pages say about how cases proceed
- Who may be present
- A Responding Student has the right "[t]o be provided a list of Conduct Counselors who may be consulted for advice and guidance throughout the conduct process"; a Conduct Counselor "must not have any other involvement in a concern." On recording: among the Conduct Advisor's duties is to "[e]nsure that all Panel proceedings are recorded," and a Responding Student has the right "[t]o be given, upon request, an audio recording of their Hearing Panel, excluding Panel deliberations, for the purpose of filing an appeal." — Stanford Student Conduct Charter of 2023, Sections II.D, II.F and V.B · communitystandards.stanford.edu — Stanford Student Conduct Charter of 2023
- What follows on the record
- "No record of any violation or alleged violation will be placed on a Responding Student's transcript." A finding through Mid-Level Review "becomes a part of the Responding Student's disciplinary record until receipt of their final degree in progress at the time of sanctioning"; a finding through High-Level Review "becomes a part of the Responding Student's disciplinary record indefinitely." — Stanford Student Conduct Charter of 2023, Section III · communitystandards.stanford.edu — Stanford Student Conduct Charter of 2023
The two questions an adviser raises first, answered from this institution's own published documents — or recorded as not stated in them.
The Stanford Student Conduct Charter of 2023 (retrieved Nov 18, 2026) governs "cases filed May 2, 2023 or after." A concern is filed with the Office of Community Standards, and "[w]ithin five days of receiving a concern, the Director of OCS or their designee determines the appropriate level of review": Alternative Resolution, Mid-Level Review, or High-Level Review. The standard of proof differs by level:
A Mid-Level Hearing Panel has three members (two students, one faculty/staff) and decides by agreement of two of three; a High-Level Hearing Panel has five members (three students, two faculty/staff) and decides by agreement of four of five. A Responding Student may "call relevant witnesses on their behalf at a Hearing Panel, and to cross-examine witnesses," and is guaranteed "at least thirty (30) days to prepare." Sanctions range from Alternative Resolution (which "must not include probation or suspension") through Mid-Level Review (probation or suspension "last at most one quarter") to High-Level Review, the only level from which expulsion is available; an expulsion sanction is further reviewed by the Provost. On appeal: "A Responding Student found responsible may appeal the decision of the Hearing Panel. An appeal must be filed within 20 days following notice of the Hearing Panel outcome," on one of five enumerated bases, including "[c]ompelling new evidence" and "[b]ias or conflict of interest." Source: communitystandards.stanford.edu — Stanford Student Conduct Charter of 2023. What any of this means for a particular case is for the institution and its process to determine; these are reproduced so you can read the originals in context.
Where the documents live
| Document | Location |
|---|---|
| Guidance on technology tools for academic integrity (Teaching Commons, updated Nov 17, 2026) | teachingcommons.stanford.edu — Guidance on technology tools (retrieved Nov 18, 2026) |
| Stanford Student Conduct Charter of 2023 (process, sanctions, records, rights, appeals) | communitystandards.stanford.edu — Stanford Student Conduct Charter of 2023 (retrieved Nov 18, 2026) |
| BCA Guidance & Recommendations (Generative AI Policy Guidance for Academic Use, adopted Oct 15, 2026) | communitystandards.stanford.edu — BCA Guidance & Recommendations (retrieved Nov 18, 2026) |
| About (OCS office contact) | communitystandards.stanford.edu — About (retrieved Nov 18, 2026) |
| Office of the Ombuds (home — independence, impartiality, confidentiality, scope) | ombuds.stanford.edu (retrieved Nov 18, 2026) |
| Why contact the Ombuds (students' reasons include "OCS questions"; contact details) | ombuds.stanford.edu — Why contact the Ombuds (retrieved Nov 18, 2026) |
Organizing your own drafts and records to bring to any of this: the records checklist. Capturing the pages above as they read today, and keeping your own dated record beside them: what to do with these sources.
Revision history of this page
2026-11-18 — Page created (scheduled, unattended build). All quotations retrieved this date from the teachingcommons.stanford.edu, communitystandards.stanford.edu and ombuds.stanford.edu pages linked beside them. The Teaching Commons guidance carries its own "updated in November 2026" line, dated Nov 17, 2026 at the byline; the BCA's Generative AI Policy Guidance states it was "adopted on October 15, 2026"; the Conduct Charter and Ombuds pages carry no on-page revision date beyond their own governing-date language ("applies to cases filed May 2, 2023 or after"). Detection-inventory sweep performed: a named-vendor sweep (Turnitin, Turnitin AI writing indicator, SimCheck, Originality, Copyleaks, iThenticate, GPTZero, Originality.ai, Winston AI, Crossplag, ZeroGPT, Packback, Grammarly Authorship, Honorlock, Proctorio, Respondus, Examity) and a category sweep (Teaching Commons, OCS policies and BCA guidance, the Generative AI Policy Guidance) found no AI-text detector confirmed deployed campus-wide; Turnitin, Unicheck and Grammarly are named only as examples of tools an individual department could adopt, and the Computer Science department's code-originality tool is named as a scoped, non-AI-text exception. NOT DISQUALIFIED: this is a genuine empty inventory at the university level — nothing is documented as ever having been deployed campus-wide, so there is nothing to have been disabled; Stanford's own guidance explains the absence as a deliberate non-adoption decision ("such tools have not been adopted for general use") rather than a removal, and its caution against relying on detection "solely" is carried into section 01 as the closest first-party statement found. No evidentiary-weight statement specific to a detector score was located, for the same reason. Process-based verification sweep performed (bounded, per the gw-institution-page method): no dedicated first-party page recommending oral or draft-based verification in place of detection was found within the bounded sweep (Teaching Commons' technology guidance, OCS policies, BCA guidance); this is recorded as none-published in tools/research/procedure-facts.json under process_verification, at the scope searched, rather than left blank. Ombuds/advocacy sweep: searched communitystandards.stanford.edu and ombuds.stanford.edu. Stanford's University Ombuds confirms service to "faculty, staff, students and postdocs at all Schools and Centers other than the School of Medicine," names "OCS questions" among students' own reasons for contacting the office, and describes its services in its own words as Independent, Impartial, Informal and Confidential; contact and scope are reported in the docket as found, with the Medicine exclusion and the office's own disclaimer that it accepts no formal complaints and conducts no formal investigations. Deliberate omission: the Charter's Section V.A (Rights of All Parties and Witnesses), Section V.C (Rights of the Reporting Party) and Section VI (Authority and Amendment) were located and read but are outside this page's two required procedure questions, so they are not quoted; the Student Conduct Penalty Code Bylaw referenced throughout Section III was not independently located and is named rather than linked. OCS's own About page publishes a central phone (650.725.2485) as visible text and a working "Email the OCS Here" mailto link, but the email address itself is never shown as page text, only as a link target; the docket therefore states the phone number and points to the link rather than reproducing an address this page's own evidence packet cannot independently confirm as published text. Nothing paraphrase-pending. Subreddit/forum demand scan not run (not the named gate for this entry; Priority C2 institutions are QUEUED directly). Internet Archive captures: to be added. Reviewer: Carrie Schluter (review confirmed 2026-11-18).
Spot an error or an outdated quotation? hello@gatheredwork.com — corrections are made on the record, in this log.