Being accused of using AI on a paper is stressful, but the next steps are usually clear: stay calm, find out your school's policy and process, gather your notes, drafts and version history, and get ready to explain your own work in your own words. This guide walks through each step so you can go into the conversation prepared. It isn't legal advice, and it can't tell you how your school will decide.
First, slow down
When a message like this arrives, the urge is to fire back a long reply right away. Wait a little.
- Read the message carefully. Is it a question, a request to meet or a formal notice? Those are different situations.
- Don't reply in anger. A short, polite response that confirms you received the message and are happy to meet is enough for now.
- Remember that a conversation is often the first step. Many professors want to hear from you before drawing any conclusions.
If your professor simply wants to meet, also read your professor wants to meet about your paper: how to prepare.
Find out the policy and the process
It's fair to want to understand which rules apply and what happens next. It's reasonable to ask, politely:
- What's the AI policy for this course? Check your syllabus first. Policies vary a lot between schools, departments and even individual courses.
- What is the concern based on? A passage that reads differently, a detection tool score, missing citations or something else.
- Is this an informal conversation or a formal academic integrity process?
- What are the steps and the timeline?
- Can I bring materials, and can I bring someone with me? Some schools allow an advisor or support person, and some don't.
Your student handbook usually describes the academic integrity process. Many schools also have an academic integrity office, a student advocate, an ombuds office or an academic advisor who can explain how the process works. If you have legal questions, talk to a qualified professional. This guide can't advise you on that.
About AI detection tools
If a detection tool is part of the concern, it helps to know a few things:
- Detection tools give estimates, not certainty. They can be wrong.
- Schools and instructors use them differently. Some treat a score as a reason to talk, not a final answer. Ask how your school uses it.
- Don't run your paper through other tools or rewrite it before the meeting. That changes what you turned in and doesn't help you explain the work itself.
The most useful thing you can do is focus on what you can show and explain: how you actually worked.
Gather your materials
Bring whatever shows how your paper came together.
- Version history. Google Docs keeps it under File, then Version history. Microsoft Word keeps version history for files saved to OneDrive or SharePoint. Other editors have similar features.
- Notes, outlines and brainstorming, in whatever form you kept them.
- Your sources, with your highlights or annotations, plus any library database search history.
- Earlier work from the same course, if it's relevant to how you usually write.
- Any related messages, such as emails with the professor or a writing center appointment.
Put it in a rough timeline so you can walk through it in sequence. Be realistic about what these materials do. No single item settles who wrote a paper. They help you explain how you worked and give the conversation something concrete to look at.
If you don't have drafts because you write in one file and overwrite as you go, that's common. Your notes, sources and ability to explain your choices matter even more then. Never create or backdate drafts after the fact. That's deceptive and makes things much worse.
Get ready to explain your own work
In the meeting, you'll probably be asked to talk about the paper itself. Practice explaining:
- Your main argument, in two sentences.
- Why you structured the paper the way you did.
- Why you chose each major source and what it adds. See how to explain your sources.
- How the paper changed from your first draft to the final version. See how to explain your writing process.
- Specific sentences, terms or phrases the professor might point to.
Questions you may hear
- Can you summarize your argument without looking at the paper?
- How did you come up with this topic?
- What does this term mean, and why did you use it here?
- Walk me through how you wrote this paragraph.
- How did you find this source? What's its main point?
- What changed between your drafts?
- Did you use any AI tools at any point? What for?
Practice answering these out loud, not just in your head. Speaking shows you which parts you understand well and which you only recognize on the page. Use the Professor Meeting Prep Sheet to list what to bring and what to expect, then practice with a friend or classmate asking follow-ups. An AI practice coach that asks spoken questions about your own paper can give you more rounds of practice. For more on this kind of conversation, see the explain your work page.
If you did use AI tools
Many courses allow some uses of AI (brainstorming, for example) and don't allow others. The syllabus usually sets the line. If you used an AI tool in any way, be honest about what you used, what you used it for and which parts you wrote yourself. Misstating what happened is a separate problem and usually makes the situation harder. Being accurate is the right thing to do, and it gives the conversation a clear starting point.
In the meeting
- Listen first. Let the professor explain the concern fully.
- Ask clarifying questions. "Which section are you looking at?" is a fair question.
- Walk through your materials when they're relevant, in sequence.
- Explain your choices in plain words. Specific details help more than general statements.
- Say when you don't remember. "I'm not sure, but my notes show..." is honest and useful.
- Stay calm and respectful, even if you feel frustrated.
- Take notes, and ask what happens next and when before you leave.
After the meeting
Write down what was discussed while it's fresh. If next steps were agreed, a short, factual email summarizing them helps everyone stay on the same page. If the matter goes to a formal process, follow its steps and deadlines. Many schools have a way to respond to or appeal a decision; your handbook explains how.
For future papers, keep version history on and save your notes. It's a simple habit that keeps a record of your own work.
A quick checklist
- You've read the course AI policy in the syllabus.
- You know whether this is an informal conversation or a formal process.
- Your version history, notes and sources are gathered in one place.
- You can explain your argument and key choices out loud.
- You're ready to answer honestly about any tools you used.
- You have a list of questions to ask about next steps.
