How to Annotate MCAT CARS Passages (Without Wasting Time)
MCAT CARS annotation is not about underlining everything — it's about marking the moves an author makes. Learn a lightweight system for noting structure, tone, and argument shifts that speeds up question answering.
2026-06-07 · 9 min read
Why most students annotate wrong
The most common CARS annotation mistake is highlighting too much. Students underline the first sentence of each paragraph, then a sentence that sounds important, then a claim that seems relevant — and end up with three-quarters of the passage marked. This helps nothing. When everything is highlighted, nothing stands out.
The second mistake is annotating for recall. Students write margin notes like "author likes X" or "this paragraph is about Y" as if they're taking notes for a class. On CARS you are not trying to memorize the passage — you're trying to navigate it. Your notes should serve navigation, not comprehension.
Effective annotation is sparse and structural. It marks where the author changes direction, not what the author is saying in full.
What to annotate: the four things worth marking
1. Argument pivots. Mark the word or phrase where the author shifts — from setup to claim, from one position to a counterargument, from evidence to conclusion. Common pivot signals: "however," "yet," "but," "although," "nonetheless," "in contrast," "despite this." A small arrow or a bracket at the pivot is enough.
2. The main claim (if it's explicit). Some CARS authors state their central thesis directly, usually at the end of the first paragraph or the beginning of the last. A star or "MC" in the margin is useful. If the thesis is implied rather than stated, don't mark it — you'll construct it from the passage's arc.
3. Author tone shifts. If the author moves from neutral description to open criticism or from skepticism to endorsement, note it briefly: "+," "–," "?," or "neutral" in the margin. A shift in tone is one of the most tested elements across comprehension and reasoning-beyond-the-text questions.
4. Paragraph function labels. A one-word label per paragraph tells you what that paragraph does, not what it says. Examples: "background," "problem," "counterarg," "evidence," "conclusion," "example," "complication." These labels are your map when a question says "the author mentions X in order to..."
What not to annotate
Specific details, statistics, or examples. You do not need to remember these. CARS questions that ask about specific details tell you where to look — you return to the passage to verify. Annotating every detail is time wasted on items you will re-read anyway.
Passages are available to return to during CARS. This is not a memory test. Your annotations should help you find things quickly, not reproduce what's already on screen.
Definitions and descriptions. If the author spends a paragraph explaining what a term means, you don't need to annotate it — you just need to know the paragraph is a definition paragraph. Your function label covers this.
A practical passage walkthrough
Here's how this looks in practice. Imagine a 600-word CARS passage structured roughly as:
Paragraph 1: Background on a historical debate in philosophy of mind.
Paragraph 2: The traditional view and its main proponents.
Paragraph 3: A challenge to the traditional view. Opens with "However..."
Paragraph 4: The author's assessment of the challenge — with a specific qualifier.
Paragraph 5: Implications and a call for further research.
Annotations: P1 → "background"; P2 → "trad. view"; P3 → mark "However" with an arrow, label "challenge"; P4 → mark where the author qualifies their view (e.g., "to some extent"), note tone as "+/–"; P5 → "implications / conclusion."
Total annotation time: 90 seconds. What you gain: a map of the argument's structure. When a question asks "the author's attitude toward the traditional view is best described as..." — you know to check P4 and re-read the qualifier.
Annotation on the digital MCAT interface
The MCAT is administered digitally. You can highlight text using the interface, but you cannot write in margins. Compensate by using the digital highlighting tool strictly for your four annotation targets — pivots, main claim, tone shifts — and keeping a brief scratch paper note for paragraph function labels (P1: background, P2: trad. view, etc.).
Keep scratch paper notes in abbreviations, not sentences. "P3: challenge / however" takes two seconds to write and gives you the same navigational value as a lengthy note.
Practice your annotation system under timed conditions before test day. A system you've never used under pressure is not a system — it's a plan. The test is not the place to experiment.
How annotation connects to question strategy
Your annotations change how quickly you answer different question types. For main idea questions, check your "MC" annotation and your paragraph function labels — the answer should match the arc from background to conclusion. For reasoning questions (what does the author assume, what would weaken the argument), use your pivot annotations to locate where the argument makes its key moves. For application questions (apply the author's view to a new case), return to your tone and claim annotations to understand where the author's commitments are strongest.
Verbloom's CARS practice gives passage-level feedback — you can see after each question which part of the passage the correct answer referenced, helping you evaluate whether your annotations captured the right structure.
Frequently asked questions
Should I read the questions before the passage to know what to annotate?
This is a legitimate strategy but not universally effective for CARS. CARS questions rarely point to specific facts that you could efficiently hunt for mid-read. Most test-takers find passage-first reading more effective for CARS — read with structure in mind, then answer questions using your annotations and targeted re-reads.
How long should annotating take?
For a standard CARS passage (500–600 words), annotation woven into your first read should add no more than 60–90 seconds beyond reading alone. If annotation is taking 3+ minutes, you're over-annotating.
Does everyone need to annotate?
No. Some high scorers annotate minimally or not at all and rely on a strong first read with excellent retention. Try the annotation approach described here for 10–15 practice passages and assess whether your accuracy and pacing improve. Use what works for you under test conditions.
What about passages with dense technical language?
Don't slow down to parse every term on first read. Annotate the structure (what the paragraph is doing) and return to technical language only if a question specifically requires it. CARS does not require specialized knowledge — it only requires understanding what the author argues.
Related Verbloom guides
Sources
Want CARS reading to feel methodical?
Verbloom drills the argument-first reading that CARS rewards — main idea, author attitude, structure, and supported inference — in short, focused sessions.
Try Verbloom