How to talk to your supervisor about using AI

Plenty of graduate students use AI tools quietly and hope the subject never comes up in supervision. It is an understandable instinct and a bad strategy. Your supervisor signs declarations about your work, may be asked directly about your methods at examination, and will eventually notice patterns in your drafts anyway. Undisclosed tool use discovered late damages the one relationship your thesis depends on.

The conversation is easier than the avoidance. Supervisors are not, for the most part, waiting to forbid things: they are waiting to be reassured about your learning, about integrity risk, and about their own accountability. This guide gives you the preparation, the framing, and a concrete agenda for the meeting, plus what to do with a skeptic, what to do with an enthusiast, and what to do with everything you agree afterwards.

One reassurance before the scripts: in most departments this conversation goes better than students fear. Supervisors have been fielding versions of it for a while now, most have settled views, and the discomfort of raising it is almost always smaller than the discomfort of being asked why you never did.

Why you should raise AI use before your supervisor does

Timing changes the meaning of the conversation. Raised by you, early, it reads as professionalism: you are treating AI like any other methods decision that needs supervisory sign-off. Raised by your supervisor after they notice something, it reads as a confrontation, and you spend the meeting defending instead of planning.

There are structural reasons too. Many universities now require AI disclosure in the thesis, and some ask supervisors to countersign it; your supervisor cannot sign a statement they are hearing about for the first time at submission. Examiners sometimes ask supervisors how the work was produced. And norms are shifting under everyone's feet: an agreement made early protects you if your department tightens its rules mid-degree, because you can show your use was discussed and approved as you went.

There is a purely practical gain as well. Supervisors know where the local lines are in ways no policy page captures, and five minutes of their institutional knowledge can save you from an honest mistake that no amount of careful reading would have prevented.

Do your homework before the meeting

Walk in with the policy read and your own position worked out. The meeting goes better when you are asking for confirmation of a considered plan, not for permission in the abstract.

• Read every layer of your university's AI policy and bring the relevant clauses with you
• List the specific uses you want to make: literature discovery, summaries of papers you then read in full, statistics checking, editing passes, grounded drafting you verify against sources
• List the uses you will not make, and say so unprompted: it is the fastest way to establish good faith
• Prepare one concrete example of your process from question to verified claim, using real material from your project
• Check what your funder and your target journals say, since those rules bind you regardless of what your supervisor prefers
• Decide how you will log AI use as you go, so documentation is an offer you make rather than a burden they impose

Specificity is the whole trick

The preparation list matters because specificity is persuasive. A question like whether you can use AI invites a values debate that nobody wins. A question like whether you may use grounded drafting for the literature review, with every claim verified against the source PDF and a log kept, invites a decision. Supervisors say yes to plans and no to vibes.

Specificity also protects you later. A vague blessing covers nothing when a panel asks what exactly was agreed; a list of named uses covers each of them.

Frame the conversation around research quality

Do not open with the tools. Open with the standards: you want every claim in your thesis traceable to a real source, every citation verifiable, and a record of how the work was made, and you want to agree how AI fits inside those standards. This framing addresses what supervisors actually worry about: whether you are learning the craft, whether something fabricated will surface in front of examiners, and whether they will be held responsible for either.

Concretely, that means talking about verification rather than generation. A supervisor who hears that you use a tool that drafts text hears risk. A supervisor who hears that nothing enters your draft unless it is grounded in a paper you hold, and that you can show the check for any sentence, hears process. Same technology, different conversation.

If you work in CiteDash, this framing is simply a description of how the platform behaves. If you work in general-purpose tools, the framing is a commitment you are making, so be sure your actual habits can cash it before you offer it.

Questions to ask your supervisor about AI

An agenda keeps the meeting from dissolving into vague reassurance in either direction. Take notes in the meeting itself: the answers are the skeleton of the written agreement you will send afterwards, and visibly writing them down signals exactly the seriousness you want to project. These six questions cover the ground:

