GRE Quant: Master Arithmetic, Algebra, Geometry, and Data Analysis

Last updated: Tue, Jul 7, 2026

GRE Quant: Master Arithmetic, Algebra, Geometry, and Data Analysis

GRE Quantitative Reasoning rewards precise thinking, compact calculations, and strong control of core math. You do not need advanced calculus, but you do need to translate everyday language into equations, navigate traps, and choose the fastest path to a correct answer. This guide breaks down the four content areas, the question formats, scoring, timing, and the practical drills that move you from a Q158 plateau to Q168 and higher. You will see formulas you must memorize, step-by-step walkthroughs, and compact routines that compress study time while expanding accuracy.

Whether you are starting from rusty high school math or you already score in the mid 160s, your next gains come from better habits, not just more practice. Build the right habits here, then cement them with targeted drills and mock tests.

The GRE Quant section at a glance

GRE Quant measures how well you reason with numbers, algebraic relationships, geometry, and data. The test uses simple computations to probe whether you can structure a problem correctly, spot constraints, and avoid common pitfalls. Almost every question can be solved by multiple methods, and time is tight enough that method choice matters. Think in terms of translation, triage, and verification.

Format and timing reflect those goals. You take two Quant sections, each adaptive at the section level. The first section mixes easy to medium difficulty. Your performance on that first section determines the difficulty mix of the second, which in turn influences your scaled score. The on-screen calculator is basic, so you still need strong mental math and estimation. You also face several question formats, each with its own shortcuts.

Here is a compact view of the section:

Two sections of Quant, 12 questions per section, 21 minutes per section, 42 minutes total.
Question formats: Quantitative Comparison, Multiple Choice Single Answer, Multiple Choice Multiple Answer, Numeric Entry, Data Interpretation sets.
Content coverage: arithmetic and number properties, algebra and functions, geometry and coordinate geometry, data analysis and statistics, with probability and combinatorics at a basic level.

A useful rule of thumb is that accuracy on the most discriminating problems, often algebraic translation, quantitative comparison, and multi-step Data Interpretation, moves your scaled score. Getting fast on easy points is necessary, but reducing careless errors and building a decision tree for tough problems is what raises you above Q165.

For official confirmation of formats and scoring, consult the ETS Quantitative Reasoning measure overview. It outlines section adaptivity and the scoring scale from 130 to 170 in 1-point increments. While ETS does not publish exact raw-to-scaled mappings, the test is designed so that small accuracy gains, particularly on the harder second section, can yield large scaled-score gains. See ETS Quant overview: https://www.ets.org/gre/test-takers/general-test/about/quantitative-reasoning (external).

How scoring works and what Q158 vs Q168 really means

GRE Quant is section-level adaptive. Your first Quant section mixes easier and moderate questions. Performance on that section routes you to a second section that is either easier or harder. The second section carries more weight, because it contains more discriminating items. Two test takers with the same total number of correct answers can end up with different scaled scores if one faced the harder second section and answered those harder items correctly.

Because ETS does not publish raw-to-scaled tables, you should treat any conversion you see online as approximate. Still, practical prep requires targets. For most recent forms, you can think of the following broad patterns. If you land a harder second section and miss 0 to 1 total across both sections, you are in the 170 range. Miss 2 to 3 and you are often at 168 to 169. Miss 4 to 5 with a harder second section and you typically sit near 166 to 167. If your second section is easier, you have less headroom, so even with few misses your scale may cap in the low to mid 160s.

Here is a simplified comparison to calibrate goals:

Scenario	Section 2 difficulty	Total misses	Likely scaled score band
A	Harder	0 to 1	170
B	Harder	2 to 3	168 to 169
C	Harder	4 to 5	166 to 167
D	Easier	0 to 2	162 to 165
E	Easier	3 to 5	158 to 161

These are not guarantees. They describe the general feel of recent tests many high scorers report. The lesson: you do not need perfection to score 168+, but you do need the harder second section and strong accuracy on it. That is why targeted improvement from Q158 to Q168 focuses on getting routed to the harder second section, then converting tough items with high precision.

To steer your prep, track three metrics for each full-length practice: accuracy by difficulty band, accuracy by format, and error type. If you are stuck around Q158, you likely have a mixture of content gaps and decision speed issues. If you are around Q164 to Q166, most misses come from one or two leaky content areas, plus a few unforced errors. Your plan should move from fixing fundamentals to sharpening those high-leverage edges.

For study integration across the test, keep your Quant plan aligned with your broader GRE approach. The comprehensive GRE hub offers context for how Quant scores interact with Verbal and AWA in admissions and scholarships.

Timing and triage: a practical system for 21 minutes

With 12 questions in 21 minutes, your average budget is about 1 minute 45 seconds per question. That average is not how you should spend your time. Easy points are often faster than a minute, while the hardest problems can reward 2 minutes or a bit more. Build a flexible budget, make quick triage decisions, and practice one-pass marking so you do not sink time into low-yield paths.

Use this target budget:

Quantitative Comparison: 60 to 90 seconds. If you do not see a relationship fast, test simple values, then move on.
Single-answer multiple choice: 75 to 105 seconds. Set up the equation or shortcut. If algebra grows, consider an alternative method.
Multiple-answer multiple choice: 90 to 120 seconds. These often require checking several conditions. Avoid partial correctness.
Numeric Entry: 90 to 120 seconds. Precision matters. Estimate first, then compute.
Data Interpretation: 2 to 3 minutes per set introductory question, then 75 to 90 seconds per follow-up, depending on chart complexity.

Organize your section with a triage code you can execute in under 5 seconds:

Solve now: clear path, expected under 90 seconds.
Solve later: promising but time heavy, mark and return after harvesting easy points.
Skip and guess: low expected value, such as tangled geometry with several unseen constraints, or a multi-case Data Interpretation item that would push you over budget.

