Project Summary
This research project explores how instructors evaluate student writing in the AI landscape: the process that they follow and the tools and resources they use to support their process. The project draws on interviews with University of Chicago instructors who teach writing-intensive courses, along with tool probes that surfaced how instructors interpret AI-detection, authorship, source-attribution, and writing-process tools.
The artifacts being developed from this research are intended to support two audiences: instructors navigating writing assessment in courses where AI tools are available, and designers building tools that aim to support instructors without replacing their judgment.
Tools and Features Covered
Tools directly covered in the research materials:
- Pangram (AI detection scores, AI-assistance categories, segment-level analysis, confidence indicators)
- Process Feedback (writing-process reports, editing time, revision patterns, copy-paste events)
- DraftMarks (human-AI co-writing traces, AI-generated content, revision intensity, deleted or unused AI text)
Related tools with overlapping features:
Feature categories covered by the study include text-based AI detection, citation and source verification, writing-process records, and student-AI interaction and source attribution.
Summary of Findings
A Framework for Understanding Student Writing in the AI Landscape
The framework presents four steps that may arise as instructors evaluate student submissions for potential AI use.
It was synthesized from interviews with University of Chicago instructors who teach writing-intensive courses, with the goal of identifying how instructors evaluate student submissions in the context of potential AI use and the considerations in each step of the evaluation process.
Ways to Use the Framework
The framework is not intended to prescribe a single process, as an instructor's process is shaped by their own professional values and teaching contexts. Instead, instructors can use it to reflect on their current practices, make implicit evaluation decisions more explicit, and consider resources or tools that may be useful in their own classroom contexts.
Example uses include:
- Reflect on their current evaluation process: Identify the steps, sources of information, and judgments they already rely on when questions about AI use arise.
- Check assumptions before acting: Consider whether an initial concern may be shaped by expectations about a student, their writing ability, or what student writing "should" look like.
- Plan conversations with students: Decide when and how to ask students about their drafting, revision, source use, or AI use in ways that provide additional context.
- Revisit course and assignment design: Use recurring concerns to identify where AI policies, assignment expectations, process documentation, or instructional scaffolding could be made clearer.
- Compare practices with colleagues: Use the framework as a shared vocabulary for discussing how instructors make judgments and respond to similar situations across courses.
Step 1: Notice What Raised the Question
Step 1: Notice What Raised the Question
As the instructor is reading through the student submission, certain aspects in the submission may raise the instructor's concern about potential AI use. These initial reactions provide a signal that further review is needed, but often do not provide enough information to make a decision.
The table below provides the different aspects that raise the instructor's concern and some questions that instructors ask themselves during the process.
| Aspects | Questions for Consideration |
|---|---|
| Linguistic and Stylistic |
|
| Idea and Content |
|
| Course Considerations |
|
Step 2: Gather Observations
Step 2: Gather Observations
If the first read raises concern, instructors often seek additional information that can help place that concern in context. The table below presents the different sources of information that instructors reference, the questions that they consider, and the limitations that instructors recognize. Alongside these sources, instructors also reflected on their own assumptions and potential biases about the student and how these might shape their interpretation of the submission.
| Source | Questions for Consideration | Limitations |
|---|---|---|
| The submitted work | Instructors may start with re-reading the student submission to identify specific concerns that they have.
|
|
| The student's prior work | When available, instructors may compare the submission with prior assignments, drafts, in-class writing, or other writing samples.
|
|
| The student's writing process | When available, instructors may use tools like Google Docs version history or Process Feedback to understand a student's writing process.
|
|
| Classroom and instructional context | When available, instructors may consider using their interactions with the student in class discussion or office hours.
|
|
| External Support and Tools | When available, instructors may ask colleagues or the Office of College Community Standards (OCCS) for additional support when evaluating a student submission.
When available, instructors also might use AI detection tools or writing-process tools to provide additional information for them to consider. |
|
Step 3: Reflect Before Choosing a Response
Step 3: Reflect Before Choosing a Response
Before choosing a response, instructors often considered these three aspects: learning goals, their certainty, and the stakes.
| Category | Questions for Consideration |
|---|---|
| Learning goals |
|
| Certainty |
|
| Stakes |
|
Step 4: Respond
Step 4: Respond
Instructors described several possible responses, depending on the available context, course policy, and learning goals:
| Response | Questions for Consideration | Limitations |
|---|---|---|
| No formal action | Grade the submission on its merits when uncertainty remains or the available observations do not support further action.
|
|
| Conversation | Direct Conversation: The instructor directly raises concerns about a student's submission with the student and invites them to discuss their work, writing process, or use of AI.
Indirect Conversation: The instructor asks more broadly about the student's drafting and writing process without directly raising concerns about potential AI use.
|
|
| Grading response | Apply the course policy through a grading adjustment when the available context supports treating the case as a course-policy issue. Instructors may also choose to leave comments on the student's paper denoting specific areas that raised their concern.
|
|
| Resubmission or alternate assessment | Offer the student a chance to demonstrate their learning through a revised submission or a different assessment format, giving the student another opportunity.
|
|
| Consultation or formal reporting | Consult teaching colleagues, the Office of College Community Standards (OCCS), or the appropriate Dean of Students office, and follow institutional guidance when formal reporting is appropriate.
|
|
Tools for Understanding Student Writing in the AI Landscape
This summary organizes tools by the kinds of information they provide. The table below identifies the tools directly covered in the research materials and related tools with overlapping features. The goal is not to rank or endorse tools, but to clarify what each tool family can show, where its outputs may be useful, and what risks instructors may want to consider before using it in a course.
Across our interviews with instructors who teach writing-intensive courses at the University of Chicago, instructors treated these tools as sources of context. They were most useful when they helped instructors understand how a submission may have been produced, identify concrete points for conversation, or reduce manual checking work. They were least useful when they appeared to make a judgment that instructors saw as pedagogical, contextual, or relational.
Tools Directly Covered in the Research Materials
| Tool | Features covered or relevant to this study | Related tools with overlapping features | How instructors might use this information |
|---|---|---|---|
| Pangram | AI detection scores; AI-assistance categories; segment-level analysis; confidence indicators. | Turnitin AI Writing Report; GPTZero; Copyleaks AI Detector. | Use detector outputs as one contextual signal when deciding whether to gather more information, re-read specific passages, or prepare questions for a conversation with the student. |
| Process Feedback | Writing-process reports; editing time; revision patterns; copy-paste events. | Google Docs version history; Draftback; Grammarly Authorship. | Use writing-process records to understand how a submission developed and to support reflective conversations about drafting, revision, source use, and effort. |
| DraftMarks | Human-AI co-writing traces; AI-generated content; revision intensity; deleted or unused AI text. | Grammarly Authorship. | Use source-attribution or AI-interaction records to discuss what role AI played in the writing process, what the student accepted or changed, and how those choices relate to course expectations. |
1. Text-Based AI Detection
1. Text-Based AI Detection
Tools
- Directly covered tool: Pangram
- Related tools: Turnitin AI Writing Report, GPTZero, Copyleaks AI Detector
What it shows
- Document-level scores
- Paragraph- or sentence-level highlighting
- AI-generated vs. AI-paraphrased categories
- Word- or phrase-level signals
- Confidence indicators
How it works
These tools analyze submitted text and estimate whether portions resemble writing produced or revised by generative AI. Different tools report the estimate at different levels: overall document, segment, paragraph, sentence, or phrase.
What it can help with
- Document-level results can help instructors decide whether additional review is needed, especially for essays with very high or very low AI detection scores.
- Paragraph- and sentence-level flags can provide concrete reference points for instructors to use in their conversations with students without relying on these indicators to signal AI use.
Where it falls short
- Middle-range AI detection scores (e.g., 40-70% AI-generated) are difficult to interpret.
- Sentence or word-level AI detection results can conflict with instructor judgment, especially when a sentence reflects a student's ordinary academic register, an attempt at sophisticated writing, or weak writing.
- Word-level signals are especially fragile because vocabulary choices can reflect many things besides AI use.
- Students can access AI detection tools themselves. It is possible for a student to run their essay through detection tools repeatedly until it scores 0% AI-generated.
Considerations for classroom use
- Are students aware of the usage of the tools being used? Are they allowed to see the results?
- What type of AI detection tool will you use? How did the company evaluate the reliability of the AI detection tool (e.g., false positives, false negatives)?
- How will AI detection tools be used for student submissions? Will all student submissions be run through an AI detection tool or will only suspected student submissions be run through an AI detection tool?
- What is the AI detection score threshold that will determine whether further action is required? Will this threshold be shared with students?
- Does your departmental policy require a formal case for an AI detection score above a certain threshold?
- What will happen if the tool shows a result you disagree with?
2. Citation and Source Verification
2. Citation and Source Verification
Tools
- Directly covered tool: Not represented by a standalone tool in the research materials
- Related tools: Copyleaks Citation Checker, Turnitin Similarity, library or database searches
What it shows
- Checks for fabricated, inaccurate, or misattributed sources
- Comparison against source databases
- Citation or similarity reports
How it works
These tools compare references, quotations, or source claims against existing bibliographic records, web sources, or submitted-text databases.
What it can help with
- Instructors responded positively to citation verification because its outputs are easier to verify.
- A source that does not exist, an inaccurate page range, or a misattributed quotation can be verified and discussed with students to promote better citation practices.
- The feature also reduces manual checking work required by instructors.
Where it falls short
- Citation problems do not, on their own, explain how a text was produced.
- They may reflect AI use, weak research practices, citation-management errors, or misunderstanding of the assignment.
Considerations for classroom use
- What is the procedure for checking citations? Will you check every citation or only ones that look unusual?
- To what extent do different citation issues raise concerns in the context of your course, and how serious is each type of issue?
- What are the existing citation practices that are taught in class?
3. Writing-Process Records
3. Writing-Process Records
Tools
- Directly covered tool: Process Feedback
- Related tools: Google Docs version history, Draftback, Grammarly Authorship
What it shows
- Version history
- Replay of document creation
- Insertion and deletion timelines
- Copy-paste history
- Editing time
- Revision patterns
How it works
These tools show how a document unfolded over time, either by replaying revision history or summarizing process traces such as time, pauses, revisions, and copy-paste events.
What it can help with
- Process records can make an otherwise invisible writing process visible.
- Copy-paste history was especially useful to instructors because it can show what entered the document all at once and sometimes where it came from.
- Aggregated process summaries can help instructors understand effort, revision, and drafting behavior without watching every keystroke.
Where it falls short
- Replay tools can be time-consuming to review and can feel invasive.
- Instructors worried that visible monitoring could change how students write and damage classroom trust.
- Process records are also incomplete: students can retype generated text, draft elsewhere, use another device, or move text between documents.
Considerations for classroom use
- What will you do if some students prefer to draft on paper, in another application, or with assistive technology? Would requiring students to write within a given document disadvantage anyone in the course? Are there alternatives that students can use?
- What will be your procedure for reviewing the process outcomes for each student? On an "as needed" basis? Or all students?
- Will you communicate the types of writing-process tools you use and how you use them to your students? This includes the types of information captured from the tool and how you might use this information in your evaluation process.
- How might writing-process-based insights support students' learning or structure conversations with students about their writing process?
- Which of these features are you comfortable and uncomfortable using? Why? Writing-process reports can vary widely in how much detail they provide to you about the student's writing process.
4. Student-AI Interaction and Source Attribution
4. Student-AI Interaction and Source Attribution
Tools
- Directly covered tool: DraftMarks
- Related tools: Grammarly Authorship, Clarity by Turnitin
What it shows
- Whether a passage was authored by the human writer or generated by AI
- The prompt and instruction used when a passage was AI-generated, when that exchange is captured
- The complete text of the AI-generated output
- Version snapshots marking when AI-generated text was inserted, fully removed, or substantially edited
How it works
DraftMarks tracks writer-AI interaction across a few common setups: writing and AI chat in separate windows (e.g., a Google Doc alongside a ChatGPT tab), an AI assistant built directly into the writing tool, or an ambient AI assistant added through a browser extension. It classifies text mainly by whether it can be mapped to the writer's own keystrokes: text typed by the writer is marked as human-authored, while text that can't be traced to keystrokes, including pasted content that didn't originate in the same app, is marked as AI-generated. When the AI chat happens in a separate window, the tool infers AI origin from paste and keystroke patterns rather than directly capturing the prompt exchanged with the chatbot.
What it can help with
- Interaction records provide a record rather than a prediction, which instructors found useful.
- Seeing that a passage was generated, pasted, revised, or typed can clarify the scope and role of AI assistance.
- These records can also support conversations about acceptable use: what the student asked AI to do, what they accepted or changed, and whether they understood the resulting text.
Where it falls short
- These tools only capture activity inside the tracked setup (the supported editor, extension, or paired chat window).
- When writing and an AI chatbot are in separate windows, the tool infers AI authorship from paste and keystroke patterns rather than directly recording the prompt and response, so the captured "prompt" may be incomplete or approximate.
- A student can use an AI chatbot or workflow the tool isn't set up to track, another device, another browser, a private window, or any other untracked path.
- The record may be incomplete even when no one intended to evade it.
Considerations for classroom use
- What type of support from AI does your course policy permit?
- Does your policy distinguish AI-generated, AI-assisted, feedback from AI on student written work, and grammar or spelling assistance?
- Will students declare their AI use themselves, will the tool record it, or both?
- If collecting student self-declaration, will it be in the form of listing AI assistance? Or asking for a reflection assignment on how AI contributed to their process?