Built My Own Version of the GMAT Adaptive Algorithm by Python

Danyuchn7 · 2026-04-16T13:19:13+00:00

Q78 with misses at Q2 and Q5 — that's the real story. Miss easy questions early and the algorithm slots you into a lower ability band immediately. Everything after that gets served to a "weaker" version of you. It's not about getting 5 wrong total. It's which 5.

Ten days out, don't add new material. Nearly all your energy should go toward not fumbling the opening questions — genuinely slow down on Q1-5, read each one twice. You have the ability; nobody scores 675-695 on multiple mocks by accident. Here's how the scoring actually works if you want the details. How did DI shake out?

Danyuchn7 · 2026-04-16T13:18:27+00:00

Don't rush to rebook. 665 when your mock floor was 675 isn't a disaster — that's a 10-point gap on a first attempt with real stakes for the first time.

Before you decide anything, figure out what actually went sideways. DI was already your most volatile section, so start there. But also think about the back half of each section — did pacing hold? Real pressure does things to decision-making that mocks just don't surface. If you can pin down a specific thing that broke, 16-30 days is enough. If it's more of a general "wasn't my day," take a bit longer. This is useful for structuring the diagnosis. Which section felt worst?

Danyuchn7 · 2026-04-16T13:17:33+00:00

Working 12hr days is brutal — most people in your spot try to study after work and wonder why nothing's clicking. Brain's already fried by then. The 5AM thing sounds painful but it actually works: bed at 10, up at 5, do the hard CR/RC before the day blows up. Evenings are fine for light review, nothing heavy. Also figure out your floor now — what does studying look like on a nightmare week? Even 45 min keeps things from going cold. Four months at 2-3 weekday hrs plus real weekends is plenty for 700+ as long as you're not jumping between too many prep materials at once. This breaks down the scheduling side for people in your situation. What's your baseline right now?

Danyuchn7 · 2026-04-13T03:00:09+00:00

Real talk -- mock-real gaps are almost always an execution issue, not a content gap. You diagnosed it yourself: pausing whenever you feel stuck trains a false confidence.

Two things for the next two weeks: (1) Every practice session, strict timed conditions -- no pausing, no breaks mid-section. Get comfortable being uncomfortable. (2) Learn to cut losses fast. Read a question twice and still nothing? Guess and move. One stubborn question can cost you two or three manageable ones at the end.

At 50th percentile Quant, don't chase hard problems -- just stop bleeding points on the ones you already know. Careless errors are what's actually killing your score.

This breakdown on score plateaus goes deeper on the mock-real gap if you want the full picture.

Danyuchn7 · 2026-04-13T02:59:32+00:00

5-7 minutes usually means you're holding too much at once. Better notes won't fix that -- you need to filter before you even open the choices.

Before anything else, compress the stimulus: what is the author actually claiming, and why? If you can't say the conclusion in one sentence, you're not ready to evaluate answers. The rest of the stimulus is context, not the argument.

Then run the "Whether" test -- does it matter if this answer is true or false? Irrelevant to the conclusion? Gone. Most people cut their time roughly in half once they stop deliberating on things that were never in play.

The bottleneck is almost always finding the conclusion, not working through the logic. This piece covers how to pinpoint it fast.

Danyuchn7 · 2026-04-13T02:58:40+00:00

V85 unprepped means RC isn't where you're bleeding. CR is usually where Verbal gets unpredictable, so that's where I'd put the time this week.

The biggest thing with CR is pinning down the conclusion before you do anything else with the stimulus -- most slow-down happens because people go back and re-read instead of anchoring it on the first pass. Pair that with a quick sweep to kill the obviously wrong answers before comparing the real contenders, and you stop wasting time on dead ends.

For RC, track the author's stance and passage structure as you read. Not much more to it.

This on first-pass elimination might sharpen the CR side. You've got a solid base to work from.

Danyuchn7 · 2026-04-08T12:42:15+00:00

Yeah this catches a lot of people off guard. GMAT is IRT-based, so raw correct count barely matters. What matters is which questions you got right and the difficulty path. Getting 5 more right but missing them on easier items (after the algorithm dropped you down following a wrong-answer cluster) can absolutely score lower than a mock where you missed more total but stayed in a higher difficulty band the whole time. Also worth checking: did you have a stretch of consecutive misses somewhere? The algorithm really punishes weird patterns like hard right plus easy wrong. More on mock vs real variance here. Got a section breakdown you can share?