Here is a timing worksheet you can emulate in practice sets:

Item type	Budget per item	Typical shortcut
Quantitative Comparison	60-90 s	Testing numbers, boundary cases, algebraic isolation
MC, single answer	75-105 s	Backsolving, plugging smart numbers, recognizing patterns
MC, multiple answers	90-120 s	Check constraints sequentially, eliminate by impossibility
Numeric Entry	90-120 s	Round-then-correct, fraction arithmetic, factor pairing
Data Interpretation	2-3 min set opener, 75-90 s follow-ups	Pre-scan axes and units, compute once, reuse

When you practice, do not allow heroic rescues. If a solution path is not emerging in the first 30 seconds, mark the item, write a one-line plan in the scratch space, and move on. That habit alone can reclaim 2 to 3 minutes per section. Fold in a structured review cycle to learn from those marks, and your score rises because your time allocation matches point value.

To refine pacing alongside your broader test tactics, pair this section with the GRE test-day strategy guide. It shows how to align section timing with warm-up routines, break management, and mental resets.

Arithmetic and number properties: the foundation you must master

Arithmetic on the GRE is not about heavy computation. It is about clean fraction work, ratios, percents, place value, divisibility, and exponents. These topics show up directly and also hide inside algebra, geometry, and data problems. You want instant recall of core facts and flexible manipulation.

Key clusters to master:

Fractions and ratios: a/b = c/d implies ad = bc. If x is p% of y, then x = (p/100)*y.
Percents and growth: A price increases by r% then decreases by r%, the net change is negative, equal to r^2/100% loss. Compound growth: A = P(1 + r/n)^(nt).
Exponents: a^m * a^n = a^(m+n), a^m / a^n = a^(m-n), (a^m)^n = a^(mn), and a^(-n) = 1/a^n. For roots, sqrt(ab) = sqrt(a)*sqrt(b) if a, b >= 0.
Divisibility: Test for 2,3,4,5,6,8,9,10. Prime factorization guides LCM and GCD.
Absolute value and distance: |x - y| is the distance between x and y on the number line.

A small set of percent and ratio templates saves minutes:

Percent change: (new - old)/old * 100%. For chained changes, multiply multipliers: a 20% increase then 15% decrease yields multiplier 1.2 * 0.85 = 1.02, so net 2% increase.
Mixture problems: Use the balance method. Suppose you mix solutions with concentrations c1 and c2 to achieve ct. The ratio of amounts is (c2 - ct) : (ct - c1).
Work rates: If A takes a hours, B takes b hours, working together they take t hours with 1/t = 1/a + 1/b. For combined average speed, if distances are equal, harmonic mean applies.

Example 1, percent change and ratio thinking: A shirt priced at 50 dollars goes on sale for 30% off. Then a coupon takes an additional 20% off the sale price. What percent of the original price is the final price?

Compute multipliers: first 30% off is 0.7, then 20% off is 0.8. Combined multiplier 0.7 * 0.8 = 0.56.
Final price is 56% of the original. Percent reduction is 44%. The test may ask either.

Example 2, fraction addition shortcut: Compute 7/12 + 5/18.

LCM of 12 and 18 is 36. Convert: 7/12 = 21/36, 5/18 = 10/36.
Sum is 31/36. If a numeric entry asks for decimal, know 36*0.86 = 30.96, so decimal is about 0.8611....

Example 3, exponents and units: If x = 2^3 * 3^2 * 5, how many positive divisors does x have?

Prime exponents are 3, 2, 1. Number of divisors is (3+1)(2+1)(1+1) = 4*3*2 = 24.

Your goal is to make these manipulations automatic. For quick formula review and drill prompts, use the GRE arithmetic formulas cheat sheet. It compresses the facts you want to recall in under 10 seconds during a test.

Finally, practice estimation. If a Data Interpretation question gives a bar at roughly 78 and another at 52, exact difference is 26. If the options are spread out by tens, estimation gets you there instantly. Keep three mental anchors for percent-of-a-number: 10% is one decimal left, 5% is half of 10%, 1% is two decimals left. Many answer options are engineered so that these benchmarks are enough.

Algebra and functional relationships: translation over technique

Algebra measures whether you can represent constraints precisely and move symbols without error. You should be comfortable isolating variables, working with inequalities, factoring, handling quadratics, and interpreting functions. Most algebra on the GRE does not require long computations if you pick the right entry point.

Core tools:

Linear equations: ax + b = cx + d implies x = (d - b)/(a - c) if a != c.
Inequalities: Multiplying or dividing by a negative flips the sign. Intervals and critical points drive solution sets.
Factoring: x^2 - y^2 = (x - y)(x + y), ax^2 + bx + c = a(x - r1)(x - r2).
Quadratic formula: For ax^2 + bx + c = 0, x = (-b ± sqrt(b^2 - 4ac))/(2a). Discriminant tests number of real roots.
Functions: If f(x) = 2x^2 - 3x, then f(x + 1) requires substitution, not distribution magic.

Two high-yield methods reduce cognitive load:

Plugging in numbers. If a problem is abstract and involves ratios or percent, pick legal values that simplify arithmetic. For example, if x is 20% of y and z is 40% of y, choose y = 100 so x = 20, z = 40. Compute what the question asks.
Backsolving. If answer choices are numeric and the problem can be inverted, start with the middle answer, test feasibility, and adjust higher or lower. This is efficient in rate, work, and mixture problems.

Example 1, absolute value inequality: Solve |2x - 5| < 9.

Rewrite as compound inequality: -9 < 2x - 5 < 9.
Add 5: -4 < 2x < 14.
Divide by 2: -2 < x < 7. That is the solution set.

Example 2, system with substitution: Given x + y = 7 and 2x - y = 1, find x and y.

Add equations: (x + y) + (2x - y) = 7 + 1, so 3x = 8 gives x = 8/3.
Substitute into x + y = 7: 8/3 + y = 7 so y = 7 - 8/3 = 21/3 - 8/3 = 13/3.

