Stop Highlighting Everything: Build a Claim–Evidence–Question Map for Dense Reading

You finish a difficult chapter with half the page glowing yellow, then open your notes and realize you still cannot explain the author’s point. The problem is not that you failed to pay attention. Highlighting captures passages, but it does not automatically preserve the job each passage does.

A claim–evidence–question map gives every important note a role. Instead of collecting sentences, you record what the author is saying, what they use to support it, and what remains uncertain. The result is a small set of notes you can actually use in a seminar, a report, a meeting, or an exam answer.

This method works especially well for dense articles, textbook chapters, policy documents, research summaries, and work proposals: material that contains reasoning, not just facts to memorize.

Why a page of highlights is hard to use later

A highlight usually answers only one question: “Was this sentence noticeable?” That is useful while reading, but later you need different answers: What is the central conclusion? Which examples are merely illustrations? What information would challenge the conclusion? Where did you stop understanding?

Without those distinctions, a powerful statistic, a definition, a limitation, and a minor example all look equally important. Rereading becomes your only way back into the material.

A three-part map fixes this by separating the architecture of an argument:

• Claim: the point the author wants the reader to accept.
• Evidence: the reasons, observations, data, examples, or cited sources offered in support.
• Question: an uncertainty, limitation, missing link, unfamiliar term, or possible alternative explanation.

The useful note is not the one that preserves the most words. It is the one that lets you reconstruct the author’s reasoning without reopening every page.

Set up the map before you read

Use a notebook page, a document, or three columns in a spreadsheet. Put the source title and the purpose of your reading at the top. “Prepare for Tuesday’s discussion” produces different notes from “find support for a recommendation.” Naming the purpose prevents you from treating every paragraph as equally valuable.

Then make one row for each substantial section, not each paragraph. A ten-page article may need only four to eight rows. Leave room for a page number, heading, or short location marker so you can find a passage again.

The wording in this example is deliberately plain. Your map is a working tool, not a miniature version of the source. If you cannot state a claim in your own words yet, write a question instead of copying a polished sentence.

Read in passes, not as one continuous highlighting session

First pass: find the author’s route

Read the title, introduction, headings, conclusion, charts or figures, and first and last sentences of major sections. Do not try to make perfect notes. Your goal is to predict the route: problem, main conclusion, supporting reasons, and implications.

Write a provisional one-sentence answer to: “By the end, what does this author appear to want me to believe or do?” Mark it as provisional. Dense writing often becomes easier once you know the destination.

Second pass: capture the load-bearing claims

Now read closely. For each section, ask, “If this section vanished, what part of the overall argument would become weaker?” The answer is often its claim.

Write claims as complete, modest statements. Avoid labels such as “important point” or “benefits.” Those labels do not tell future-you what the point was.

• Weak note: Training
• Better claim note: The proposal treats short practice cycles as more useful than a single long orientation.

A claim may be a definition, a causal explanation, a recommendation, or an interpretation. Do not assume every confident sentence is a proven fact; some are the author’s judgment or framing. Recording that distinction makes your later writing more accurate.

Third pass: attach only the evidence that does real work

Under each claim, note the support that most directly carries it. This might be a study result described by the author, a comparison, a process explanation, a case example, or a quotation from another source. Keep the evidence linked to the claim it supports.

Use verbs that reveal the type of support: defines, compares, reports, illustrates, assumes, cites, calculates, describes. A note such as “reports survey responses” is more informative than “survey.” It helps you avoid treating an illustration as proof or a source’s opinion as a settled conclusion.

You rarely need every detail. Preserve an exact figure, name, or phrase only when it matters for your assignment or when changing it would distort the point. Otherwise, a brief paraphrase plus a location marker is easier to review.

Make questions do useful work

The question column is not a record of failure. It is how you keep confusion from becoming vague and how you notice limits in a convincing argument.

Useful questions tend to fall into four groups:

