PSAT 10 Math Adaptive Module Strategy & Pacing Guide

What You Need to Know

The adaptive setup (what it means for your strategy)

• The PSAT 10 Math section is module-adaptive: you’ll get two Math modules, and your performance on Module $1$ influences the difficulty of Module $2$.
• You can move freely among questions within a module (skip, flag, return), but you cannot go back to Module $1$ after you finish it.
• There is no penalty for wrong answers, so a strategic guess is always better than leaving something blank.

Why pacing matters more on an adaptive test

• Module $1$ is leverage: avoid careless misses because it affects the “ceiling” of Module $2$.
• Module $2$ is where time pressure spikes (more multi-step items if you did well). Your pacing plan must assume a few time-sinks.

The core rule to live by

Treat Module $1$ as accuracy-first with controlled pacing, and treat Module $2$ as triage-first with smart time banking.

Key timing facts you should anchor to

• Total Math time: $70\,\text{min}$ for $44$ questions.
• Per module: $35\,\text{min}$ for $22$ questions.
• Average pace: $\frac{70}{44} \approx 1.59\,\text{min/question} \approx 95\,\text{s/question}$.

You won’t spend $95$ seconds on every question; you’ll bank time on easy ones to “pay” for the hard ones.

Step-by-Step Breakdown

The “Two-Pass + Checkpoints” method (the highest-yield pacing system)

Pass $1$ (fast wins + time banking)

1. Start each question with a $10$-second scan: identify if it’s (a) direct, (b) medium, or (c) time-sink.
2. Solve direct questions immediately (aim $30$–$75$ seconds).
3. If you don’t see a clean path by ~$30$ seconds, flag and skip.
4. Keep moving until you’ve collected the easy/medium points.

Decision rule:

• If you can write a plan in one sentence (e.g., “factor, set equal to $0$, pick roots”), do it.
• If you’re still “translating” the problem after $30$–$40$ seconds, skip.

Pass $2$ (return to flagged questions in priority order)

5. Return to flagged questions and do them easiest-first (not in order).
6. For each flagged question, give it a hard cap of ~$2.5$ minutes.
7. If it’s still not cracking, switch strategies (see “Quick Tricks”) or guess strategically and move on.

Endgame (last $2$–$3$ minutes)

8. Fill every blank.
9. Re-check:
   • student-produced responses (sign, decimal, fraction form)
   • “EXCEPT/NOT” wording
   • unit conversions

Module-specific game plan

Module $1$: “High accuracy, no hero moves”

1. Use Two-Pass.
2. Be extra careful on “easy-looking” algebra/arithmetic (these are where careless errors happen).
3. Do not spend $4$ minutes on one hard question; that’s how you lose points you could’ve gotten later.

Module $2$: “Triage + time discipline”

1. Expect more questions that require setup (modeling, systems, functions, geometry with constraints).
2. Skip earlier if needed; hard questions can appear anywhere.
3. Protect time for the last $5$ questions (they’re often not freebies).

Built-in checkpoint pacing (simple and effective)

Use these checkpoints to stay honest. If you’re behind, you must skip more aggressively.

Per module ($35\,\text{min}$ for $22$ questions):

• After $5$ questions: about $8\,\text{min}$ used
• After $11$ questions: about $17.5\,\text{min}$ used
• After $16$ questions: about $25.5\,\text{min}$ used
• After $22$ questions: about $35\,\text{min}$ used

Practical version (easier to remember):

• Q $11$ by about $18\,\text{min}$
• Q $16$ by about $26\,\text{min}$
• Finish with $2$–$3\,\text{min}$ to review

If you hit Q $11$ at $22\,\text{min}$, you are behind: switch to “fast solve or flag” mode immediately.

Key Formulas, Rules & Facts

Timing rules (your pacing “formula sheet”)

Adaptive-test rules of thumb (what changes vs non-adaptive)

“Method selection” rules (to solve faster)

Answer-format facts (where points get lost)

• Multiple choice: choose one option.
• Student-produced response: you must enter the value correctly.
  • If a question asks for $\frac{a}{b}$, don’t enter a rounded decimal unless allowed.
  • If a question asks for a positive value, don’t enter a negative root.

Examples & Applications

Example $1$: You’re behind at the halfway checkpoint

• You’re on Q $11$ and the timer shows $22\,\text{min}$ used (you wanted about $18\,\text{min}$).
• You’re behind by about $4\,\text{min}$.

Fix (what you do next):