Example 3, function composition: If f(x) = x^2 + 2 and g(x) = 3x - 4, compute f(g(2)).

First g(2) = 3*2 - 4 = 2.
Then f(2) = 2^2 + 2 = 6.

Inequalities with rational expressions frequently appear. A standard approach is to find critical points where numerator or denominator is zero, then test intervals:

Example 4, inequality with rational expression: Solve (x - 3)/(x + 1) > 0.

Critical points at x = 3 and x = -1 (denominator cannot be zero).
Test intervals: (-infty, -1), (-1, 3), (3, infty).
Choose test values: x = -2, expression is (-5)/(-1) = 5 > 0, so interval works. x = 0, expression is (-3)/(1) = -3 < 0, not working. x = 4, expression is (1)/(5) > 0, works.
Solution: (-infty, -1) union (3, infty).

Make algebra your strength by drilling translation more than rote technique. For targeted problem sets, use the algebra practice problems. Work them untimed first to ensure correct structure, then repeat timed to simulate test constraints.

Geometry and coordinate reasoning: know the pictures, not every theorem

GRE geometry spans lines and angles, triangles, circles, polygons, 3D solids, and coordinate geometry. The test expects you to know common theorems and formulas, but it does not dive into obscure Euclidean proofs. Success comes from recognizing patterns, drawing to scale when helpful, and labeling systematically.

Core formulas to memorize and apply:

Triangles: Sum of interior angles is 180. Area = (1/2)bh. Pythagorean: a^2 + b^2 = c^2. Special right triangles: 3-4-5 and multiples, 5-12-13 and multiples, 45-45-90 with legs x and hypotenuse x*sqrt(2), 30-60-90 with sides x, x*sqrt(3), 2x.
Circles: Circumference = 2πr. Area = πr^2. Arc length for angle θ degrees is (θ/360)*2πr. Sector area is (θ/360)*πr^2.
Polygons: Sum of interior angles = (n - 2)*180. Regular polygon interior angle = ((n - 2)*180)/n.
Coordinate geometry: Distance = sqrt((x2 - x1)^2 + (y2 - y1)^2). Midpoint = ((x1 + x2)/2, (y1 + y2)/2). Slope m = (y2 - y1)/(x2 - x1).

A compact reference table helps during review:

Shape or concept	Formula or fact	Notes
Triangle area	`A = (1/2)bh`	Base and height are perpendicular
Right triangle	`a^2 + b^2 = c^2`	Recognize 3-4-5 and 5-12-13
45-45-90	`x, x, x*sqrt(2)`	Isosceles right triangle
30-60-90	`x, x*sqrt(3), 2x`	Hypotenuse equals 2 times short leg
Circle circumference	`2πr`	Units linear
Circle area	`πr^2`	Units squared
Rectangle area	`lw`	Perimeter `2(l + w)`
Slope	`(y2 - y1)/(x2 - x1)`	Parallel lines have equal slopes

Example 1, shaded region: A rectangle measures 10 by 6. A circle with radius 3 is inscribed so that it touches two adjacent sides and a corner of the rectangle. What is the area of the rectangle not occupied by the circle?

Circle area: πr^2 = 9π.
Rectangle area: 10*6 = 60.
Shaded area: 60 - 9π. If a numeric choice is needed, approximate π ≈ 3.14, shaded area ≈ 60 - 28.26 = 31.74.

Example 2, coordinate slope and perpendicularity: A line passes through (2, 3) and (5, 9). What is the slope of a line perpendicular to it?

Slope of the given line is (9 - 3)/(5 - 2) = 6/3 = 2.
Perpendicular slope is the negative reciprocal, -1/2.

Example 3, polygon interior angles: What is the measure of each interior angle of a regular nonagon?

Sum of interior angles is (n - 2)*180 = 7*180 = 1260.
Each angle is 1260/9 = 140 degrees.

Many geometry questions embed algebra. For instance, you may get a coordinate geometry question that asks for where two lines intersect, which is a system of equations. Or a circle question that uses the Pythagorean theorem to find radius. When stuck, draw a diagram, label known values, and look for right triangles or parallel lines that create angle relationships. If the figure is not drawn to scale, trust the labels, not your eyes.

Data Analysis and Interpretation: statistics, probability, and reading graphics

Data Analysis on the GRE includes single- and multi-graph sets, tables, and word problems involving descriptive statistics, probabilities, and counting. These appear as standalone questions and as Data Interpretation sets. Your goals: read axes and units before numbers, compute once per data point when possible, and know when to estimate.

Essential statistics:

Mean: average = sum/count.
Median: middle value, or average of two middle values if even count.
Mode: most frequent value.
Range: max - min.
Standard deviation: a measure of spread around the mean. On the GRE, you rarely compute it exactly. Compare two datasets by spread from the mean.

Probability basics:

Complement: P(A) = 1 - P(not A).
Independent events: P(A and B) = P(A)*P(B).
Mutually exclusive: P(A or B) = P(A) + P(B).
Conditional: P(A|B) = P(A and B)/P(B).

Counting principles:

Multiplication principle: if task 1 has m options and task 2 has n, total mn.
Permutations without repetition: P(n, r) = n!/(n - r)!.
Combinations: C(n, r) = n!/[r!(n - r)!].

Example 1, median from a histogram: A histogram shows 50 data points across five bins. If the first two bins contain 10 and 15 points, and the third contains 12, the median lies in which bin?

The median is the 25th and 26th values averaged. After the first two bins, you have 25 points. The 25th is at the end of the second bin, and the 26th is in the third bin. So the median lies on the boundary between bin 2 and bin 3. If the question asks the bin containing the median, and bins are continuous, the third bin contains the 26th and thus also contains the median position.