• Meaning: “What does the author mean by ‘informal learning’ here?”
• Connection: “How does this example establish the broader conclusion?”
• Boundary: “Would this reasoning apply to a small team as well as a large organization?”
• Alternative: “Could the reported outcome be explained by experience level rather than the new process?”

Write questions precisely enough that you can answer them. “Confusing” is a feeling; “Which step links the observation to the recommendation?” tells you what to investigate.

Not every question needs a solution before you move on. Mark each one mentally as one of three kinds: look it up, raise it in discussion, or keep it as a limitation. That prevents a single unfamiliar term from turning into a twenty-minute detour.

Use a worked mini-example

Imagine you are reading a report that recommends replacing a long project kickoff meeting with a short written brief followed by focused check-ins.

Your map might contain this:

• Claim: A written brief makes early project decisions easier to revisit than a discussion-only kickoff.
• Evidence: The report describes how meeting participants remembered different versions of the decision and shows the brief as a shared reference point.
• Question: Who owns updating the brief when the scope changes?

Notice what the map does not say: “Briefs are good.” It captures the proposed mechanism—an accessible record resolves conflicting recollections—and identifies a practical condition the report may not have addressed. That is enough to contribute something specific in a meeting or evaluate whether the recommendation fits your situation.

Turn the map into something you can use

When the reading is complete, spend five minutes making a short synthesis beneath the map. Do this before closing the source.

1. Write the source’s central claim in one or two sentences.
2. List the two or three strongest pieces of support, not every example.
3. Name one limitation, open question, or condition that affects how broadly the conclusion applies.
4. Write one sentence beginning, “This matters because…” and connect it to your assignment, project, or discussion topic.

This final step is where notes become usable knowledge. For an essay, it can become the seed of a paragraph plan. For a class, it gives you a comment more substantial than “I agree.” At work, it helps you summarize a document without confusing its recommendations with your own.

Adjust the method to the kind of reading

For a textbook chapter

Claims often appear as concepts or relationships rather than disputed arguments. Put key definitions in the claim column, then use evidence for the process, example, diagram, or explanation that shows how the concept works. Questions can identify terms that need a separate flashcard or practice problem.

For an academic article

Keep the author’s research question, method, findings, and interpretation distinct. A finding is not automatically the same as the author’s broad conclusion. If a section describes a method, note what it can show and what it cannot show rather than trying to squeeze it into “proof.”

For a work document or proposal

Pay particular attention to assumptions and implementation details. A recommendation may sound sensible while depending on capacity, access, approval, or ownership that is not stated. Your questions can become a constructive agenda for the next conversation.

Common ways the map goes wrong

Writing too much. If your evidence cells contain full paragraphs, the map has become transcription. Limit yourself to the smallest note that preserves the reasoning. You can always mark a passage to revisit.

Calling every statement a claim. Background information and examples matter, but they usually support a larger point. Look for the statement that gives them purpose.

Turning questions into attacks. A question need not prove the author wrong. “What conditions are required?” is often more productive than “This is flawed.”

Forgetting locations. A page number, section heading, or slide title saves time and protects you from misremembering where a detail came from. This is particularly important when you will quote or cite later.

Mixing your response with the source. Label your own application clearly: “My implication” or “Possible use.” That keeps a later draft honest about what the source actually said.

Keep the map light enough to repeat

The point is not to make reading slow. On a short article, you may make only three rows. On a long chapter, map only the sections relevant to your purpose. If you need to prepare for an exam, create the map while learning, then cover the evidence and question columns and try to reconstruct them from the claims.

For collaborative work, share a cleaned-up version containing the central claim, strongest support, and unresolved questions. It is often more helpful than forwarding a document with scattered comments because teammates can see what needs a decision.

Your next action is small: choose the next substantial thing you need to read and draw three headings—Claim, Evidence, Question—before you begin. After the first section, pause long enough to complete one row. That pause is where passive highlighting becomes understanding.