It could also be the length of the post—really long posts trigger the spam filter apparently. FYI!
Part 3 of this older series on time management has been updated for the timing for the new exam:
https://www.manhattanprep.com/gmat/blog ... rt-1-of-3/I recommend bailing fast (within 30 seconds) on ~4-5 questions in your weaker section and up to ~4 in your stronger section. Note that this is "bail without engaging very much / trying to solve." You'll
also have to guess on other questions that you try but you just can't figure out for whatever reason. But those don't count against your "bail fast" quota. (And there's no limit on these. If you don't know how to do something, you don't know how to do it. Continuing to spend more time on it won't help.)
Re: your comment about never bailing in less than 30 seconds, I do think you can still do this on something that you know is terrible for you. I hate cylinders, for example, and won't do those at all. I don't even check whether it's an easier one.
For others, though, I'll take a little longer to decide because I'm reading it and realizing that it just contains too many annoying things. (I saw one the other day that was a Roman Numeral with absolute value, fractions, and three variables. And it talked about something with consecutive integers and something else now, I forget—and I was like Nope! Too many annoying things!)
People often find it harder to know when to bail fast on Verbal. It's hard to bail fast on SC, because it takes time to read the sentence...and SC is the shortest of the three types anyway. So I might bail on a hard SC, but I'm probably not truly bailing
fast and saving a lot of time. But if I read an SC and the sentence is so weird that I can't even understand it, that's a pretty good bail opportunity.
On CR, I decide based on one of two things: (1) The question type (which is the first thing to figure out when you start the problem) and (2) The argument itself.
Some people, for example, really dislike Evaluate or Boldface questions, so you could just decide to bail any time you see one of those. Sometimes the argument itself is too weird to understand (though, again, the time it takes to figure out that you don't understand it might mean that you aren't bailing
fast.
For RC, again it might be based on the question type (Except questions are especially annoying). It could also be based on the passage. Let's say that I thought the second half of paragraph 2 was really hard to understand. Okay, I'll guess if I get a question about that part. Chances are I'll only get one (and I might not even get any!).
For review / knowing that you're learning. You said that you did a general Geo review and that worked. I will guess that you feel comfortable doing the same for anything that's about "facts" (math, SC / grammar stuff). But CR and RC aren't about facts, they're about process and reasoning.
You can still do a general review there though. For example, can you articulate what kind of reasoning you want to be doing for each CR question type? For each one, can you say
(1) How to identify that type,
(2) The kinds of things you can expect to see in the arguments of that type (will it have a conclusion or not? will it have counterpoints / counterpremises? etc),
(3) What your goal is for that type (eg, for Find the Assumption, I need to find something that the author must believe to be true in order to make that particular argument), and
(4) What kinds of characteristics the correct answer should have and what kinds of traps they tend to set for that specific type (eg, for Find the Assumption, the correct answer is necessary for the argument to be valid; if you said that this answer was not true, you'd kill the argument; tempting traps include: something that might strengthen the argument but it's not necessary to the argument / doesn't have to be true; something that makes a false distinction (eg, the answer makes a distinction between older and younger women but the argument was talking about all women); an "opposite" trap—this thing is something the author most assume to be false in making the argument.
And that process review is something you can also do for Q and SC. What are the steps for Testing Cases on a DS problem? What are the variations? For example, you can test characteristics (like odd and even) instead of testing actual values.
On SC, what kinds of things can the First Glance tell you? Go look at 15 OGs right now. Don't read the original sentence and don't do the whole problem—instead, literally just take 15 seconds to look at the very first difference in the answer choices and try to articulate
one thing that that problem
could be testing, just based on that one set of differences.
I thought that the detail of your plan was good, yes. But maybe you aren't taking those things to the last step, which is "What are my takeaways? What did I just learn that I want to remember and use on the real test? How* am I going to remember that so that I can recall and use it on the test? And what did I just discover that I need to change in some way before I get to the real test?"
*This is the "Know the Code" pattern: You want to be able to get to the point where you can say "When I see ABC, I'm going to XYZ."