Timed Practice and Full-Length Mocks

Procedure⏱ 1 h 30 minIntermediateApplies to: GRE General TestApplies to: Verbal ReasoningApplies to: Graduate school admissions

Build GRE Verbal speed, accuracy and stamina through a graded sequence of timed sets and full-length mock tests, with structured review after each session.

In this guide: How to prepare for GRE Verbal Reasoning

Timed practice turns what you know into what you can do under exam conditions. The GRE Verbal Reasoning section gives you 27 questions in 41 minutes (two sections, 18 minutes and 23 minutes, in the standard test). Untimed accuracy does not transfer automatically: you need to rehearse pacing, decision-making about when to move on, and the stamina to stay sharp through a full test.

This page sets out a progression from short timed sets to full-length mocks, and how to review each session so that the time you spend translates into score gains.

Before you start
  • A set of official GRE practice materials (ETS PowerPrep and the Official GRE Verbal Reasoning Practice Questions book) plus a question bank you have already worked untimed.

  • A quiet place, a timer, and a way to record answers and timings (paper log or spreadsheet).

  • Your error log from untimed practice, so you know which question types are slow or inaccurate.

  • A full-length mock scheduled only after you can complete a 20-question timed set within the target time.

SectionVerbal Reasoning
Questions per section20 (standard test); 27 in the two-section format used in some practice materials
Time per section30 minutes (standard test); 41 minutes for 27 questions
Average paceAbout 1.5 minutes per question
Recommended mock frequencyOne full-length mock per week in the final 4–6 weeks
Review-to-practice ratioAt least 1:1; ideally 1.5:1 in early weeks

Steps

  1. Before changing anything, measure where you are. Take one official Verbal section under strict timing, no pauses, no phone. Record the number correct and the time you spent on each question. This baseline tells you whether your problem is speed, accuracy, or both.

    You should see

    A completed section with a raw score and a per-question timing log. Expect the last few questions to feel rushed; that is normal on a first attempt.

  2. Verbal questions are not equal. Text Completion and Sentence Equivalence are usually faster; Reading Comprehension, especially long passages, takes longer. Set a rough budget: about 1 minute for short TC/SE items, 1.5–2 minutes for medium items, and up to 2.5–3 minutes for long RC sets. Practise hitting these budgets on 10-question sets before moving to full sections.

    You should see

    You finish 10-question sets within the summed budget, with no single question consuming more than about 3 minutes.

    Careful

    Do not memorise rigid per-question times. The budget is a guide; the real skill is noticing when a question is costing too much and deciding to guess and move on.

  3. Once you can hit per-question budgets, practise full 20-question sets in 30 minutes. Use a mix of question types in the order they appear on the test. Do not stop the clock to check answers. Mark any question you guessed so you can review it honestly.

    You should see

    You complete the set within 30 minutes and can report your score plus a list of guessed questions.

  4. Review is where the learning happens. For each wrong or guessed question, write down: the question type, why you missed it (content, logic, or timing), and the correct reasoning. Note any question where you spent more than 3 minutes. Add these entries to your error log.

    You should see

    An error-log entry per missed question, with a category and a one-line fix. Patterns should start to appear after three or four sets.

  5. In the final 4–6 weeks, take one full-length mock per week under test-day conditions: same time of day, no breaks beyond the official ones, no interruptions. Use official full-length tests where possible. The goal is stamina and pacing across sections, not just a score.

    You should see

    A complete mock with section scores and a note of where your energy or accuracy dropped.

    Careful

    Do not take more than two full-length mocks per week. Fatigue and burnout will lower scores and make the data misleading.

  6. After each mock, compare section scores and timing. Identify the section where you lost the most marks and the question types responsible. Set one or two specific goals for the following week (for example, 'cut long-RC time by 30 seconds per question' or 'stop guessing on TC without checking the sentence').

    You should see

    A short written plan for the next week with one or two measurable goals.

  7. In the last week, reduce volume. Do one or two short timed sets and review your error log rather than taking new full-length mocks. Protect sleep and keep the test-day routine familiar.

    You should see

    You enter test day rested, with your pacing habits and error-log fixes fresh in mind.

What to check

Scores are high untimed but drop sharply when timed.

Likely cause

You have not yet automatised the reasoning, so speed forces shortcuts that introduce errors.

How to check

Compare untimed and timed accuracy on the same question types. If the gap is large on RC, the problem is reading and reasoning speed, not knowledge.

Fix

Return to untimed practice on the weak types for a week, then reintroduce timing in 10-question sets before returning to full sections.

You run out of time on the last few questions every section.

Likely cause

One or two questions are consuming far more than their budget.

How to check

Look at your per-question timing log. Identify any question over 3 minutes.

Fix

Practise a hard stop: if a question passes its budget, mark a guess and move on. Review the question afterwards to see whether the extra time would have helped.

Mock scores fall in later sections.

Likely cause

Stamina or test-day routine is the issue, not content.

How to check

Compare accuracy in the first and second halves of the mock.

Fix

Take mocks at the same time of day as your real test, with the official breaks, and build up with longer timed sets before the next mock.

Notes

Use official materials for full-length mocks; third-party tests vary in difficulty and can distort your pacing data. Keep a single error log across timed sets and mocks so patterns are visible. If you are not sure whether a question was a guess, mark it during the test; honest data makes review useful.

See also