Duke University.
- Detection status
- iThenticate is confirmed, with "Duke has also added access to the iThenticate AI writing detection tool," available to all Duke faculty and staff plus graduate students with a Nursing or Nicholas School license; Duke's Center for Teaching and Learning separately states it does "not recommend AI detection software as a part of your AI policy because of false positive rates, biased detections, and software shortcomings" for coursework, and that "[d]etection results should never be the sole evidence of academic dishonesty"
- Office in these sources
- Office of Student Conduct & Community Standards (OSCCS) · Smith Warehouse, Bay 5, 114 South Buchanan Boulevard, Durham, NC 27708 · 919-684-6938 · conduct@duke.edu
- Ombuds or advocacy office
- Office of the Ombuds — "a confidential, impartial, informal, and independent resource for all members of the Duke community," reporting to the President and "not part of any other department, group or school" · 919-864-0772 · ombuds@duke.edu · ombuds.duke.edu
- Sources last checked
- Nov 20, 2026
- This record
- Assembled from 9 linked documents on 4 hosts · change log below: 1 dated entry, Nov 20, 2026 · human review confirmed Nov 20, 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.
Duke 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 Duke Community Standard leaves instructors discretion to set their own course-level AI rules, so a course syllabus is also a relevant source for your own situation, and some graduate and professional programs (for example the Graduate School's statistical-science program) publish supplementary processes not covered here. Confirm applicability with the institution. Any dates are quoted from the sources, not a deadline calculation performed for you.
Duke's own pages split on detection: discouraged for coursework, deployed for research
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 (the Center for Teaching and Learning's AI pages, the myResearchPath research-integrity hub, and IT/library pages) found two first-party results addressing different scopes of academic work, as at several other institutions reviewed in this queue.
For coursework, Duke's Center for Teaching and Learning (CTL) states, in guidance on writing an AI syllabus policy (page last modified Aug 25, 2025; retrieved Nov 20, 2026):
Source: ctl.duke.edu — Artificial Intelligence Policies in Syllabi. This is guidance for instructors drafting their own course policy — the Duke Community Standard otherwise leaves AI-use rules to each instructor — rather than a university-wide statement that a detector has been purchased and then disabled.
For research work, the Office of the Vice Provost for Research's myResearchPath hub states (no on-page revision date; retrieved Nov 20, 2026):
The same page adds a caution: "iThenticate is an aide to support human decision making, not a tool to make automated determinations of plagiarism or AI writing." On who may use it: "All Duke faculty and staff are eligible to use one of Duke's iThenticate licenses, accessible through SSO login. The School of Nursing and the Nicholas School of the Environment have each purchased additional licenses for use by their graduate students." Source: myresearchpath.duke.edu — iThenticate. This tool is scoped to research manuscripts, theses, and grant proposals, not to the Duke Community Standard process for ordinary coursework described in Section 02 below; no page located in this review states that iThenticate is used university-wide to evaluate undergraduate coursework for academic-dishonesty purposes.
What Duke's own pages say about how academic-dishonesty cases proceed
- Who may be present
- A respondent is entitled "to be accompanied by an advisor to the hearing (who must be a University community member)," and may separately request a Community Standard Advocate "trained by the Office of Student Conduct & Community Standards (OSCCS) to answer respondents' questions about the disciplinary process and provide support." On recording: participants "may not bring devices that capture or facilitate communication...into an in-person or virtual hearing room, unless authorized by OSCCS"; OSCCS itself "will make an audio recording of the conduct board hearing to be kept on file for three years." — Conduct Board Hearing · dukecommunitystandard.students.duke.edu — Conduct Board Hearing
- What follows on the record
- "Suspension will become a permanent part of a student's reportable disciplinary record, and transcript notation." A Reprimand, by contrast, "will not become a part of a student's reportable disciplinary record or a notation on a student's transcript"; Disciplinary Probation is part of the reportable record but not transcript-noted; Expulsion and Degree Revocation each carry "a permanent notation...on the student's permanent academic record." — Disciplinary Outcomes · dukecommunitystandard.students.duke.edu — Disciplinary Outcomes
The two questions an adviser raises first, answered from this institution's own published documents — or recorded as not stated in them.
Academic-dishonesty allegations against undergraduates begin with an instructor's incident report, which the Faculty-Student Resolution (FSR) appendix to the Duke Community Standard states may include "highlighted examples of suspected AI-generated content." An instructor may offer the optional, one-time FSR for "minor and appropriate cases of academic misconduct" by a student with no prior history, or refer the matter directly to OSCCS. If a case proceeds to a Conduct Board hearing, the applicable standard is stated on the hearing page: a respondent may "be found responsible only if the information meets a preponderance of evidence threshold." Source: dukecommunitystandard.students.duke.edu — Appendix B: Faculty-Student Resolution Process; dukecommunitystandard.students.duke.edu — Conduct Board Hearing.
A student found responsible by a Conduct Board panel may appeal: "The two grounds for appeal are: New information not reasonably available at the time of the hearing that is material to the hearing panel's decision; and/or Procedural error(s) that materially impacted the hearing panel's decision." The appeal statement is due "within three days of the date the hearing report is sent to the respondent," limited to five pages, and is reviewed by a three-person Appellate Board panel, which "typically" decides "within 20 business days." Source: dukecommunitystandard.students.duke.edu — Appealing a Conduct Board Hearing Decision. 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 |
|---|---|
| Artificial Intelligence Policies in Syllabi (CTL — detection discouraged for coursework) | ctl.duke.edu — AI Policies in Syllabi (last modified Aug 25, 2025; retrieved Nov 20, 2026) |
| iThenticate (myResearchPath — research/proposal AI-writing detection tool, access and scope) | myresearchpath.duke.edu — iThenticate (retrieved Nov 20, 2026) |
| Introduction to the Duke Community Standard (pledge, scope) | dukecommunitystandard.students.duke.edu (retrieved Nov 20, 2026) |
| Appendix B: Faculty-Student Resolution (FSR) Process | dukecommunitystandard.students.duke.edu — Appendix B (retrieved Nov 20, 2026) |
| Conduct Board Hearing (standard of proof, accompaniment, recording) | dukecommunitystandard.students.duke.edu — Conduct Board Hearing (retrieved Nov 20, 2026) |
| Disciplinary Outcomes (sanctions, transcript/record notation) | dukecommunitystandard.students.duke.edu — Disciplinary Outcomes (retrieved Nov 20, 2026) |
| Appealing a Conduct Board (CB) Hearing Decision | dukecommunitystandard.students.duke.edu — Appealing a CB Hearing Decision (retrieved Nov 20, 2026) |
| Meet the OSCCS Team (office location, phone) | dukecommunitystandard.students.duke.edu — Meet the OSCCS Team (retrieved Nov 20, 2026) |
| Office of the Ombuds — About Us and Contact Us | ombuds.duke.edu/about-us; ombuds.duke.edu/contact-us (retrieved Nov 20, 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-20 — Page created (scheduled, unattended build). All quotations retrieved this date from the duke.edu-family pages linked beside them; the CTL syllabus-policy page states "Last modified: August 25, 2025," and no other page used displays an on-page revision date. 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 (CTL's AI-and-teaching pages, the myResearchPath research-integrity hub, IT/library pages) found two scoped first-party results: CTL's syllabus-policy guidance states it does "not recommend AI detection software" for coursework, while myResearchPath documents iThenticate — "available...through SSO login" to all faculty and staff, plus graduate-student licenses at the School of Nursing and the Nicholas School — as having "also added access to the iThenticate AI writing detection tool" for research manuscripts and proposals. No current duke.edu page located in this review names Turnitin, by that name, as licensed or deployed for either plagiarism or AI-writing detection; a 2025-dated internal training announcement referencing a Turnitin vendor demo at the Fuqua School was located by search but could not be confirmed as reflecting a current, deployed tool and is not used as evidence. NOT DISQUALIFIED: because a documented AI-text detector (iThenticate) remains available in the research-integrity scope even though the separate coursework scope recommends against detector use, this does not meet the disqualification standard (no documented detector in use, or every detector found disabled or recommended against) — the same pattern as rochester, built earlier in this queue. Evidentiary-weight sweep: CTL's statement that detection results "should never be the sole evidence of academic dishonesty" and myResearchPath's caution that iThenticate is "an aide to support human decision making, not a tool to make automated determinations," are both carried into the detection-status line. Process-based verification sweep performed (bounded, per the gw-institution-page method): CTL's guidance that a detection result "can open a conversation with students if approached from a questioning perspective" is the closest statement found; no separate named conversation-based or draft/version-history method was located distinct from the FSR and hearing process already described in section 02, recorded in tools/research/procedure-facts.json under process_verification as none-published at the scope searched. Ombuds sweep: ombuds.duke.edu describes a single, university-wide Office of the Ombuds serving "all members of the Duke community" (students, faculty, and staff), reporting administratively to the President and "not part of any other department, group or school," self-described as "confidential, impartial, informal, and independent"; narrower school-specific graduate-student and medical-student ombudspersons were also found by search but are not used here since the university-wide office is eligible and available to the general student reader. Office contact confirmed on OSCCS's own team page: Smith Warehouse Bay 5, 114 South Buchanan Boulevard, Durham, NC 27708, 919-684-6938; conduct@duke.edu confirmed as the office's working email across the hearing-request, evidence-submission, and FSR-notification pages used above. Deliberate omission: school- and department-specific supplementary academic-integrity processes (for example, the Graduate School's statistical-science program) were located by search but not used as evidence for this university-wide page; the lede notes their existence. 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-20).
Spot an error or an outdated quotation? hello@gatheredwork.com — corrections are made on the record, in this log.