• Which uses do you consider acceptable at each stage: literature work, analysis, drafting, revision?
• How would you like me to document AI use in my notes, and how much detail do you want to see routinely?
• Do you want prompts or transcripts for anything, and for which kinds of work?
• How should the final thesis disclose this, and will you review the statement before submission?
• What would you need to know before signing any declaration about the thesis?
• Can we put a recurring ten minutes on this each term, since both the tools and the rules keep moving?

Show your process, not just your outputs

Abstract assurances persuade nobody. If you can, show the process live: a claim in your draft, the source it resolves to, and the verification that ties them together. In CiteDash this trail exists by construction: claims are grounded in the full-text PDFs the platform holds, citations are database objects that resolve to real papers, and the Fact Checker verifies each claim against its source before it reaches you.

Whatever tools you use, the demonstration to aim for is the same: pick any cited sentence and show where it came from. A supervisor who has seen that once will trust your workflow in a way no policy discussion achieves, and a workflow that cannot survive that demonstration is one you should change regardless of what your supervisor thinks. Our guide to AI that does not make up references explains what separates verifiable workflows from the rest.

If your supervisor is skeptical about AI

Skepticism is usually specific even when it sounds general. Most of it decomposes into two fears: fabricated citations reaching examiners, and you outsourcing the understanding your degree certifies. Address the fears rather than the mood. For the first, show the verification trail. For the second, describe what stays yours: the questions, the argument, the interpretation, the reading.

Then make it cheap to say yes. Propose a limited trial: one bounded use, full transparency, review in a month. Offer transcripts and logs without being asked. Accept boundaries you privately think are overcautious, at least initially: a working agreement you can revisit beats a standoff you technically win. And if the answer is still no on some uses, respect it and get the permitted scope in writing, because a clear no is far better to hold than an ambiguous maybe.

If your supervisor is enthusiastic about AI

An enthusiastic supervisor is a different risk. An airy instruction to use whatever you like is not a policy, and it will not protect you if a departmental panel or an examiner asks questions later, because casual verbal permission has a way of being remembered vaguely at exactly the wrong moment. University policy binds you both regardless of your supervisor's personal views.

So push politely for the same specifics you would want from a skeptic: which uses, what documentation, what disclosure. If your supervisor suggests uses the policy prohibits, say so in the meeting; you are the one whose degree is at stake. Enthusiasm plus a written agreement is the best possible outcome. Enthusiasm instead of one is a trap.

Put the agreement in writing

After the meeting, send a short email: here is what we agreed I will use AI for, here is what I will not do, here is how I will document it, here is the disclosure plan, tell me if I have any of this wrong. It reads as diligence, takes five minutes, and creates the record both of you will want if anyone ever asks.

Keep the thread alive. When your use changes, when a new tool enters your workflow, when the university updates its policy, add a line to the record and copy your supervisor. The agreement should evolve with the work; an agreement from your first year that no longer describes your practice is barely better than none.

Close the loop with the written disclosure

The conversation's final output is not the meeting but the paragraph in your thesis. Agree with your supervisor what the AI use disclosure statement will say, where it will sit, and when they will see a draft of it. CiteDash can generate a disclosure from your actual platform usage, alongside an originality pre-check and submission readiness checks, which turns the declaration from a memory exercise into a report.

A disclosure your supervisor has reviewed before submission is a disclosure that will not surprise anyone at examination. That is the whole goal of the exercise: by the time an examiner asks how AI figured in this thesis, everyone in the room already knows the answer, and it is written down.

The bottom line on discussing AI with your supervisor

Raise it first, raise it early, and come prepared: policy read, uses listed, process demonstrable. Frame everything around verifiability, ask concrete questions, and convert the answers into a written agreement you maintain as the work evolves. Skeptics get demonstrations and bounded trials; enthusiasts get pinned down as politely as skeptics get persuaded. The students who struggle with this conversation are almost never the ones who had it too early.

And if the first conversation goes badly, remember that it is a conversation, not a verdict. Policies evolve, supervisors update their views, and an agreement revisited each term has plenty of chances to improve.