Example 2, expected value quick check: A bag has 3 red and 2 blue marbles. You draw one marble at random, which pays 5 dollars if red and 2 dollars if blue. Expected value is?

P(red) = 3/5, P(blue) = 2/5.
EV = (3/5)*5 + (2/5)*2 = 3 + 0.8 = 3.8 dollars.

Example 3, Venn diagram with two sets: In a class of 40 students, 15 take biology, 22 take chemistry, and 8 take both. How many take neither?

Use inclusion-exclusion: |B union C| = 15 + 22 - 8 = 29.
Neither is 40 - 29 = 11.

Data Interpretation sets often hinge on unit traps. Suppose a line chart shows revenue in millions per quarter, and a table shows costs per year. Questions may ask for year-over-year change in profit. Your move: translate units into the same frame, compute quarter sums for revenue, subtract annual cost once. If you compute cost per quarter mistakenly, you double count and fall into a trap.

Finally, when you see a small sample with two datasets and a standard deviation question, compare spreads relative to the mean. If set A has values 4, 5, 6 and set B has 1, 5, 9, both have the same mean of 5, but set B has larger spread, so larger standard deviation. This sort of comparison appears in Quantitative Comparison format too, where calculation is not necessary.

Quantitative Comparison: the fastest ways to get them right

Quantitative Comparison (QC) asks you to compare two quantities without always computing exact values. Your answer choices are always the same four options: A if Quantity A is greater, B if Quantity B is greater, C if they are equal, D if the relationship cannot be determined from the information given. Fast QC performance depends on three habits: simplify, test strategic values, and watch domain constraints.

Use this structured approach:

Simplify symbols as far as possible. Factor, cancel, or isolate key terms.
Test baseline values. Start with simple numbers like 0, 1, -1, 2, fractions like 1/2, and extremes when allowed.
Respect the domain. If variables are integers, odd, positive, or nonzero, your test values must match.
Try to disprove equality. If you can find two legal values that change the relationship, the answer is D.
If expressions are clearly equal or can be manipulated to equal, choose C. Be cautious with squares and absolute values.

Example 1: Given x > 0, compare Quantity A: (x + 1)^2 and Quantity B: x^2 + 2x + 1.

Expand Quantity A: it is x^2 + 2x + 1, which matches Quantity B exactly.
Answer is C.

Example 2: Given -1 < x < 1, compare Quantity A: x and Quantity B: x^2.

Test x = 1/2: x = 0.5, x^2 = 0.25, so A > B.
Test x = -1/2: x = -0.5, x^2 = 0.25, so B > A.
Relationship changes. Answer is D.

Example 3: Given a and b are positive integers and ab = 36, compare Quantity A: a + b and Quantity B: 15.

Factor pairs: (1,36) sum 37, (2,18) sum 20, (3,12) sum 15, (4,9) sum 13, (6,6) sum 12.
Depending on pair, a + b can be more than, equal to, or less than 15. Answer is D.

In QC, mental math baseline values are your toolset. Memorize squares up to 20, cubes up to 10, and common fractions-to-decimals. Test small corner cases that often flip signs, like x = 0, x = 1, x = -1, and extremes where constraints permit, like very large numbers or numbers near zero.

Multiple choice and numeric entry: methods that beat raw algebra

Most GRE Quant questions permit multiple routes. Your job is to pick the one that minimizes time and error rate. Three flexible methods cover a large share of the test: backsolving, plugging in numbers, and proportional reasoning. Numeric Entry questions remove answer choices, but often the same shortcuts apply.

Backsolving works when the prompt asks for a number, answer choices are numeric, and the problem can be inverted. Start with the middle choice so you can adjust direction intelligently.

Example, backsolving in a rate problem: A machine produces widgets at a constant rate. If 6 machines working together take 5 hours to complete a job, how many hours would 10 machines take to complete the same job, working at the same rate?

Work is rate times time times machines. Let one machine have rate r. Original work is W = 6*r*5 = 30r. Same work W must be 10*r*t.
Solve 10*r*t = 30r gives t = 3. If you had answer choices, backsolving with the middle value would speed validation.

Plugging in numbers is ideal for percent, ratio, and abstract variable questions.

Example, plugging in with ratio: If x is 25% of y and y is 40% of z, what percent of z is x?

Pick z = 100. Then y = 40, x = 25% of 40 = 10. So x is 10% of z.

Proportional reasoning helps when quantities scale linearly.

Example, recipe scaling: If 4 cups of flour make 24 cookies, how many cups are needed for 18 cookies, assuming direct proportion?

Cookies per cup is 24/4 = 6. For 18 cookies, you need 18/6 = 3 cups.

For Numeric Entry, estimation and rounding-then-correct save time. If a computation is 548/37, note that 37*15 = 555, which is close, so the decimal is just under 15. If an exact decimal is required and time runs out, convert to a reduced fraction to avoid calculator slip-ups.

Finally, always scan answer choices before committing to a method. If answers are far apart, estimation is safe. If answers are clustered, you need precision. Let the answer set tell you the tolerance required.

Mental math and calculator strategy: when to click and when to compute

The GRE calculator is a four-function tool with a square root, memory keys, and parentheses. It cannot factor polynomials or do symbolic algebra. Used well, it prevents arithmetic slips. Used poorly, it burns time. Build a decision rule: only use the calculator when the arithmetic is messy enough that mental math would be slower or error-prone.

Three habits improve calculator use:

Pre-simplify. Factor numerators and denominators before typing. Reduce fractions to avoid long decimals. For example, 210/84 simplifies to 5/2 before you even think about the calculator.
Chunk inputs. For 73*48, compute 70*48 = 3360 and 3*48 = 144, sum to 3504 in one or two mental steps. This is faster than clicking.
Verify with estimation. After a calculator output, do a quick magnitude check. If you divide a larger number by a smaller one and get a result under 1, you likely reversed the operands.

Keep a mental math kit:

Squares: 11^2 = 121, 12^2 = 144, up to 20^2 = 400.
Fractions to decimals: 1/3 ≈ 0.333, 2/3 ≈ 0.667, 1/6 ≈ 0.167, 5/8 = 0.625.
Percent anchors: 10%, 5%, 1% rules for quick interpolation.

A comparison of when to use or skip the calculator:

Situation	Use calculator?	Rationale
Long division with awkward primes, e.g., `739/17`	Yes	Saves time and reduces slip risk
Multiplying two two-digit numbers with easy factors, e.g., `24*25`	No	`2425 = 600` instantly via `254 = 100`, times 6
Square roots of non-perfect squares, e.g., `sqrt(38)`	Yes	Quick approximation if required
Fractions with obvious reduction, e.g., `252/63`	No	Reduce to `4` mentally

Practice both with and without the calculator. On test day, you want the choice of tool to be automatic, not an internal debate. The more fluent your mental math, the more the calculator becomes a safety net rather than a crutch.

The fastest path from Q158 to Q168+: a targeted playbook

Moving from Q158 to Q168 is not about solving harder math. It is about eliminating avoidable errors, solidifying two or three weak content areas, and learning to harvest the right points on the right timeline. This playbook focuses on the highest return actions for that transition.

Phase 1, two weeks, accuracy first: - Identify your three biggest error categories from recent practice: careless arithmetic, misreading constraints, algebraic setup, geometry formulas, or Data Interpretation misreads. - Drill ten high-frequency problem types per category, untimed, focusing on perfect setup and clean arithmetic. If you cannot explain each step aloud, you do not own the pattern yet. - Build a one-page formula sheet with percent, ratio, exponents, triangles, circles, and coordinate formulas. Write it from memory daily, check, correct, and rewrite until perfect in under 3 minutes.

Phase 2, two to three weeks, timing and decision rules: - Convert those same drills to timed sets: 12-question sets in 21 minutes, then 24 in 42. Apply triage codes, force yourself to mark and move when time is up. - Add Data Interpretation sets to each timed practice. Pre-scan charts for units and scales before solving any question. - Build two or three standard approaches for each format. For QC, always test 0, 1, -1 when legal. For numeric entry, round-then-fix.

Phase 3, two weeks, mock tests and analytics: - Take two to four full-length GRE mock practice tests under test-like conditions. Use the same scratch setup, time-of-day, breaks, and calculator use you will use on test day. - After each test, complete a deep error log with five fields: problem ID, type, cause (content, setup, arithmetic, time, misread), fix (what you will do next time), and a similar practice problem to cement the fix. - Target the harder second section by maximizing first-section accuracy. On the harder second section, adopt a sharp triage. It is better to guess one low-yield 3-minute knot and bank time for two medium-high value questions than to lose both.

Along the way, use structured guidance so you do not guess what to study next. The GRE score improvement framework explains how to pick the right metrics and milestones for each score band. If you want a program that aligns daily tasks to your target schools and timeline, explore the GRE career-aligned mentorship program. It integrates study plans, analytics, and application strategy.

Practice design: what to drill, how to space it, and when to simulate

Quality practice is deliberate. You need three layers: skill drills, mixed sets, and full-length simulations. Each layer should have a purpose and measurable outcomes. Resist the urge to grind random problems without feedback loops.

Skill drills: Pick one topic, like percent change with chained discounts or factoring quadratics. Do 10 to 15 problems of that type. First pass is untimed, focus on method clarity. Second pass is timed, focus on pace without losing reasoning steps. Third pass, do the same problems a week later to test retention.
Mixed sets: Build 12-question sets that mimic the section mix. Include at least one Data Interpretation set, two QC items, and a spread across arithmetic, algebra, and geometry. Practice pacing and triage here. Score, then tag every miss with an error type and a specific fix.
Simulations: Sit for full-lengths with real timing, minimal pauses, and your test-day scratch routine. Practice the pre-section warm-up, and the between-section reset.

The spacing of drills matters. Use a simple schedule:

Same-day review: After each practice set, re-solve every miss the right way immediately. Capture in the error log.
Next-day review: Revisit those same misses and any near-misses to confirm the fix holds.
One-week review: Sample 30 to 50 percent of past misses to ensure durability. Adjust your formula sheet if you repeatedly forget a fact.

To plan your weeks and align Quant with Verbal and AWA, use the GRE study plan templates. They help you stage Quant emphasis around other sections, so you avoid fatigue spikes and keep the whole test improving together.

Word problems and translation: from language to math in four moves

Most algebra and arithmetic questions on the GRE are word problems wearing light disguises. Translation is the skill that unlocks them. Build a four-move sequence: define variables, map relationships, express constraints, and check units. Do it with short lines on scratch paper, not paragraphs.

Move 1, define variables with purpose: - Use letters that connect to the story, like p for price, q for quantity, t for time. - Note constraints next to variables: p > 0, q integer, 0 < r < 1.

Move 2, map relationships: - Translate sentences into equations or inequalities. Example: "Twice as many apples as pears" becomes a = 2p. - For rate and work problems, write the skeleton first: work = rate * time.

Move 3, express constraints: - Boundaries matter: "at least", "no more than", "exactly", "between", "inclusive". - For consecutive integers, define the smallest integer and build up, like n, n+1, n+2.

Move 4, check units: - Keep every quantity in consistent units. Convert minutes to hours, centimeters to meters, as needed. - Label your totals. If you add costs and quantities, something is off.

Example, two-variable system from a store discount: A store sells pens at 2 dollars each and notebooks at 5 dollars each. During a sale, all items are 20% off. A customer buys a total of 10 items and pays 28 dollars. How many pens did the customer buy?

