Using AI in Your Research and Writing: Guidelines for My Students

Branislav L. Slantchev (slantchev@ucsd.edu)
Department of Political Science, University of California San Diego

October 30, 2026

TL;DR Think of AI as a well-read colleague giving you feedback rather than as a research assistant who can do things you can't. As with a colleague, not all advice will be good and worth taking, but a lot of it will deserve attention. Never rely on AI output you can't verify yourself. For the parts that carry the argument (the model, the methods, the analytical choices) verifying isn't enough: you have to understand them, because that is where the argument lives. And unlike a human collaborator, AI shares none of the responsibility: if it's in your paper, it's yours.

The rest of this note explains what that means in practice: why I care how your drafts are produced, how to get the most out of AI as a colleague, where the line is for writing, models, and data, and what you owe your coauthors and other readers. Near the end is a stage-by-stage workflow with example prompts, and a checklist to run before anything goes out.

Why I care how your drafts are produced

When I read your drafts, I am reading to understand your ideas. Bad writing is useful to me: an awkward paragraph or a confused transition usually points to a problem in your reasoning or analysis, and that is exactly where I can help. If you smooth the draft over with AI before I see it, the problem does not go away. It just goes underground, and it surfaces anyway, usually late in the process, when it is far more costly to fix (a job talk, a referee report, a committee meeting).

So when you send me a draft, send me your draft. I would much rather read something rough that shows me how you think than something polished that hides it. That includes the language: drafts for me do not need polished English. Polishing comes later, for outside readers (see the section on English below). This is part of my job as your advisor, and it is the main reason the rules below are stricter for you than for anyone else whose work I read.

Good uses: AI as a well-read colleague

The right model is a well-read colleague who is always available and never tired of reading your drafts. Write first, then ask it to read. Like any colleague, it will sometimes be wrong, miss the point, or push you toward its own view of the paper, so weigh its advice the way you would weigh a colleague's: take what survives scrutiny and ignore the rest. But a lot of what it says will deserve your attention, and used this way it is very efficient. Some things that work well:

None of this is a substitute for thinking. It is a way to get feedback faster and more often than you could get it from people.

Bad uses: letting AI build the argument

The line that matters is between using AI to get feedback or fix language and using it to build the argument for you. Framing the question, positioning it against the literature, deciding what the contribution is, and structuring the argument are intellectual work. That work is your job, and it is what I am trying to help you learn to do. AI may suggest an idea, mechanism, or approach you had not considered, just as a colleague might. You can pursue it, but you must work out why it makes sense, develop it yourself, and decide whether it survives scrutiny. Adopting a suggestion is not the same as understanding it.

In practice, do not:

The test I use: if I asked you to explain a paragraph without looking at it, could you? If not, it is not yours yet.

Data, code, models, and methods: verify, understand, own

Many people worry about AI-written prose and think nothing of having AI collect, collate, and analyze data, or write the programs that do it. In my view this is backwards. With English text you can at least read the output and see where it departs from what you meant. With a model, an estimation, or a program, the problems are often invisible unless you already have the skills to see them, and people often turn to AI precisely because they lack those skills. Three rules apply here, and they apply to different kinds of work.

Verify what is mechanical. Some tasks really are mechanical: the syntax of R or C++ once you know what the program should do, data formatting, reference management, language editing. AI can do these for you, but you must be able to tell when it got them wrong. For code, that means testing it on simulated data with known answers, checking special cases by hand, and comparing against an independent implementation. The standard is not whether you could have written it yourself, but whether you can tell when it is wrong.

Understand what carries the argument. A formal model is an argument (Slantchev 2017, 2020b). The math is a form of accounting: it guarantees that the conclusions follow from the premises. The argument itself lives in the choices around the math: which premises go in, how the interaction is structured, what the players know and want, and how the parameters are interpreted. None of these choices is rigorous, and all of them are yours to make and defend. If you do not understand why the result holds, you do not have the argument, and the whole point of the exercise is lost.

Checking the math is not enough. When Fey and Ramsay (2007) argued that mutual optimism cannot cause war, I could follow every step, everything seemed correct, the conclusion followed, and I still did not believe it. It took building alternative models to discover that an innocuous-looking definition was doing all the work (Slantchev and Tarar 2011; the story is in Slantchev 2017). I really do not like solving models, but I do not outsource the analysis, not even to smart graduate students, because when you do not understand how the analysis works, you do not understand what the model is telling you. A simple test: if you cannot explain the behavior of your agents without reference to equations, you have a problem.

Be especially careful with AI when building models. It is very good at producing a model that yields whatever result you ask for, usually through some quirky assumption that buys the conclusion while the rest of the math is ornamentation. You can rationalize almost anything this way, up to bank presidents setting their pants on fire in the street (Postrel 1991; Slantchev 2017). If you do not understand the model, you will not see where the rabbit went into the hat, but your referees will. Do not formalize just to give your hypothesis a formal gloss, and do not ask AI to construct the model for you.

The same holds for statistical methods and the choices made in analyzing the data: specification, identification, measurement, what to control for. These are substantive claims, not mechanics. Check what your variables actually measure, not what they are called. A widely used "immediate balance of forces" variable (Huth and Russett 1984) was treated in later work as information revealed during a crisis (Fearon 1994; Signorino and Tarar 2006), but it is built entirely from indicators observable before the crisis. Researchers trusted the label instead of the coding (Slantchev 2017). AI output is full of plausible labels.

Code is not purely mechanical either. Working out the algorithmic solution to a problem forces you to think it through, which is why writing code often clarifies your thinking. And code embeds choices: how missing data are handled, which observations a merge silently drops, default standard errors, bandwidth selectors, solver tolerances. AI-written code makes these choices for you, often by default and without telling you. Verifying code means knowing what choices it made, not just that it runs.

