Passage Mapping for

Core Review

What Passage Mapping Is (and Is Not)

Passage mapping is the practice of creating a brief, structured index of a passage's paragraphs as you read. A map entry for each paragraph contains:

1. Topic: What is this paragraph about? (A few words — the subject.)
2. Purpose: What job does this paragraph do in the passage? (A verb or short phrase.)
3. Label: A 1–3 word shorthand you can scan later. (P1-Background, P2-Experiment, P3-Criticism, etc.)

What passage mapping is NOT:

• It is NOT note-taking. You are not summarizing content or recording facts.
• It is NOT an outline in the traditional sense (no hierarchical bullet points).
• It is NOT time-consuming. Aim for 10–15 seconds per paragraph after reading — 5–10 words total per entry.

The purpose of the map is navigational. When question 7 asks "According to the passage, what was the sample size of the 2019 study?", you don't re-read the whole passage — you glance at your map, see that "P4: 2019 Study/Methods," and scan directly to paragraph 4.

The Three Elements of a Map Entry

1. Topic

Identify what the paragraph is about — the subject matter. This is usually found in the first sentence (topic sentence), though occasionally a paragraph builds to its topic.

Examples: "Darwin's finches," "Hawthorne effect," "Gram staining procedure," "Limitations of fMRI."

2. Purpose

Identify what the paragraph does in the passage's overall argument. Use verbs:

• Introduces — presents a new concept, theory, or problem
• Defines — explains what a term means
• Describes — provides factual information without argument
• Illustrates — gives an example or case study
• Supports — provides evidence for a claim
• Contrasts — presents an opposing view or difference
• Refutes — argues against a position
• Qualifies — adds nuance or limitations to an earlier statement
• Concludes — wraps up, synthesizes, or makes a recommendation
• Transitions — bridges between two major sections
• Elaborates — provides additional detail on a previously introduced topic

The purpose is the most important element. It tells you not just where something is, but how the passage uses that information. This is critical for organization and purpose questions.

3. Label

A compact, scannable 1–3 word tag. The label serves as your visual anchor — when scanning your map, your eye should catch it instantly.

Examples: P1-Intro, P2-Mechanism, P3-Evidence, P4-Counterargument, P5-Resolution.

Use consistent labeling language across passages so your brain can parse maps instantly. A recommended system:

• P#-Background/Context — opening paragraph that sets the stage
• P#-Claim/Thesis — where the author states the central argument
• P#-Evidence/Example — supporting data, studies, or illustrations
• P#-Mechanism/Process — explaining how something works
• P#-Counterargument — presenting opposing views
• P#-Rebuttal/Response — answering the counterargument
• P#-Implication — "so what" paragraph (significance, consequences)
• P#-Conclusion — final synthesis or recommendation

How to Build a Passage Map

Step 1: Read the first paragraph thoroughly. This paragraph usually contains the passage's topic, scope, and often the thesis. Your map entry for P1 should capture the subject and the author's starting position.

Step 2: For each subsequent paragraph, read the topic sentence (first sentence) carefully, then read the rest of the paragraph with reduced intensity. Your goal is to understand what the paragraph contributes to the passage, not to memorize details. You can return for details later when a question demands them.

Step 3: Immediately after finishing each paragraph, write your 3-element entry. Do NOT wait until the end of the passage — you'll forget the purpose of paragraph 2 by the time you reach paragraph 5.

Step 4: After the final paragraph, spend 10 seconds reviewing your map as a whole. Ask: what is the through-line? How does the passage build? This review solidifies the passage architecture in your mind and pre-answers organization questions.

Example Passage Map

Passage topic: The evolution of antibiotic resistance in bacteria.

Total mapping time: approximately 90 seconds. Result: a complete navigation index.

With this map:

• A detail question about "horizontal gene transfer" → scan P3.
• A purpose question about "the function of paragraph 4" → answer: "provides empirical evidence supporting the severity of the problem."
• A main idea question → the passage presents a problem, explains its mechanisms, provides evidence, identifies a contributing factor, and proposes solutions.
• An organization question → "A problem is introduced, its mechanisms are explained, evidence is presented, contributing factors are discussed, and solutions are proposed."

Adapting Passage Maps to Passage Type

Scientific/Technical Passages (common on DAT): These passages often follow predictable patterns: introduction of a phenomenon → mechanism/explanation → evidence/studies → implications or remaining questions. Your map will highlight this structure. Pay special attention to paragraphs describing experiments — label them with the study name or year for quick reference.

Argumentative Passages: These present a thesis, supporting arguments, counterarguments, and rebuttals. Your map must clearly distinguish the author's position from positions the author is reporting. Crucially: when the author presents an opposing view, note whether the author endorses or rebuts it. A common DAT trap asks about "the author's view" when the passage neutrally presents a view the author does not hold.

Narrative/Historical Passages: These follow chronological or thematic sequences. Your map may use time markers: P1-Origins, P2-Development, P3-Modern Era. Or thematic: P1-Political, P2-Economic, P3-Cultural.

Common Mapping Mistakes

Mistake 1: Writing too much. If your map entries are full sentences, you're summarizing, not mapping. The map is a skeleton, not a clone. Every extra word costs time and adds visual clutter.

Mistake 2: Recording content instead of purpose. "P3: In 2019, WHO reported that 700,000 people die annually from resistant infections" is a content note. "P3: Evidence (WHO data)" is a map entry. The former tells you what was said; the latter tells you where to find it and why it's there.

Mistake 3: Failing to label shifts. When a paragraph contains a "however," "but," or "in contrast," the purpose may shift mid-paragraph. If the shift is significant, note it: "P4: Describes early optimism, then qualifies with limitations." Better yet, treat the shift as a sub-entry or split it if the paragraph is long.

Mistake 4: Spending more time mapping than reading. If you're spending 3+ minutes on a map, you're over-investing. The map exists to save time across 16–17 questions; it should cost 60–120 seconds to build.

Common Traps

• Turning the map into an outline. Students who are comfortable with academic outlining tend to produce hierarchical, detailed maps. This is counterproductive — the DAT rewards speed and navigation, not comprehensive documentation.
• Assuming all paragraphs have one clear purpose. Some paragraphs serve multiple functions (e.g., both describing and evaluating). Note the primary function; the secondary function will be apparent when you re-read the paragraph for a question.
• Skipping the map review at the end. The 10-second map review is where main idea and organization questions are pre-answered. Don't skip it.