How to Read a Research Paper: The Three-Pass Method, Explained

Most people read a research paper the way they read a novel: first page to last, in order, hoping understanding arrives somewhere along the way. It usually does not. Papers are not written to be read linearly. They are reference documents with a predictable structure, and once you know that structure you can decide in ten minutes whether a paper deserves an afternoon.

This guide walks through the approach we use on the POMODIARY team, built on the widely taught three-pass method described by computer scientist S. Keshav in his short note "How to Read a Paper". We add practical checklists for each section, a note template you can copy, and some honest advice about where AI reading assistants help and where they do not.

Why linear reading fails

A typical paper front-loads motivation and back-loads the details you actually need to judge it. If you start at the introduction and push through every equation, you spend the most effort on the part you are least equipped to evaluate, before you even know whether the result matters to you. The three-pass method flips this: invest a little, decide, then invest more only if the paper earns it.

The three passes at a glance

Pass	Time	Goal	You can answer
First	5 to 10 minutes	Get the shape	What kind of paper is this, and is it relevant?
Second	Up to an hour	Grasp the content	What did they do, what did they find, and how strong is the evidence?
Third	Several hours	Understand deeply	Could I reproduce this, and where are its weak points?

Most papers you encounter should stop after the first pass. That is not laziness; it is triage.

Pass one: the bird's-eye view

Read only these parts, in this order:

Title and abstract. What problem, what approach, what headline result.
Introduction. Skim it, paying attention to the final paragraph, which often lists the contributions.
Section and subsection headings. These are the paper's skeleton.
Figures and tables. Look at them and read their captions. Do not study them yet.
Conclusion. Compare what they claim at the end with what they promised at the start.
References. Glance for papers you already know. This tells you which conversation the paper belongs to.

At the end of the first pass, you should be able to answer five questions, which Keshav calls the five Cs:

Category: Is this a new method, a measurement study, a survey, a replication, a theory paper?
Context: Which earlier work does it build on or argue against?
Correctness: Do the assumptions look reasonable at a glance?
Contributions: What, concretely, is new?
Clarity: Is it well written enough to be worth the effort?

If you cannot answer these, either the paper is badly written or it is outside your current background. Both are useful to know.

What to look for in the abstract

An abstract is an advertisement, so read it skeptically. Underline four things: the problem, the method, the main quantitative result, and the comparison point. "Our method improves accuracy" means little until you know improved compared to what, on which data, and by how much. If the abstract gives no numbers at all, note that as a question to answer in pass two.

Pass two: the content

Now read the whole paper with care, but skip proofs and dense derivations. Your aim is to be able to explain the main argument and its evidence to a colleague.

Reading figures properly

Figures are where many papers make or break their case. For each important figure:

Read the axis labels and units before the curves. Is the y-axis truncated so a small difference looks large?
Check whether error bars or confidence intervals are shown, and what they represent (standard deviation, standard error, a 95 percent interval).
Count the comparison conditions. Is the obvious baseline missing?
Match the figure to the sentence in the text that cites it. Does the text claim more than the figure shows?

Reading the methods

The methods section answers the question that matters most: could this result be an artifact of how it was produced? Check:

Data or sample: Where did it come from, how big is it, and how was it selected? Small or convenience samples limit how far a result generalizes.
Comparison: What is the control or baseline, and was it given a fair chance (for example, equally tuned)?
Measurement: How was the outcome measured, and is that a good proxy for what they actually care about?
Analysis: Were the analysis choices decided in advance, or could they have been adjusted after seeing the data?
Availability: Are code, data or materials shared? This affects how much you can verify yourself.

Mark anything you do not understand rather than stopping. Unfamiliar terms and references go on a list to look up later. If after this pass you still cannot follow the argument, that is a signal to read background material first, not to force your way through.

Pass three: virtual re-implementation

The third pass is for papers central to your own work: something you will build on, review, teach, or cite as key evidence. The idea is to mentally recreate the work. Make the same assumptions the authors made and ask how you would have done it. Where your version differs from theirs, you will find either a clever idea you missed or a hidden assumption they did not justify.

During this pass, work through the derivations, check that numbers in tables are consistent with each other and with the text, and write down the strongest objection you can think of. A good test: could you present this paper in a journal club and handle hostile questions?

A note template you can reuse

Notes are what make reading cumulative. We suggest one short note per paper, in a consistent format:

Citation: authors, year, title, venue, link or DOI
One-sentence summary: in your own words
Problem: what gap the paper addresses
Method: the approach in two or three lines
Key result: with the actual number and its comparison point
Evidence quality: sample size, baselines, limitations the authors admit, limitations they do not
Relevance to me: how this connects to my project or question
Open questions: what I still do not understand or doubt
Pass reached: one, two or three

The "pass reached" field matters. Six months later it tells you whether you actually understood a paper or only skimmed it, which changes how much you should rely on your own summary.

Common mistakes

Citing after pass one. An abstract-level reading is not enough to cite a paper as support for a specific claim.
Taking figures at face value. Truncated axes, missing error bars and cherry-picked examples are common.
Ignoring the limitations section. Authors often state the most important caveats themselves, briefly, near the end.
Reading alone, forever. Discussing a paper with one other person exposes misunderstandings fast.
Never stopping. Not every paper deserves a third pass. Deciding to stop is a skill.

Where an AI reading assistant fits

AI tools are genuinely useful in this process when they support the passes rather than replace them. They are good at helping you during the first pass (getting the gist of an unfamiliar subfield), explaining a term or a dense paragraph during the second pass, and translating passages if you read in a second language. They are poor substitutes for checking figures, judging methods, or deciding whether a claim is actually supported. They can also state things confidently that are not in the paper.

A sensible workflow is to use a daily feed for discovery, then read the original for anything that matters. Our own tool, ChatPaper.AI, publishes five plain-language paper summaries a day, which works well as a first-pass filter across fields. When a paper is worth a closer look, its workspace lets you ask questions about specific passages, but the rule stays the same: before a number or claim goes into your notes or your writing, find it in the PDF yourself. We cover that discipline in more depth in our guide to using AI to summarize papers responsibly.

A simple weekly routine

If you want to keep up with a field without drowning, try this:

Each weekday, spend ten minutes doing first passes on a few new papers.
Choose one or two per week for a second pass and write a full note.
Once a month, pick the single most important paper for a third pass, ideally with a colleague.

That rhythm adds up to dozens of well-understood papers a year, which is more than most people manage by reading everything start to finish.