A 140-to-150 improvement is a 10-point jump, real, common at Lovare, and not a montage. Plan in months, not weeks: typically three to six of structured work, front-loaded on diagnosis. The encouraging math: big jumps from lower bands are more available than small jumps from high bands, because the early points come from fixing systems, not grinding margins. The plan below runs in the only order that works: diagnose what 140 means in your specific case, target the delta that defines 150, and train the gap with feedback loops instead of volume.
Diagnostically, a 140 is usually a fundamentals problem wearing a timing costume. At this level the issue is rarely speed, it is that too many questions are being answered on vibes: stems half-read, answer choices compared to each other instead of to the stimulus, question types not yet recognized as types. Untimed accuracy is the tell: if you can’t hit 85%+ with unlimited time, time was never the constraint. That diagnosis is the plan’s foundation, the same score can be produced by different failures, and your blind review (below) confirms which version is yours.
The defining capability of the 150 band: reliable type-recognition and honest timing, a scorer who solves from the stimulus, not the answer choices. That is the target state, not “more points” but a specific operational difference your training should be reverse-engineered from.
Phase 1 (weeks 1 to 3), Diagnose. Full diagnostic plus blind review. Separate the two causes of every miss: didn’t know, or knew and lost it under pressure. The ratio sets the whole plan. Phase 2 (weeks 3 to 8), Untimed mastery. Question-type by question-type, accuracy before speed; you cannot pace what you cannot solve. Phase 3 (weeks 8 to 14), Timed integration. Sections, then full tests, with blind review after every one, the Lovare Loop: diagnose, train, stress-test, review, update. Phase 4, Calibration. Test conditions, score stability, retake decision made on data.
Run blind review religiously: unlimited-time re-solves of everything flagged or missed, before seeing the key. The gap between that score and your timed score, the Blind Review Delta, splits your problem cleanly. If the delta runs big, celebrate carefully: the points exist, they are simply being lost to the clock and to nerves, and conditioned timed practice recovers them quickly. If the delta is small, the gap is genuine content, build it untimed before any speed work.
Lovare’s core diagnostic applies with full force on this jump: knowledge failure and anxiety failure produce the same wrong answers through different machinery. At this band both causes are usually active at once, real content gaps tangled with test-day dread, so the plan alternates: build knowledge untimed, then deliberately practice performing it under pressure. The Blind Review Delta above is your sorting tool, let it assign your hours, because content-grinding an anxiety problem (or breathing through a knowledge problem) is the most common way this jump stalls.
Plan three to six months. Faster happens, especially when the Blind Review Delta is large and the gap is mostly pressure, but six weeks of cramming reliably produces two points and a worse relationship with the test. Two refinements: progress is lumpy (plateaus then jumps, as systems consolidate), and the calendar should be set by score stabilitynot hope, you are ready to sit when three consecutive practice tests land at or above target under real conditions.
Budget a season, not a sprint: most successful jumps of this size land between month three and month six. The variance is diagnosis quality, not talent, targeted plans finish at the front of the range.
Yes, it is one of the most common successful jumps we coach, and it requires no rare aptitude. What it does require: an honest split of your misses into knowledge versus pressure, and a weekly loop that trains the real cause.
Because something specific is being practiced around instead of through. Two blind-reviewed tests will name it, a question type, a pacing behavior, or test arousal, and plateaus end quickly once the real cause gets the hours.
Treat this jump as an engineering project with a known failure mode: undiagnosed effort. Every hour you spend before sorting knowledge-losses from pressure-losses is an hour spent guessing. Sort first, then train narrow, then test wide, and 150 stops being a hope and becomes a schedule.