u/Worried-Situation-35

A lot of people read RC like the goal is to understand every sentence perfectly the first time.

I don’t think that’s the right goal.

The first read should give you a usable map of the passage. You want to know what the passage is doing, not memorize every detail.

When I read RC, I’m mainly trying to track four things

What is the main issue or topic?
What viewpoints are being introduced?
What does the author seem to think?
What is each paragraph doing?

That last one matters a lot. After each paragraph, I want a short mental label. Something like

introduces the old theory
gives evidence against it
explains the new theory
author qualifies the debate
example of the broader point

That is way more useful than highlighting a bunch of random details.

For natural science passages especially, I would not get stuck trying to master every technical term. A weird term is usually only important because of the role it plays. Is it evidence? An example? A theory? A contrast? A mechanism? A criticism?

That question keeps you from getting buried in the details.

My basic approach would be

Paragraph 1 figure out the topic and setup.
Paragraph 2 ask what changed, what view was added, or what evidence was introduced.
Paragraph 3 look for contrast, development, or the author’s position.
Final paragraph ask where the author leaves the debate or what the passage ultimately wants you to understand.

By the end, I want to be able to say:

“This passage is mainly about ___, the author thinks ___, and the paragraphs move from ___ to ___ to ___.”

If you can do that, the questions become much less chaotic because you know where to go back and what kind of answer should be supported.

A lot of RC timing improvement starts here. Not by reading faster immediately, but by reading with a clearer purpose.

Happy to answer RC questions in the comments. I also tutor privately if anyone wants more direct help with this.

A lot of RC review is too shallow. People finish a passage, miss a few questions, check the right answers, and move on. The problem is that this usually tells you what was right, but not why you missed it. When I review RC, I want to figure out whether the problem started in the passage read itself or in the question/answer choice stage.

The first thing I’d ask is
- Did I actually have the main point right?
- Did I know the author’s attitude?
- Did I understand what each paragraph was doing?
- Was there a viewpoint shift or contrast I didn’t catch?

If those were blurry, then the issue probably started before I even got to the questions.

Then for each missed question, I’d ask
- What was this question really testing?
- What part of the passage should have controlled the answer?
- Why did my answer feel attractive in the moment?
- Was my choice too broad, too extreme, or only partially supported?
- Did I misread the passage, or did I mis-handle the answer choices?

That part matters a lot, because not every RC miss is the same. Sometimes the issue is passage structure. Sometimes it’s a bad elimination. Sometimes it’s bringing in an assumption that the passage never actually gave you. The goal of review is not just to say “oh okay, that was the right answer.” The goal is to identify the failure point clearly enough that you can catch it earlier next time. A lot of RC improvement happens when review stops being “read explanation, move on” and starts becoming “where exactly did my read or decision break down?”

If people want, I can also make one on how I’d approach RC in real time during the first read.

A lot of RC frustration comes from reading the passage like a pile of information instead of a structure.

When people finish a passage and think “what did I just read,” it usually means they were trying to understand every sentence equally instead of tracking what each paragraph was doing.

What helped me most was slowing down and asking after each paragraph:
- why is this paragraph here?
- is it introducing a view, pushing back on one, giving evidence, or showing me what the author thinks?
- how does it move the passage forward?

That changes RC a lot, because now you are not just reading words — you are building a map.

For me, the main things I want after reading are:
- the main point
- the author’s attitude
- the role of each paragraph

If those are blurry, the questions feel much harder and much slower.

I think a lot of people try to fix RC by rushing passages over and over, but usually the better move is to get clearer on structure first. Once the structure gets clearer, timing starts to feel less chaotic too.

If people want, I can also make a post on how I’d review a missed RC question set after a passage.

One of the most common patterns I see is that students think they are reviewing, but they are really just rereading the question and accepting the explanation after the fact.
That usually sounds like this:

“I see why B is right now.”
“I was between B and D.”
“I just misread it.”
“I need to slow down.”

The problem is that none of those actually identifies what went wrong in your reasoning.
A lot of score plateaus happen because students do not isolate the exact failure point. On LR especially, you need to be able to say what happened with precision. Did you miss the main conclusion? Did you confuse a premise with a sub-conclusion? Did you bring in an assumption that was never stated? Did the wrong answer feel attractive because it was too broad, reversed the relationship, or only matched part of the argument?

If your review is too vague, your mistakes stay vague. And vague mistakes repeat.
A better review process is to ask:
What was the argument actually doing?
What did I think the right answer had to do?
Why did my chosen answer feel tempting in the moment?
What specifically makes it wrong?
What would I need to notice next time to avoid missing this again?

That kind of review is where improvement starts. Not just knowing the credited answer, but understanding why your reasoning allowed the trap answer to survive.
A lot of students are not stuck because they are incapable of scoring higher. They are stuck because their review process is not detailed enough to produce change.

If you want, I can make another post on how I would review RC the same way.