Define variables: p pens, n notebooks. p + n = 10. Prices after discount: pens = 1.6, notebooks = 4.0.
Equation for cost: 1.6p + 4n = 28.
From p + n = 10, p = 10 - n. Substitute: 1.6(10 - n) + 4n = 28 gives 16 - 1.6n + 4n = 28.
Simplify: 16 + 2.4n = 28 so 2.4n = 12 and n = 5. Then p = 5.

Example, consecutive integers and products: The product of three consecutive integers is divisible by 6. Is the product necessarily divisible by 24?

Three consecutive integers include one multiple of 3 and at least one even. Divisible by 6 is guaranteed.
For divisibility by 24, you need three factors of 2, that is 2^3. Consider 2*3*4 = 24, divisible by 24. Consider 1*2*3 = 6, not divisible by 24. Not necessary.
This reasoning is faster than enumerating all cases.

Throughout, keep your equations lean. The most common errors come from writing too many symbols and then losing track of constraints. Practice stating the question in your own words before you start the algebra. If you cannot express what you are solving for in a short sentence, you will likely wander.

Error logging and analytics: fix causes, not symptoms

An error log is not a list of wrong answers. It is a diagnosis tool. Record problem ID or a short description, the category, the exact cause, and a prevention plan. Then close the loop by drilling a twin problem with the prevention plan in place.

Use these cause categories:

Content gap: formula missing, concept misunderstood.
Setup error: wrong equation, misread condition, unit slip.
Arithmetic slip: computational mistake after correct setup.
Timing: ran out of time, over-invested in a low-yield path.
Trap: selected an answer that matches a common misconception.

For each cause, specify a prevention:

Content gap: add to formula sheet, create a 2-minute concept recap, drill 5 similar problems.
Setup error: write variable definitions explicitly, underline constraints in the prompt, add unit checks to scratch work.
Arithmetic slip: round then correct, avoid stacking decimals, reduce fractions before computing.
Timing: implement hard cutoffs, mark and return, estimate early to test reasonableness.
Trap: identify the pattern, like "average of percentages vs percentage of averages," and add a one-line reminder to your sheet.

After two to three practice sets, look for patterns. If misreads cluster in Data Interpretation, add a pre-read step to note units, axes, and whether values are cumulative or per period. If algebraic slips spike on inequalities, mark "flip on negative" on your scratch at the start of the section until it is automatic.

This process takes discipline. It is the most reliable path to higher scores in fewer hours because it prevents re-learning the same fix every week.

Geometry and number properties traps you should expect

The GRE likes certain traps. Knowing them helps you avoid careless losses. Two trap families recur: visual misleads in geometry and overgeneralizations in number properties.

Geometry visual misleads:

Not to scale figures. The picture may look like a right angle or an isosceles triangle when the information does not guarantee it. Only use properties that the prompt or labels confirm.
Parallel lines implied but not stated. Without a parallel marker or an explicit claim, you cannot use alternate interior angle equality.
Hidden constraints. A common trick is to provide one side or angle and expect you to find a similar triangle or proportional sides that are not obvious until you extend a line or drop a perpendicular.

Number properties overgeneralizations:

Even and odd products. Many assume that even times anything is even, which is correct, but then forget about divisibility by 4 or 8, which requires more 2 factors.
Prime traps. 1 is not prime. 2 is the only even prime. If a question asks about primes in an interval, check endpoints and test small primes explicitly.
Absolute value equalities. From |x| = a, you get x = a or x = -a, but when inequalities appear, split careful cases with sign flips.

Example trap, average vs weighted average: You have two classes. Class A has 10 students with an average of 80. Class B has 30 students with an average of 90. What is the combined average?

Not the average of 80 and 90. Use weights: (10*80 + 30*90)/40 = (800 + 2700)/40 = 3500/40 = 87.5.

Example trap, percent of a percent: A sales tax of 8% is added after a discount of 20% off the list price. How much tax is paid on a 100 dollar item?

Discounted price is 80 dollars. Tax is 0.08*80 = 6.4. Not 8 dollars.

Avoiding these traps depends on slowing down the first 10 seconds of each problem just enough to define variables, note constraints, and preview a solution path. Then, accelerate through the algebra. That pattern turns what looks like a speed problem into a planning problem.

Data Interpretation step-by-step: from chart to answer

Data Interpretation sets are a common place to lose time and points. They reward a consistent approach. Use a five-step process:

Pre-scan the visuals. Note axes, units, whether the values are absolute or rates, and if they are per quarter or per year. Write down any conversions you will need.
Identify reusable computations. If multiple questions will ask for totals or averages across the same categories, compute once and circle it on your scratch page.
Estimate before you compute. If the chart bars are at about 50 and 70, the difference is about 20. If answer choices are 18, 20, 22, 24, your estimate directs you to a quick exact subtraction.
Avoid double counting. If one chart shows revenue per quarter and another shows annual costs, do not add costs four times.
Check for percent-of-what. Many traps switch denominators. If a question asks for percent increase from A to B, the denominator is A. If it asks what percent B is of A, the denominator is A. If it asks for percent point change in a rate, subtract the rates directly.

Example, multi-visual set: Suppose you have a bar chart of units sold per quarter for Products X and Y across two years, and a table of price per unit by product per year. A question asks: What is the percent increase in revenue for Product X from Year 1 to Year 2?

Pre-scan: Units are per quarter, price is per year. Revenue requires sum of units for X per year times that year's price.
Compute once: Sum Q1 to Q4 units for X in Year 1. Do the same for Year 2. Multiply each by its respective price. Note both revenues on scratch.
Percent increase: (Rev2 - Rev1)/Rev1 * 100%. Keep track of denominators.

If a follow-up asks which product had greater total revenue in Year 2, you already have totals for X. Compute Y once for that year and compare. This reuse of work is the main time saver in Data Interpretation.

Putting it all together: test-day execution for Quant

On test day, Quant is one piece of a larger performance. You want consistency more than peak heroics. Build a simple routine and stick with it. Warm up, execute the timing plan, apply decision rules, and recover quickly from mistakes.