Own all of it. Scholars routinely collaborate with people who can do things they cannot, and we rely on those colleagues to do the work properly. This mostly works, but it occasionally ends in scandal when someone in the research pipeline turns out to have been less than careful or honest with the data or analysis. Even then, "my coauthor was responsible for the analysis" is barely acceptable, because everyone whose name is on the paper has to stand behind its results. "The AI did it" is not acceptable at all. A human collaborator shares the responsibility; AI shares none of it. If you do not understand what the AI did, nobody in the pipeline does.

I have found math errors in papers more than once that turned out to come from students using AI without catching the problem. That is the kind of mistake that can sink a paper or a reputation. In practice:

If English is not your first language

We are not in the English Department, and research is evaluated on its ideas and on how well it was done. But a weak grasp of idiomatic English can obscure good ideas, and readers do penalize that, fairly or not. Using AI to improve your language is legitimate, in the same way that hiring a copyeditor always has been. I see no principled difference between the two.

A few cautions, though:

This is advice for native speakers as well. Keep working on your own writing. Read widely and emulate writers you admire. Sword (2012) and Thomas and Turner (2011) are excellent on prose in general, and McCloskey (2019) and Thomson (2001) are indispensable for academic work in economics and formal theory. AI can help here if you give it examples of writing you want to emulate and discuss with it why you like that style, or give it the principles from the books above. Together you can build a list of principles of your own to apply consistently and revise as your writing improves.

Disclosure and coauthorship

When someone asks you to write something (a referee report, a memo, a section of a joint paper), disclose substantive use of AI to generate text, code, or analysis; asking for feedback on your own draft is different. There is no good reason to hide it, and finding out after the fact damages trust far more than the AI use itself would have. For confidential work, including referee reports, first check whether AI use is permitted at all by the journal or institution.

My rules for papers we write together (the first three are about AI; the last is how I run every joint paper, AI or not):

What not to share with AI

Anything you paste into an AI tool leaves your control, and some material is not yours to share:

If the university provides an AI tool with data protections, use it for anything sensitive. Those protections do not override journal or IRB rules.

Readers outside our group

Norms around AI are unsettled, and colleagues hold very different views. When I evaluate other people's work, I judge the ideas and the research. Some readers, however, will refuse to take seriously anything they suspect was AI-generated, and some will assume it from polished or uneven prose alone. You cannot reliably control what readers suspect, especially as AI-generated prose improves. What you can control is the quality of your work and your ability to explain it:

A workflow, start to finish

Here is what this looks like over the life of a paper. At every stage the pattern is the same: you do the thinking and make the choices, AI reads, questions, checks, and handles the mechanical parts, and you verify what comes back. The prompts are examples, not scripts.

A few habits make the interaction much more useful:

Know what its critiques are worth:

The upshot: when AI says something is fine, that is no proof that it is. You will have to stand behind the claims on your own. When AI says something is wrong, that might be a signal of a real problem, or it might not. You will have to decide whether it is, and what to do about it.

Before you send anything out

Disclosure: how this document was written

I wrote this policy with Claude, following the approach it describes. The original argument came from a reply I wrote to a colleague about AI and student writing, and from my work on using formal models. Claude turned that into a set of guidelines, which I edited iteratively using its feedback until I was satisfied that the result correctly conveys my ideas. I then circulated the draft among colleagues and incorporated their feedback. I stand behind every word in this document.

References

Fearon, James D. 1994. "Signaling versus the Balance of Power and Interests: An Empirical Test of a Crisis Bargaining Model." Journal of Conflict Resolution 38: 236–269.

Fey, Mark, and Kristopher W. Ramsay. 2007. "Mutual Optimism and War." American Journal of Political Science 51: 738–754.

Huth, Paul, and Bruce Russett. 1984. "What Makes Deterrence Work? Cases from 1900 to 1980." World Politics 36: 496–526.

McCloskey, Deirdre N. 2019. Economical Writing: Thirty-Five Rules for Clear and Persuasive Prose. 3rd ed. Chicago: University of Chicago Press.

Postrel, Steven. 1991. "Burning Your Britches Behind You: Can Policy Scholars Bank on Game Theory?" Strategic Management Journal 12: 153–155.

Signorino, Curtis S., and Ahmer Tarar. 2006. "A Unified Theory and Test of Extended Immediate Deterrence." American Journal of Political Science 50: 586–605.

Slantchev, Branislav L. 2017. "On the Proper Use of Game-Theoretic Models in Conflict Studies." Peace Economics, Peace Science and Public Policy 23(4): 1–14.

Slantchev, Branislav L. 2020a. Analytic Theory II (POLI 203B), course syllabus.

Slantchev, Branislav L. 2020b. "The Simple, the Trivial, and the Insightful: Field Dispatches from a Formal Theorist." In The SAGE Handbook of Research Methods in Political Science and International Relations, ed. Luigi Curini and Robert Franzese. London: SAGE.

Slantchev, Branislav L., and Ahmer Tarar. 2011. "Mutual Optimism as a Rationalist Explanation of War." American Journal of Political Science 55: 135–148.

Sword, Helen. 2012. Stylish Academic Writing. Cambridge, MA: Harvard University Press.

Thomas, Francis-Noël, and Mark Turner. 2011. Clear and Simple as the Truth: Writing Classic Prose. 2nd ed. Princeton: Princeton University Press.

Thomson, William. 2001. A Guide for the Young Economist: Writing and Speaking Effectively about Economics. Cambridge, MA: MIT Press.