1. For the next $6$ questions, enforce a strict cap of about $60$–$75$ seconds each.
2. Anything not cracking fast: flag and move.
3. You’re trying to “buy back” $4\,\text{min}$ before the final block.

Key insight: You don’t recover time by solving faster on hard questions; you recover time by skipping earlier and returning later.

Example $2$: A quadratic that won’t factor quickly

You see something like:

$2x^2 - 7x - 4 = 0$

Fast decision:

• If factoring isn’t obvious in ~$20$ seconds, graph.

Desmos approach:

1. Graph $y = 2x^2 - 7x - 4$.
2. Read the $x$-intercepts (solutions).
3. If the problem needs an exact form and the intercepts look non-integer, you may need algebra; otherwise, use the intercepts directly if the question allows.

Key insight: On digital math, graphing is a legitimate speed tool when algebra is messy.

Example $3$: System of equations with ugly numbers

$3x + 4y = 19$

$7x - 2y = 5$

Two fast routes:

• Elimination (paper): multiply the second equation by $2$ to eliminate $y$ quickly.
• Desmos (often fastest): graph both lines and read the intersection.

Key insight: When arithmetic looks annoying, Desmos reduces error risk and saves time.

Example $4$: When to guess (strategically) near the end

You have $90\,\text{s}$ left and $2$ questions blank.

Best play:

1. Put an answer in both immediately.
2. If one is multiple choice, eliminate obviously wrong options (sign, size, units) and guess from the remaining.
3. If one is student-produced, estimate (order of magnitude) to avoid absurd values.

Key insight: A rushed “attempt” that produces no answer is worse than a fast, reasoned guess.

Common Mistakes & Traps

1. Burning $4$+ minutes early

   • What happens: you get stubborn on one hard question in Module $1$.
   • Why it’s bad: you lose $2$–$3$ easy/medium questions later.
   • Fix: enforce the ~$2.5$-minute hard cap and move on.

2. Rushing Module $1$ because it feels easy

   • What happens: you speed-run and make silly errors.
   • Why it’s bad: Module $1$ mistakes can reduce how hard (and high-scoring) Module $2$ becomes.
   • Fix: still bank time, but do a micro-check: arithmetic, signs, and what the question actually asked.

3. Not using the flag/return system

   • What happens: you work strictly in order.
   • Why it’s bad: you waste time on a time-sink while easier points sit later.
   • Fix: Two-Pass every module: solve what’s solvable fast first.

4. Forgetting you can’t return after the module ends

   • What happens: you click through at the end thinking you can revisit.
   • Why it’s bad: you lock in blanks/mistakes permanently.
   • Fix: reserve $2$–$3\,\text{min}$ to confirm every question has an answer before finishing a module.

5. Calculator/Desmos overuse on simple arithmetic

   • What happens: you type everything, lose time, mis-key.
   • Why it’s bad: speed drops and errors sneak in.
   • Fix: do mental math when it’s genuinely quick; use calculator for messy computation or verification.

6. Answer-format errors on student-produced responses

   • What happens: you enter $0.33$ instead of $\frac{1}{3}$, or you enter $-2$ when it asks for a positive solution.
   • Why it’s bad: fully correct work becomes a wrong answer.
   • Fix: final check: “form + sign + units.”

7. Misreading “EXCEPT,” “NOT,” “NO solution,” or “all real values”

   • What happens: you solve correctly but choose the opposite.
   • Why it’s bad: these are high-frequency trap wordings.
   • Fix: circle/underline the negation word before solving.

8. No estimation/sanity check

   • What happens: you accept an answer that’s wildly too big/small or wrong sign.
   • Why it’s bad: many PSAT math questions have built-in reasonableness cues.
   • Fix: quick check: expected sign, approximate size, unit consistency.

Memory Aids & Quick Tricks

Quick Review Checklist

• You have $2$ math modules; Module $1$ performance influences Module $2$ difficulty.
• You can’t return to Module $1$ after finishing it.
• Pace per module: $35\,\text{min}$ for $22$ questions (about $95$ seconds each on average).
• Use Two-Pass:
  • Pass $1$: solve easy/medium, flag time-sinks
  • Pass $2$: return easiest flagged first, cap time, guess if needed
• Checkpoints (per module): around Q $11$ by $18\,\text{min}$; Q $16$ by $26\,\text{min}$.
• No blanks: guessing beats leaving empty.
• End-of-module review: student-produced response format, signs, “EXCEPT/NOT,” units.
• Use Desmos strategically: graph messy quadratics/systems to save time and reduce errors.

You’ve got this: stay calm, keep moving, and let your pacing plan do the heavy lifting.