Pre-test warm-up: 15 minutes before your appointment, do five mental math review lines, three quick QC items, and one Data Interpretation scan. This primes your head for translation and estimation.
Section open: On your scratch sheet, write three reminders at the top: "flip on negative", "units check", and your pacing anchor, like "after Q6, 10 minutes left".
During the section: Apply triage. Harvest easy points first. Avoid confirmation bias by scanning all answer choices before committing on non-QC items. Estimate to sanity-check calculator results.
Between sections: Reset. Close your eyes, breathe, and clear any fixation on a previous miss. Write your three reminders again.

If you want a detailed test-day framework that coordinates Quant with Verbal pacing, break timing, and mental resets, use the GRE test-day strategy guide. Do at least two dry runs with this exact routine during your full-length GRE mock practice tests.

Balanced prep with Verbal and AWA

Although this guide zeroes in on Quant, score goals live across all sections. If you push Quant volume too hard at the expense of Verbal, fatigue and diminishing returns set in. A balanced plan gets more done in less time by alternating cognitive loads.

Pair algebra drills with reading comprehension sets. The symbol manipulation muscles and the inference muscles are different enough to limit interference.
Do geometry formula refreshers on days with vocabulary review, not heavy practice, to protect retention.
Keep AWA practice short but regular, so you do not lose writing fluency. A 20-minute argument outline twice a week is enough to maintain structure.

For structured materials and cross-section tactics, explore the GRE Verbal guide and the GRE AWA overview. Then combine them with your Quant plan using the GRE study plan templates.

Explore the silo

Worked examples: from setup to answer

Use these fully worked problems to practice the sequence: define, map, compute, check.

Problem 1, mixture ratio: You have a 20% saline solution and a 50% saline solution. How many liters of each should be mixed to obtain 10 liters of a 32% saline solution?

Define: Let x be liters of 20% solution, 10 - x be liters of 50%.
Map: Total salt from 20% is 0.2x, from 50% is 0.5(10 - x). Total salt target is 0.32*10 = 3.2.
Compute: 0.2x + 0.5(10 - x) = 3.2 gives 0.2x + 5 - 0.5x = 3.2, so -0.3x = -1.8, x = 6.
Check: 6 liters of 20%, 4 liters of 50%. Salt is 1.2 + 2.0 = 3.2, matches target.

Problem 2, quadratic word problem: The product of two consecutive positive integers is 156. What are the integers?

Define: Let n and n+1 be the integers. n(n+1) = 156.
Map: n^2 + n - 156 = 0. Solve by factoring or quadratic formula.
Compute: Factors of 156 near square root about 12 or 13. Try 12: 12*13 = 156. So n = 12.
Check: Integers are 12 and 13.

Problem 3, geometry with algebra: In a right triangle, the hypotenuse is 13 and one leg is 5. Find the length of the other leg and the area.

Map: a^2 + b^2 = 13^2 = 169. If one leg is 5, the other is sqrt(169 - 25) = sqrt(144) = 12.
Area: (1/2)*5*12 = 30.
Check: Recognize the 5-12-13 triangle pattern next time.

Problem 4, Data Interpretation percent change: A table shows that a company sold 1200 units in Year A and 1500 units in Year B. The average price per unit was 8 dollars in Year A and 7 dollars in Year B. What is the percent change in revenue from Year A to Year B?

Map: Revenue A = 1200*8 = 9600. Revenue B = 1500*7 = 10500.
Percent change: (10500 - 9600)/9600 * 100% = 900/9600 * 100% = 9.375%.
Check: Larger units, lower price, but units increased more, so revenue increase is plausible.

Problem 5, probability with combinations: From a standard deck of 52 cards, what is the probability of drawing a 5-card hand with exactly 2 aces?

Map: Number of ways to choose 2 aces from 4 is C(4,2) = 6. Number of ways to choose 3 non-aces from 48 is C(48,3). Total 5-card hands C(52,5).
Compute: Probability = [6 * C(48,3)] / C(52,5).
Check: No simplification is needed if answers are in combinatorial form. If numeric is required, compute or approximate with factorial cancellations.

These exemplars show that most problems collapse if you pick the right representation early. Practice the first 15 seconds of each problem as much as you practice the final algebraic push.

Formula pack: what to memorize and why it matters

A compact formula pack increases speed and confidence. It eliminates the micro-delays caused by searching memory mid-problem. Memorize, then rehearse until recall is instant.

Arithmetic and algebra:

Percent change: (new - old)/old * 100%
Compound interest: A = P(1 + r/n)^(nt)
Exponent rules: a^m * a^n = a^(m+n), a^m / a^n = a^(m-n), (a^m)^n = a^(mn)
Distance-rate-time: d = rt
Work: W = rt, combined rate 1/T = 1/a + 1/b
Quadratic formula: x = (-b ± sqrt(b^2 - 4ac))/(2a)

Geometry:

Triangle area: A = (1/2)bh
Pythagorean triples: 3-4-5, 5-12-13, 7-24-25, and multiples
Circle: circumference 2πr, area πr^2
Rectangle: area lw, perimeter 2(l + w)
Trapezoid area: A = (1/2)(b1 + b2)h
Coordinate slope: m = (y2 - y1)/(x2 - x1), distance sqrt((x2 - x1)^2 + (y2 - y1)^2)

Probability and counting:

Complement: P(A) = 1 - P(not A)
Combinations: C(n, r) = n!/[r!(n - r)!]
Permutations: P(n, r) = n!/(n - r)!

Data and statistics:

Mean: sum/n
Weighted average: (w1*x1 + w2*x2 + ...)/(w1 + w2 + ...)
Standard deviation intuition: larger spread from mean implies larger SD

Build your own sheet, then test recall by rewriting it from memory under a 3-minute limit. Any hesitation marks a drill topic.

When to guess, when to grind, and when to skip