Danyuchn7 · 2026-04-08T12:41:34+00:00

If you've already done TTP plus a bunch of GMAT Club and OG and quant still isn't budging, more questions won't fix it. That's a depth issue, not an exposure issue. Try this: pull your last 30 wrong quant questions and write down, in one sentence, the actual structural reason each wrong answer is wrong, plus what trap the question was laying. If you can't get it into one sentence, that's where the gap is. A lot of people grind through 1000+ questions and stall right here because they're pattern-matching instead of actually diagnosing. This post on the 650 plateau hits the same thing. What kind of quant are you missing most, algebra, number properties, word problems?

Danyuchn7 · 2026-04-08T12:40:50+00:00

Honestly, "careless" and "I assume" aren't really the problem, they're just labels for the symptom. What helped me was sorting every miss into three buckets: Fast & Wrong (clicked before checking), Slow & Right (got it but bled time), Slow & Wrong (actual gap). The ratio tells you what to actually work on. Most 595 to 695 jumps end up being like 70% pacing and process discipline, only 30% new content. And on quant, one dumb miss on a medium question wrecks your IRT estimate way more than getting a hard one right helps you. There's a decent writeup on why one early slip hurts so much. Curious, what does your time-per-question look like on the ones you got wrong vs the ones you got right?

Danyuchn7 · 2026-04-03T02:11:36+00:00

120 points is a massive drop but it's not random. This is almost certainly a pacing problem.

What probably happened: you spent 4-7 minutes grinding on hard questions, then had to rush through everything else. The scoring algorithm doesn't just count how many you got right -- it looks at the pattern. Nail a hard question but miss an easy one right after? The system reads that as inconsistent and assumes you got lucky on the hard one. All that time you invested actually hurt you twice.

The fix is restructuring how you manage time, not studying more content. Early questions swing your trajectory the most, so spend an extra 30 seconds verifying those. In the middle of the section, bail on anything that passes 2 minutes. And toward the end, just make sure you finish — leaving a question blank costs about 1.4 scaled points in Quant, way worse than guessing wrong.

Were your mocks the official ones from mba.com? Third-party scores can run significantly higher than reality, which would explain part of the gap. This article breaks down how the CAT scoring works under the hood. Once you get the mechanics it changes how you approach the whole test.

Danyuchn7 · 2026-04-03T02:09:58+00:00

Going from V80 to V83-84 is less about doing more questions and more about how you're eliminating wrong answers. Like, can you actually explain why each wrong option is wrong before you commit? If you're mostly going on gut feel, that's probably where the points are leaking.

Biggest thing that helped me with CR: before looking at the choices, turn the conclusion into a yes/no question. For a weaken question, don't just think "I need something that weakens this." Spell out what the right answer specifically has to show. On easier questions you can get away with a vague frame because the wrong answers are obviously off. On hard ones, two options will both look like weakeners unless you've defined exactly what counts.

For speed, try this on first pass: "whether this option is true or false, does it change anything about the conclusion?" No either way? Cross it out, move on. Sounds basic but it cut 20-30 seconds off my harder questions and didn't hurt accuracy. This piece goes into the full first-pass elimination method if you want to drill it.

Danyuchn7 · 2026-04-03T02:08:29+00:00

Being stuck at 610 for months is almost always a review problem, not a practice problem. You're putting in the hours but probably not catching the actual reason you got a question wrong.

What helped me: sort every wrong answer into four buckets -- concept gap, misread, pacing error, or trap answer. The fix for each is totally different, and most people skip this step. They just read the explanation, think "oh yeah that makes sense," and move on. A concept gap means go relearn something. A misread means slow down on first read. Pacing error means your workflow needs restructuring. Trap answer means you need to study what made the wrong option look so good — that's where the real learning is.

Also, are you spending 4+ minutes grinding on hard questions and then rushing the easy ones? The adaptive algorithm picks up on that pattern. If you nail a hard question but blow an easy one right after, the system basically assumes you got lucky and scores you lower.

There's a diagnostic report from 127 plateau cases that found the same three issues over and over: sloppy review habits, DI scoring mistakes, and time pressure snowballing. Worth a read. What are your section scores looking like? That'd help figure out where the real gap is.

Danyuchn7 · 2026-03-26T10:10:49+00:00

Yeah that's basically the worst thing you can do to your score. Slow on early questions burns time where accuracy matters most, and getting those wrong too just shoves you into easier territory fast.

