TOEFL 30-Day Pre-Exam Sprint Plan (2026)

Why 30 days = 40 focused hours

Thirty days is long enough to include two full mock-test cycles, short enough to hold test-day intensity, and close enough to exam day to treat test strategy — not raw English acquisition — as the primary lever. A 4-week budget of 10 hours/week gives you 40 focused hours. Against Cambridge’s Guided Learning Hours benchmark of 150–200 hours per CEFR level, 40 hours represents roughly a quarter of that — enough to move 0.5–1.0 score bands when the baseline is already Band 4.0+.

Weekly themes and spaced repetition

The four weekly themes are ordered around spaced repetition and desirable difficulty. Week 1 deliberately spreads time across all four sections, even though that feels inefficient — the goal is to surface error patterns you didn’t know you had. Week 2 narrows on the section or task types with the heaviest error density, exploiting the fact that focused work on weak areas yields more band movement per hour than spreading the same time evenly. Week 3 reintegrates under test conditions: a full mock test mid-week sits at the center, flanked by section practice tuned to the mock’s results. Week 4 is consolidation — light mock, no new material, error-log sweep, template drills.

Mock-test cadence and review windows

Mock-test cadence matters. One full mock in week 3 and a lighter one in week 4 calibrate your pacing against reality. More mock tests than that tend to diminish returns — the useful signal comes from careful review, not test-taking volume. A 90-minute review window immediately after each mock is non-negotiable; that’s where the learning happens, not during the test itself. Tagging each error by task type and cause (timing, vocabulary, comprehension, template execution) is what makes mock-test data actionable. Map the cause back to the relevant ETS scoring dimension for Speaking and Writing tasks — that’s where rubric-aligned review converts errors into reliable gains.

The cross-section maintenance principle

A maintenance principle runs through all four weeks: no single section goes untouched for more than 3 days. Skills decay fast near test day — a 5-day Speaking break costs you more than a 5-day Reading break because Speaking execution is the most fatigue-sensitive of the four. The schedule keeps a 20-minute Speaking touch every 2–3 days even during weeks that focus elsewhere.

What 30 days can realistically achieve depends on where you start. The table below sets expectations so you can decide whether a 4-week sprint matches your target, or whether you should extend the timeline.

If you have more than 5 weeks and flexibility to adjust, the custom generator gives you a gap-weighted plan over a longer window. If a single section is pulling your total down, the weakness plan concentrates the 30 days on your lowest band. After every practice block in this plan, follow the post-practice review guide — the 30-day sprint only delivers gains when each session ends with structured review.

The week-level themes (foundation, targeted, integration, consolidation) only work if the day-level structure carries them — and from what we see across 30-day cycles, the day-level structure is where most plans either compound or quietly fall apart. Below are sample daily blueprints for each of the four weeks — use them as a starting template and adjust around your real schedule.

Sample Week 1 day (foundation, 100 min)

25 min Reading practice + 15 min review · 23 min Speaking task + self-review · 25 min Listening practice + 15 min review. Skip Writing this day; rotate it into the next foundation day. Goal: touch all four sections within 48 hours and start your error log. End the day by tagging 2–3 errors by cause: timing, vocabulary, comprehension, or template execution.

Sample Week 2 day (targeted, 90 min)

Assuming Speaking is your weakest section: 23 min Speaking task + 15 min review · 23 min second Speaking task (different prompt type) + 15 min review · 15 min listening to a high-quality model response and shadowing it. Speaking gets 76 of the 90 minutes today; the other three sections each get a 20-minute touch every 2–3 days during this week to prevent decay.

Sample Week 3 mock-test day (240 min)

Protected Sunday morning. 150 min full mock test (Reading, Listening, Speaking, Writing back-to-back, no pauses except the official 10-minute break) · 90 min section-by-section review immediately after, while errors are still in working memory. Tag every error in the same taxonomy you’ve been using all month. The mock dictates Week 4’s focus areas.

Sample Week 4 day (consolidation, 75 min)

30 min targeted practice on the weakest section identified by the Week 3 mock + 15 min review · 15 min template drill (writing or speaking response patterns) · 15 min error-log sweep — re-read your tagged errors from earlier weeks and re-attempt the 2–3 you got wrong twice. No new material introduced in the final 7 days; everything is consolidation and pacing.

Even learners who follow a structured 4-week plan can lose half its value to a handful of recurring mistakes. Watch for these patterns in your own schedule.

Studying without an error-log taxonomy

Practice without tagged review is just reading the question twice. From day one, log every error against four causes: timing, vocabulary, comprehension, or template execution. Without this taxonomy, Week 4’s consolidation has nothing concrete to consolidate.

Skipping the 90-minute mock review

The mock test takes 150 minutes; the review takes 90. Learners routinely complete the mock then defer the review to “tomorrow” — by which point the specific errors are gone from working memory. The review must happen inside the same session, ideally without leaving the desk.

Treating Week 1 as inefficient

Spreading 4 sections across one week feels slow compared to drilling a single weakness. It is supposed to. Week 1 is a diagnostic — its job is to surface error patterns you can’t identify without breadth. Skipping straight to targeted practice means optimising blind.

Mock-test overload

More than 2 mock tests in 30 days produces diminishing returns. The signal lives in review, not in test volume. Three or four mocks fragment your schedule, eat into review time, and drive test fatigue right when you need fresh attention. Stay at one full + one light.