Perfect pacing does not exist. You make real-time calls that impact your score. Learn to recognize when to guess, when a short grind is justified, and when to skip entirely.

Guess quickly when the value of information is low. If a QC item requires testing three or more cases and the decision is not close, guess D if the relationship plausibly varies or test one more case to confirm equality, then choose C. Do not sink 2 minutes to perfect a low-yield item at the start of a section.
Grind briefly when the point density is high. On the harder second section, some algebra or Data Interpretation items are worth 2 minutes because the payoff is consistency across the section. If you see a path and the arithmetic is stable, commit those 2 minutes after you have banked easy points.
Skip when constraint misreads or layered cases pile up. Some combinatorics questions hide multiple cases. If you cannot enumerate cases cleanly in the first 30 seconds, mark and return. Many test takers recover a full point by not locking onto a single low-yield knot.

Build your instincts by annotating expected-time vs actual-time in your review. If you consistently overspend on geometry constructions, impose a 90-second pre-commit checkpoint: either you see similar triangles or you postpone. If you mis-time Data Interpretation, pre-commit 45 seconds to read, then solve, not solve-then-read.

Making your work visible: scratch techniques that actually help

Scratch paper is your external memory. It must be legible at a glance and structured so you can return to a marked question and restart in seconds. A few simple conventions go a long way.

Divide the page into two columns. Left column for question numbers and small notes, right column for actual algebra and calculations.
Box the quantity you are solving for and write a one-line plan before you compute, like "solve for t using d = rt" or "use mixture balance".
Circle intermediate totals in Data Interpretation sets so you can reuse them.
Cross out answer choices in the booklet interface notes as you eliminate them. For multiple-answer items, list candidate letters after quick tests.

For QC, adopt a test-values grid:

x: -1 | 0 | 1 | 2 | large | fraction (1/2)
QA:    |   |   |   |       |
QB:    |   |   |   |       |
Rel:   |   |   |   |       |

Fill with quick evaluations. If the relationship changes, D is likely. This grid prevents you from redoing the same test values twice and keeps the domain in view.

Scratch discipline reduces careless errors and speeds re-entry when you return to a marked item with 3 minutes to go. It is also your main defense against trap answers that exploit mental arithmetic slips.

Final week checklist and day-before rhythm

Your last seven days are about consolidation, not expansion. You want freshness, not fatigue. Use a light-but-focused plan that keeps your skills peaked.

Seven days out: Take a full-length test. Analyze, fix two recurring issues. Refresh your formula sheet twice.
Six to four days out: Two 12-question Quant sets per day, timed at 21 minutes, plus one short Verbal set to keep balance. Daily 10-minute mental math drills.
Three days out: One more full-length with exact test-day routine. Focus review on Data Interpretation reads and QC habits.
Two days out: Light work only. One 12-question set in the morning, formula sheet rewrite, and one algebra mini-drill. Stop by mid-afternoon.
Day before: No full tests. Do a 20-minute warm-up early, then rest. Prepare documents, route, and snacks. Sleep on time.

Use this rhythm to arrive at the test center with calm focus. If you want a structured daily schedule that connects these beats to your specific score target, the week-by-week GRE study plan templates can be adapted quickly. If you prefer coaching and accountability to stay on tempo, consider the career-aligned GRE mentorship.

FAQ: GRE Quant preparation

Q: How much math do I need to memorize for GRE Quant? A: You need a compact set of formulas for percent, exponents, triangles, circles, coordinate geometry, and combinations. Memorize the rules, then practice applying them until recall is instant. A short formula pack you can rewrite from memory in under 3 minutes is the goal. For percent and ratio, you also want mental anchors so you can estimate quickly.

Q: What is the most efficient way to improve from Q158 to Q165+? A: Fix a few high-frequency weaknesses, usually algebraic translation, Data Interpretation reads, and arithmetic slips, then add timing discipline. Do topic drills untimed to perfect method, then timed mixed sets to enforce triage and pacing. Use two to three full-length mocks to secure a harder second section and practice executing on it. The GRE score improvement framework outlines how to sequence these steps.

Q: Should I use the calculator on GRE Quant? A: Use it selectively. It is helpful for awkward divisions, square roots of non-perfect squares, and when precision is required. Pre-simplify expressions first, and verify results with estimation to avoid keystroke errors. Many multiplications and fraction reductions are faster mentally.

Q: How many Data Interpretation questions are on the test, and how should I handle them? A: Each Quant section usually includes a Data Interpretation set with two to three questions. Pre-scan visuals for units and axes, compute reusable totals once, estimate before exact arithmetic, and watch for denominator traps. Practice one set in every mixed drill to keep the rhythm.

Q: What is the role of Quantitative Comparison practice in high scores? A: QC builds number sense and tests your ability to see structure fast. It is a high-leverage format because small mistakes are common. Practice a standard routine: simplify, test boundary and simple values, respect constraints, and try to disprove equality. Consistent QC accuracy is correlated with scores above Q165.

Q: How should I balance Quant with Verbal and AWA during prep? A: Alternate heavy Quant days with lighter Verbal or AWA to prevent fatigue and improve retention. Pair algebra with reading comprehension, and do geometry refreshers on lighter Verbal days. Use the GRE Verbal guide, GRE AWA overview, and GRE study plan templates to structure that balance.

Q: What practice tests should I take, and how many? A: Take two to four full-length mock tests under realistic conditions to calibrate pacing and build endurance. Analyze each test with an error log that targets causes, not just wrong answers. Schedule your mocks using the full-length GRE mock practice tests, and space them about a week apart in the final month.

Q: Is a coaching program worth it for Quant improvement? A: If you need accountability, tailored analytics, or application-aligned score targets, coaching can shorten the path. A structured program ties daily work to your goal and keeps you from plateauing. If this aligns with your needs, explore the career-aligned GRE mentorship program.