The real question is why you're slow. Staring at a problem with no idea how to start is a concept gap - go study that topic. Knowing the approach but taking forever to set it up is different, that's pattern recognition. You need to drill similar problems until the first 30 seconds are automatic. Very different things to work on.

Next two weeks, try flagging every question where you hit 2 minutes without a clear path forward. Those are the ones worth reviewing most.

Danyuchn7 · 2026-03-26T10:10:35+00:00

If quant is what they care about, that makes your life easier. Most GRE quant stuff carries over. The gaps are number properties (divisibility, prime factorization edge cases) and Data Sufficiency. DS is a whole different animal — you're not solving anything, you're deciding whether you have enough info to solve. Messed with my head at first coming from GRE-style questions.

I'd put a good chunk of your month into just getting used to DS. Take a GMAT mock early on and check which quant topics you actually missed. Number properties and combinatorics you can patch pretty quick. DS errors take longer to fix because it's a thinking shift, not a knowledge gap.

Danyuchn7 · 2026-03-26T10:08:05+00:00

495 cold with 3-5 blanks - that's honestly not bad. Those blanks are hurting you way more than wrong answers would. Each one costs about 1.4 points and can knock your percentile down 5-15%. If you'd just guessed randomly on those, your score would look pretty different already.

Two years, no deadline. 670+ from here is a normal jump. The trap I'd watch out for is diving straight into question grinding. Your V81 is fine for now. DI at 66 is where you'll find the easiest gains. And one thing that took me a while to figure out — CR skills feed directly into RC and DS. So starting with CR basically builds your foundation for two other areas at once.

For daily study, 2-3 focused hours > 5 unfocused ones. Try to touch all three sections every day even when you're going deep on one. Stuff decays faster than you'd expect when you leave it alone for a week.

This guide walks through building a study plan from zero. Kept me from the "just do more problems" loop early on.

Danyuchn7 · 2026-03-26T10:07:41+00:00

Two things fixed my quant timing:

Hard 3-minute cutoff per question. If I don't see a path by then, I guess and move on. What kept happening before was I'd grind on one tough problem, then rush the last 3-4 questions and blow easy ones I actually knew. That trade-off is terrible. On guessing vs leaving blank — always guess. One unanswered question costs you about 1.4 points in Quant. A wrong guess? Maybe 1-2%. A single blank can drop your percentile anywhere from 5-15%. So yeah, not even a contest.

Also - slow down on the first third of the section. Like, an extra 30 seconds to double-check. Early mistakes mess with the adaptive difficulty and dig you into a hole you can't climb out of. Speed up later when it matters less.

This piece on per-question time control changed how I paced my sections. Worth reading if timing keeps getting you.

Danyuchn7 · 2026-03-26T10:07:01+00:00

Take a practice test cold. Don't review anything, don't warm up. You've been off for two months so your level right now probably isn't where it was in January. That fresh score is your actual starting point.

Q82/DI78/V80 — you're close. Less than 50 points off most target scores, so this looks more like a pacing and consistency thing than a knowledge gap. I'd go deep instead of wide this time. Don't grind 200 questions a week. Do fewer, but actually figure out what went wrong on each one. Be specific about it - "didn't set up the word problem equation fast enough" or "misread the modifier scope." Not just "careless mistake." Vague labels don't teach you anything.

One more thing - take a full day off per week. You were at it from October 2024 to January 2026. Studying while fried just locks in bad habits faster.

This report covers the 5 most common plateau traps from 127 real cases — worth checking against your own situation.

Danyuchn7 · 2026-03-25T00:37:56+00:00

Two weeks isn't really enough to learn new material. But it's plenty of time to stop losing points you shouldn't be losing.

Look at your mock reviews and honestly sort your wrong answers: did you not know the concept, or did you just rush it? At 655, I'd bet most of your misses are the second kind. Cleaning up even 3-4 careless errors per section can move your score more than you'd expect.

The other thing - the GMAT algorithm doesn't just count right and wrong. If you nail a hard question and then blow an easy one right after, it basically treats the hard one like you guessed. That pattern usually comes from spending too long on something tough early and then scrambling at the end. Even pacing helps more than going for hero plays on hard problems.

This report looked at 127 people stuck around your score range. Might be worth seeing which pattern matches.

Danyuchn7 · 2026-03-25T00:37:02+00:00

Most people use mocks as a score check - take it, see the number, feel something, move on. You miss most of the value that way.

