Two problems with the suggested timing distributions for RC. I've attached two screenshots to illustrate this

1) Suggested timing inconsistency: If you total up the suggested time for each of my questions individually, I'd be at around -0:06, but the overall recommended pace in the second screenshot says I'm actually -00:51. Which one is the real suggested time?

2) Way too little time recommended for the passage: If i had a dollar for every time somebody told me to slow down on the passage and focus on retention, I'd actually be able to afford law school. Point is, the consensus seems to be that the best strategy is around 3-4 minutes (minimum) on the passage, and try to blitz through the questions. But as you can see here, having spent 3:44 on the passage I'm being told I spent almost 2 whole minutes more than I'm supposed to have used. Granted this is a 4 star passage and I was pretty slow overall, but still, this was not a passage I could've gotten through in just 2 minutes and expect to retain any info.

Maybe there's some setting I'm unaware of which lets me tweak the suggested timing based on my strategy, and if so please let me know. Otherwise I’d really appreciate any clarification on how these suggested timings are calculated.

1

1 comments

  • Sanique Rowe Student Services
    Tuesday, Nov 18

    Hi there,

    Thanks again for your thoughtful message! I took a close look at your screenshots and wanted to clarify both of your points:

    1) Suggested timing inconsistency: You're right to notice what seems like a discrepancy between the individual question timings and the total timing summary.

    From what I can see:

    • You spent 3:44 on the passage, which is listed as 1:45 over, meaning the target for the passage is 1:59.

    • You also spent 3:44 on the questions, and it says you're 0:51 under, which means the target for the questions is 4:35.

    When you add those target times together (1:59 + 4:35), you get 6:34, but the system lists your total target time as 6:38.

    This 4-second difference likely comes from backend rounding. The system calculates timing in seconds, but the times you see are displayed as rounded minute: second values. So even though it looks like the numbers don’t add up, it’s likely due to minor rounding at each step. Hope that clears it up a bit!

    2) Too little time recommended for the passage: The "target time" is based on timing data from top-scoring students. It’s not a hard rule, but rather a helpful benchmark. It gives you a sense of how long a high scorer might have taken on each part. That said, different strategies work for different people! If you’ve found that spending a bit more time on the passage helps your retention and leads to better accuracy, that’s totally valid.

    I hope this helps! Please let me know if you have any further questions or concerns.

    1

Confirm action

Are you sure?