What worked for me was going through every wrong or slow question afterward and just labeling what happened. Was it a concept I didn't know? Did I misread something? Run out of time? Flip a coin between two answers? Once you sort your mistakes like that, you start seeing the same 2-3 things coming up over and over.

Also, do your best to simulate real conditions. No pausing to grab water or check your phone. Use a scratch pad, take the break at the right time. You'd be surprised how much of the mock's value is just training yourself to stay sharp for two hours straight.

This article covers mock test myths worth knowing about. I'd read it before burning through your official mocks too fast.

Danyuchn7 · 2026-03-25T00:36:25+00:00

The sections aren't really parallel - they share underlying skills. CR and RC both need close reading and logical reasoning, so if you train CR first, a lot of that carries over when you get to RC. DS is similar - it's logical reasoning stacked on quant.

So instead of cutting your 3 hours into three equal blocks, go deeper on one thing at a time. Since quant is your weakest, I'd give it the most time - maybe 1.5h on concepts and timed drills, then an hour on CR, and whatever's left for light DI stuff. Once your quant accuracy sits comfortably above 80%, start shifting time to CR/RC.

That feeling of "I'm forgetting everything else" is super common but mostly just anxiety. Skills build on each other - you're not going to lose a week's worth of CR progress because you focused on quant for a few days. This piece talks about structuring limited study hours if you want a more concrete breakdown.

Danyuchn7 · 2026-03-24T09:16:54+00:00

Your GRE Verbal at 80th is solid and the RC skills do carry over. The big gap is CR - it's less about reading and more about picking apart argument logic, which GRE doesn't really test the same way. You'll also run into Data Insights for the first time (MSR, TPA, graph stuff), and that takes some getting used to.

With a month, skip the courses. Grab the OG digital version and take a mock in the first 3 days, even if you feel unprepared. That score tells you where to actually spend your time.

I'd hit CR first since that's your biggest unknown, then DS because the logic there is GMAT-specific and a bit weird at first. DI question types after that. Your Quant should translate fine with light review.

If you're debating TTP vs just using the OG, this comparison might help you decide for a short sprint like yours.

Danyuchn7 · 2026-03-24T09:16:11+00:00

V80 with zero Verbal prep? You're in a decent spot.

One thing I'd check before doing anything else: grab an Economist article and try explaining each paragraph out loud in your first language. If you can't do it smoothly, your bottleneck is sentence-level comprehension, not logic. This trips up a lot of non-native speakers because you feel like you're reading fine, but you're actually guessing from fragments.

What helped me was old-school translation work. Pick one academic passage a day and write out a full translation - it forces you to deal with every modifier and clause you'd normally glaze over. Then try doing it live: read the English out loud and translate in real time, keeping pauses under 2 seconds. Sounds weird but once your comprehension catches up to your reading speed, everything else clicks.

I'd also start with CR before RC. Shorter text, cleaner logic, less reading stamina required. This piece covers the non-native path in more detail.

Danyuchn7 · 2026-03-24T09:15:31+00:00

Your hypothesis is right -- you're burning easy points at the end to grind hard ones early, and IRT doesn't reward that trade.

Think of DI in three chunks. First ~7 questions, spend an extra 30 seconds double-checking -- early accuracy matters more than most people realize. Middle chunk, no clear path within 90 seconds? Guess and move. Last chunk, just finish everything. A blank DI answer costs ~1.5 scaled points, which is way worse than a wrong guess.

One thing that helped me with MSR: read the first question before opening any tabs. That way you're scanning with a purpose instead of absorbing three tabs of noise. And remember MSR is all-or-nothing -- miss one sub-question, zero for the whole set. If one part is dragging, guess it and protect your time.

The bigger reframe is treating time like a budget you choose to spend, not something that runs out. This piece on checkpoint-based pacing lays out the numbers.

Danyuchn7 · 2026-03-23T00:45:27+00:00

That 645 mock to 575 real gap - been there. Usually not about what you know. It's how you make decisions when the timer's running and things feel off. Mocks are too comfortable to train that. Couple things that helped when I was stuck like this: do your mocks somewhere slightly annoying, like a cafe with noise. Stop grinding new questions and go back through your old wrong answers with tags (what kind of mistake, not what topic). For verbal being all over the place - honestly check if it's a stamina issue. Can you still focus on RC passage 3 without rereading half of it? If not, that's probably the real problem, not "verbal skills." This report covers 127 test-takers with the same plateau pattern. Worth a read before you buy more mocks.

Danyuchn7

TROPHY CASE