The SAT Math pacing system: pre-decide hand / Desmos / skip before writing, cap directionless work at sixty seconds, mark and run a planned return sweep, check pace at Q7, Q11, Q15 and Q18, and classify every miss into one of six error categories.
Subject: SAT Prep · 76 slides · applied lesson
Open the interactive version of this deck · Homework for this lesson
Title
SAT Math · Pacing
The single fastest way to recover free points on test day
Objectives
This is a behaviour deck, not a maths deck. Nothing here asks you to learn a new formula.
The goal: never let time be the reason you miss a question.
Section
Section 1
Warm-up
Think back to your most recent timed math section. Answer from memory, not from the score report.
Discussion prompt
Where were you when time was called — did you reach the last question? And roughly how long did you spend on the single worst question of the section?
Hint: If you genuinely cannot remember, that is itself the finding — it means you had no clock awareness at all.
Answer:
Almost every student underestimates the worst question by half. A question that felt like ninety seconds is usually three to four minutes.
That single question is not one lost point. It is the questions after it that you never read.
If you finished with time to spare, the rule still applies — it is what created the spare time, and the next deck is about spending it.
Concept
A digital SAT math module is 22 questions in 35 minutes.
| quantity | value |
|---|---|
| questions in the module | 22 |
| minutes in the module | 35 |
| seconds available | 2,100 |
| average seconds per question | about 95 |
Ninety-five seconds is the average, not the allowance. Some questions take twenty. That surplus is the whole game.
Estimation
A student stops answering at Q18 when time is called. Four questions are left blank — not wrong, blank.
Predict first
If those four were roughly average-difficulty questions, about how many raw points did the clock alone cost?
Correct: About 4 raw points — every unanswered question is a guaranteed zero.
Why: Four blanks is four raw points gone before difficulty is even considered. Unlike a wrong answer, a blank has no chance of being right: there is no wrong-answer penalty on the SAT, so a blank is strictly worse than a guess. Run the same count on your own most recent section — the number of questions you never reached is the score the clock is holding back, and it is usually larger than any single topic you could study.
Intuition
Students treat a hard question as something to defeat. The test does not award style points for persistence.
Every extra second on question 12 is a second taken from question 19 — and question 19 might have been a twenty-second question.
opportunity cost — What you gave up to do the thing you did. On a timed section, the cost of a long question is measured in the questions you never reached, not in the minutes on the clock.
Real world
You have run this exact algorithm before, without being taught it.
Discussion prompt
Think about a supermarket checkout: you pick a queue, and after a moment you notice it is not moving. What do you actually do, and what is the rule you are following without saying it out loud?
Answer:
You switch queues — and you switch on evidence (the queue is not moving), not on feeling (I have already waited, so I should stay).
The trap in both cases has a name: sunk cost. The forty seconds you already spent are gone whether you stay or leave. They are not a reason to stay.
Concept
Here it is. Everything else in this deck is an elaboration of this one line.
The 60-Second Rule — If you have no clear path after 60 seconds — mark it, skip forward, and return.
Read it again and notice what it does not say. It does not say 'if the question is hard'. It does not say 'if you are stuck'. It says no clear path.
Definition probe
The rule turns on one phrase. Sort each situation by whether you have a clear path.
Sort into buckets
At the 60-second mark, which of these is a clear path?
Explain it to yourself
Before we break the rule into steps, put it in your own words.
Discussion prompt
Write the 60-second rule as you would explain it to a friend who has never heard it — in one sentence, without using the word 'skip'.
Answer:
A good version names the trigger and the action: 'If a minute goes by and I still cannot say what my next move is, I flag the question and go to the next one.'
If your sentence contains the words 'hard' or 'stuck', rewrite it. The trigger is no clear path, which is measurable. 'Hard' is not.
Concept
The rule is a decision system with three moves. They are numbered because the order matters.
Applied to every question, every time. A rule with exceptions is not a rule, it is a preference.
Ranking
Order matters more than it looks. Drag these into sequence.
Put in order
Why: Pre-deciding comes first because it is the only step that prevents time waste rather than limiting it. If you start the clock before choosing a method, you spend the first twenty seconds of your minute deciding — which is exactly the twenty seconds you needed at the end. The sweep is last by definition: it cannot start until you have reached the end of the module.
Section
Section 2
Concept
Before your pencil moves, before you type anything, you answer one question: how am I doing this one?
This costs about one second and prevents most of the time you currently lose.
Sorting
Read each question stem. Do not solve anything — just choose the door.
Sort into buckets
Hand, Desmos, or skip on sight?
Intuition
Without a pre-decision you do not skip the deciding — you just do it mid-question, with half an equation already on the page.
That is the expensive version: you have sunk effort into a method before asking whether it was the right method, so now switching feels like waste.
Deciding costs the same second either way. Deciding first is the only version that can change what you do.
Worked example
Question: solve for x.
\[ 3(x - 4) = 2x + 5 \]
Pre-decide: hand calc
Why: Two moves visible from here — distribute, then collect x on one side. No graph would be faster than that, and nothing here is messy enough to justify typing.
Distribute the 3 across the parenthesis
Why: This clears the only structural obstacle; after it, both sides are plain linear expressions.
\[ 3x - 12 = 2x + 5 \]
Subtract 2x from both sides, then add 12 to both sides
Why: Collecting the variable on the left and the constants on the right isolates x in one pass.
\[ x = 17 \]
Verify: substitute 17 into the original equation
Why: Left side: 3(17 - 4) = 3(13) = 39. Right side: 2(17) + 5 = 39. Both sides agree, so 17 is correct.
Elapsed: about thirty seconds. This is a question that funds the hard ones.
Worked example
Question: for what value of k does this equation have exactly one real solution?
\[ x^2 + kx + 9 = 0 \]
Pre-decide: Desmos
Why: The phrase 'exactly one real solution' is a Desmos flag. By hand it means setting a discriminant to zero and solving; in Desmos it means adding a slider and watching the parabola touch the axis.
Type the equation with a slider on k, then drag k
Why: Desmos offers to add the slider automatically. Drag until the parabola is tangent to the x-axis — the point where two intersections collapse into one.
Read both values off the slider
Why: Tangency happens twice, symmetrically, because k is the coefficient that shifts the vertex sideways.
\[ k = 6 \quad \text{or} \quad k = -6 \]
Verify: check the discriminant is zero
Why: With k = 6: 6^2 - 4(1)(9) = 36 - 36 = 0, so there is exactly one real root. The same arithmetic works for k = -6, confirming both.
Elapsed: about forty seconds, and none of it spent on sign errors.
Trap
Q12. You read it once and immediately start writing algebra.
Start expanding by hand because that is what you always do
Why: No decision was made — the method was a habit, not a choice.
Forty seconds in, the fractions get ugly and you think 'maybe Desmos'
Why: Now switching means abandoning visible work, which is exactly when sunk cost bites hardest.
Push on by hand to avoid 'wasting' the forty seconds
Why: The forty seconds are already spent. They are not recoverable by spending eighty more.
Result: 2m 10s on one question, answer still wrong.
Q12. You read it once and spend one second on the door.
Pre-decide out loud: 'intersections — Desmos'
Why: The decision is made while the cost of making it is one second, before any work exists to protect.
Type both sides into Desmos and read the intersection
Why: The chosen method matches the question's shape, so the work converges instead of sprawling.
Answer, then move on
Why: No mid-question method change, because the method was chosen when changing was free.
Result: 45s, answer correct.
Discrimination
The single most common pre-decision error is reaching for Desmos on things it does not speed up.
Sort into buckets
Which tool is actually faster here?
Step zero
You will say this to yourself 22 times per module, so it has to be short.
Discussion prompt
Write the exact words you will say to yourself in the first second of every question. Maximum six words.
Answer:
Strong versions are almost rude in their brevity: 'Hand, Desmos, or skip?' — or just 'Which door?'
If your script is a sentence, it is too long. You need it to fit in the gap between finishing the last question and starting this one.
Section
Section 3
Concept
Sixty seconds is not how long a question should take. It is how long you are allowed to spend without a clear path.
Most questions you answer will finish well under it. The rule only ever fires on the ones that were going to hurt you.
the 60-second clock — A cap on directionless work. It starts when you start working and it only matters if, when it runs out, you still cannot name your next move.
Prediction
You have to recognise the mark without looking, because looking costs time too.
Predict first
Without counting, how long do you think a minute of hard concentration feels like?
Correct: Much shorter — deep concentration compresses time, so 60 real seconds usually feels like 30 to 40.
Why: This is why 'I only spent a minute on it' is almost always false. Absorbed in a problem, your internal clock runs slow, and a question that felt like a minute was frequently two and a half. The fix is not to trust the feeling: anchor to the four windows on the next slide, which are things you can observe yourself doing rather than durations you have to sense.
Concept
Break the minute into four observable stages. You do not time them — you notice which one you are in.
| window | stage | what you are doing |
|---|---|---|
| 0 to 10 s | Read | Read the problem once, completely, including the last line |
| 10 to 20 s | Pre-decide | Hand, Desmos, or skip |
| 20 to 50 s | Work | Execute the chosen method |
| 50 to 60 s | Check | Confirm the answer, or confirm you have no path |
| past 60 s | SKIP | No clear path — mark and move |
If you are still in Read when you feel like you should be finishing, that is the signal — not the clock.
Ranking
These are the observable stages inside the minute.
Put in order
Why: Reading comes before deciding because you cannot choose a tool for a question you have not finished reading — and the most common cause of a wrong pre-decision is deciding off the first clause. Checking comes last and is never skipped: even when the answer is wrong, the check tells you that it is wrong while you are still on the question and can flag it honestly.
Worked example
Question: a 40 mL solution is 25% acid. How many mL of pure acid must be added so the result is 40% acid?
0 to 10 s — Read the whole thing, including 'pure acid'
Why: 'Pure acid' is 100% acid, which is the fact the setup hinges on. Reading only the first sentence loses it.
10 to 20 s — Pre-decide: hand calc
Why: One equation with one unknown. Typing it into Desmos would take longer than solving it.
20 to 50 s — Write the setup before any arithmetic
Why: Acid before plus acid added, over total volume after, equals the target concentration. Naming the parts first is what stops the classic error of adding percentages.
\[ \frac{0.25(40) + x}{40 + x} = 0.40 \]
Still in Work — clear the fraction and solve
Why: Multiplying both sides by (40 + x) removes the only obstacle: 10 + x = 16 + 0.4x, so 0.6x = 6.
\[ x = 10 \]
Verify: 50 to 60 s — substitute back
Why: Acid after: 0.25(40) + 10 = 20 mL. Volume after: 40 + 10 = 50 mL. And 20/50 = 0.40, which is the 40% asked for.
Finished inside the minute — and the check happened on the question, not in a panicked sweep at the end.
Trap
Sixty seconds have passed. You have half a page of work and a feeling.
Think: 'I'm almost there, one more line'
Why: 'Almost there' is a feeling generated by effort already spent, not by evidence about how much is left.
Spend another 40 seconds. Think it again.
Why: The feeling regenerates every time, because it is caused by the sunk effort, which only grows.
Arrive at 2m 30s with no answer and no time
Why: Three later questions are now unread, and each was worth exactly as much as this one.
Sixty seconds have passed. You have half a page of work and a feeling.
Ask the only question that matters: 'can I name my next move?'
Why: This replaces a feeling with a test you can pass or fail in two seconds.
No — so mark it and go to the next question
Why: The half page of work stays on the page. It is still there when you return, and it will be worth more with fresh eyes.
Return at the end and finish it in 30 seconds
Why: Returning to your own written setup is far faster than starting over, which is why marking beats erasing.
Counterexample
A rule you cannot argue against is a rule you will not apply under pressure. So argue against it.
Discussion prompt
Describe a specific situation where continuing past the 60-second mark is genuinely the right call. Be precise about what makes it different.
Answer:
The legitimate case: you have a clear path and are simply mid-execution — the last line of arithmetic, the final substitution. The rule was never about the clock alone; it fires on no clear path at 60 seconds.
The other legitimate case: it is the last question and there is nothing to move on to. The rule exists to protect later questions; with none left, it has nothing to protect.
Notice what is not on this list: 'it is worth more points' (all questions are worth the same), and 'I understand it, I just cannot get it out'.
Commit first
You are 58 seconds into Q9. You have an equation written down but you cannot see how to isolate the variable, and the numbers are getting worse.
Predict first
What does the rule say to do at 60 seconds?
Correct: Mark it and go to Q10 — an equation you cannot advance is not a clear path.
Why: Having written something is not the same as having a next move. The test is 'can I name the next action', and 'isolate the variable somehow' is not an action. Do not erase: the written setup is what makes the return visit fast. Do not guess-and-abandon either — you will have time to come back, and a considered answer beats a random one. Note how confident you were: confident-and-wrong here is the exact habit costing you the four blank questions.
Cost model
Annotate the budget line. The numbers are from a real 35-minute module.
Annotate
On: \( 2100 \text{ s} \;=\; 22 \times 95 \text{ s} \)
Section
Section 4
Concept
The digital SAT has a Mark for Review flag on every question, and a Review page listing all of them.
The flag is the whole mechanism. An unflagged skip is a question you have lost, not a question you have deferred.
Intuition
Skipping feels like conceding the point. It is the opposite: it is the only move that keeps the point available.
A question you left at 60 seconds is a question you spent 60 seconds loading into your head. When you come back, that setup is still there and the fresh look often lands in seconds.
The thing you are giving up is not the question. It is the grinding.
Ranking
The sweep is a procedure, not an impulse. Put its moves in order.
Put in order
Why: Guessing comes first, not last — it is the step that protects you if time is called early, and it costs about five seconds for all of them. Then triage: questions where a setup already exists are the cheapest points on the page, so they come before the ones you never started. Students who invert this order run out of time mid-sweep and leave actual blanks behind.
Trap
Q7 is going nowhere at 60 seconds.
Move to Q8 without flagging
Why: The decision to return exists only in your head, where it competes with 15 more questions.
Reach the end of the module with 4 minutes left
Why: Now you must reconstruct which questions you skipped — by scrolling and re-reading.
Spend 2 of the 4 minutes finding them
Why: Half the sweep is spent on search, which teaches you nothing and answers nothing.
Two of four recovered minutes spent on navigation.
Q7 is going nowhere at 60 seconds.
Tap Mark for Review, then go to Q8
Why: One tap converts a vague intention into a list the test itself maintains for you.
Reach the end with 4 minutes left and open the Review page
Why: Every flag is listed. Search time is zero.
Spend all 4 minutes on actual mathematics
Why: The recovered time goes into answers instead of navigation.
Four of four recovered minutes spent on questions.
Worked example
You reach the end of the module with 4 minutes left. Three questions are flagged: Q7, Q13, Q19.
First 10 seconds: put a plausible answer on all three
Why: Blanks are guaranteed zeros. This step alone converts three certain misses into three chances, and it survives the clock being called early.
Q13 first — you had already written the setup
Why: A written setup is the cheapest point on the page. Restarting cold is what makes the other two expensive.
Q13 was the geometry one: a square with the same area as a circle of radius 6.
\[ A = \pi r^2 = \pi (6)^2 = 36\pi \]
The square has the same area, so its side is the square root of that area
Why: Same area is the bridge between the two shapes — it is why the circle formula is allowed to determine the square.
\[ s = \sqrt{36\pi} = 6\sqrt{\pi} \approx 10.63 \]
Verify: square the answer and compare to the circle's area
Why: 10.63 squared is about 113.0, and 36 pi is about 113.1. They agree to rounding, so the side length is right.
Elapsed on Q13: 35 seconds, because the setup was already on the page. Two questions and three minutes still left.
Elimination
Four minutes left, four flags. Only one order is right.
Eliminate the wrong options
You have flagged Q3, Q9, Q13 and Q20. Which do you open first?
Survives elimination: b
Why: Sweep order is by distance to an answer, never by question number or difficulty. The question with a setup already written is nearly free, and finishing it banks a point that funds the time you then spend on the genuinely hard ones. Every question on the SAT is worth exactly one raw point, so the only sensible strategy is to buy the cheapest points first.
Explain it
You understand a procedure when you can defend its counter-intuitive step.
Discussion prompt
A friend says: 'Guessing on all the flagged questions first is a waste of time — I'll answer them properly in a minute anyway.' What do you say back?
Answer:
The guess costs about five seconds for all of them and it is insurance: it is what you keep if time is called at minute two of a four-minute sweep.
It also costs nothing later — you overwrite the guess when you solve the question properly. There is no downside to hold against the upside.
This is only true because the SAT has no wrong-answer penalty. On a test that penalised guessing, the advice would be different.
Section
Section 5
Concept
The 60-second rule keeps single questions from running away. Checkpoints keep the module from running away.
| checkpoint | time used | time left | note |
|---|---|---|---|
| after Q4 | 6 min | 29 min | settling in — do not be early here |
| after Q7 | 11 min | 24 min | first real checkpoint |
| after Q11 | 17 min | 18 min | halfway on both clocks |
| after Q15 | 24 min | 11 min | the squeeze starts |
| after Q18 | 29 min | 6 min | return sweep begins now |
Four checks in 35 minutes. Not one per question — that is its own kind of time waste.
Matching
These come from 22 questions in 35 minutes, about 95 seconds each.
Match the pairs
Why: Each question is worth about 95 seconds of the 2100-second module, so the time used after question N is roughly 95N seconds. After Q11 you are halfway through the questions and halfway through the clock, which is the checkpoint worth memorising if you only memorise one. The others are there so you catch a drift early, while a single skip can still fix it.
Estimation
You glance up after finishing Q11 and the timer reads 14:00 remaining.
Predict first
How far behind pace are you, and how many questions of slack does that represent?
Correct: About 4 minutes behind — you should have about 18 minutes left after Q11, so you are 2 to 3 questions of time short.
Why: After Q11 the pace target is about 18 minutes remaining. At 14:00 you are 4 minutes light, and at roughly 95 seconds a question that is about 2.5 questions' worth of time. The recovery is not to speed up on every remaining question — that is how accuracy collapses. It is to skip the next two borderline questions on sight, which returns the deficit in one move and leaves the rest of your pace intact.
Worked example
Situation: end of Q11, timer shows 14:00. Eleven questions left.
Compute the real budget rather than guessing at it
Why: 14 minutes is 840 seconds across 11 questions. Knowing the actual number stops you from either panicking or coasting.
\[ \frac{840}{11} \approx 76 \text{ seconds per question} \]
Compare to the 95 seconds you had been getting
Why: You need to move about 20% faster. That is not a speed you can grind out — it has to come from not doing something.
Skip the next two questions that are long rather than hard
Why: Two skipped table-and-chart questions return roughly three minutes to the pool, which restores the budget to about 95 seconds for everything else.
Verify: recompute the budget after the two skips
Why: Nine questions left with about 13 minutes on the clock gives 780/9, roughly 87 seconds each — close enough to normal pace to keep your accuracy.
The deficit was fixed by two decisions, not by rushing twenty questions.
Trap
You have been burned by pacing, so you resolve to watch the clock.
Glance at the timer after every question
Why: Each glance costs two seconds and, worse, breaks the thread you were holding on the next question.
Twenty-two glances across the module
Why: That is roughly 45 seconds of pure looking, plus the re-reading each interruption causes.
Start doing arithmetic on the timer mid-question
Why: Now you are pacing instead of solving, and the anxiety of being behind makes you rush the question in front of you.
You have been burned by pacing, so you resolve to watch the clock.
Check at four fixed points only: Q7, Q11, Q15, Q18
Why: Four checks cost about eight seconds total and each one lands where a correction is still cheap.
At each check, make one decision and then stop thinking about time
Why: On pace: continue. Behind: skip the next borderline question. That is the entire decision tree.
Between checkpoints, the only clock is the 60-second rule
Why: Per-question discipline handles the small scale; checkpoints handle the large one. Neither needs the timer in your peripheral vision.
Edge cases
A rule is only understood at its edges.
Discussion prompt
Suppose the module were 22 questions in 20 minutes instead of 35 — about 55 seconds a question. Does the 60-second rule still work? What would you change, and what would you keep?
Answer:
Keep: pre-deciding. It gets more valuable as time shrinks, because a wrong method is now unaffordable.
Change: the cap. At 55 seconds average, a 60-second cap on directionless work is no longer a cap — it is the whole budget. You would drop to about 35 seconds.
The general form is what to remember: the cap is roughly a third to a half of the average per-question time. On the real 35-minute module that is 60 seconds; the number is derived, not magic.
Section
Section 6
Two truths and a lie
Four claims about pacing. Two are true, two are the beliefs that cost you the section.
Sort into buckets
Sort each claim.
Error analysis
A typical attempt at the mixture question. Every line is defensible; the sequence is not.
Annotate
On: \( \frac{0.25(40) + x}{40 + x} = 0.40 \;\Rightarrow\; 0.25(40) + x = 0.40 \)
Concept
The most expensive mistake, because it feels like diligence.
the fix — 'Almost there' is a feeling, not a fact. If you do not have the answer, you are not almost there — replace the feeling with the test: can I name my next move?
Drill this by saying the test out loud during practice. It stops being a thought and becomes a reflex.
Concept
You intended to return. The intention did not survive eleven more questions.
the fix — Always tap Mark for Review before you move. A visual flag turns a hope into a list — and the Review page then does the remembering for you.
Concept
You start writing because writing feels like progress. Then the method turns out to be wrong.
the fix — One second of deciding before the question saves thirty seconds inside it — and, more importantly, it is the only second where switching methods is free.
Concept
You reach the end, see 3 minutes, and start thrashing between flags.
the fix — Plan the sweep before the module starts. 'I will guess on everything flagged, then take the ones with setups first' is a strategy. 'I'll come back to it' is a gamble.
Comparison
The four mistakes and their fixes. Two cells are blank — fill them in from memory.
Comparison matrix
| mistake | what it feels like | the fix |
|---|---|---|
| Pushing past 60s | Diligence | Ask 'can I name my next move?' — if not, flag it |
| Skipping without marking | Efficiency | Tap Mark for Review every single time |
| Not pre-deciding | Momentum | One second: hand, Desmos, or skip? |
| Panic sweep | Urgency | Guess on all flags first, then take the ones with setups |
Faded example
This is the script you run 22 times. Fill the blanks.
Fill in the blanks
Read the question completely. Say: hand, Desmos, or skip? Start working. At sixty seconds, ask: can I name my next move? If not — mark the question and move to the next one. At the end, guess on every flag, then return to the ones where I already have a setup.
Why: The script has exactly four decision points, which is why it fits in working memory under pressure. Notice that three of the four are about stopping — the hard part of pacing is never going faster, it is choosing not to continue. If you had to think about any blank for more than a second, that is the step that will fail on test day.
Section
Section 7
Concept
After every practice question you miss, you write down one word: the category.
A wrong answer teaches you nothing on its own. A wrong answer with a category tells you what to drill tomorrow.
error log — A running list of misses, each tagged with its category. The pattern in the log — not the individual misses — is what you study.
Concept
| category | what happened |
|---|---|
| Pacing | Ran out of time, never got to attempt it |
| Setup | Wrong equation or formula structure |
| Arithmetic | Right approach, wrong calculation |
| PSDA | Misread a table or graph, or wrong statistical logic |
| Geometry | Wrong formula or area relationship |
| Desmos opportunity | Could have used Desmos but did it by hand |
Six is deliberate. Fewer and the categories stop telling you anything; more and you will not use them.
Sorting
Each line is a real miss. Give it a category.
Sort into buckets
Which category does each miss belong to?
Matching
A category is only useful if it names a fix.
Match the pairs
Why: Every fix is a behaviour you can perform on the next question, not a topic you have to go and learn. That is the point of the taxonomy: it converts 'I got it wrong' into a specific thing to do differently in ninety seconds' time. Notice that three of the six fixes are about sequence — setup before arithmetic, question before data, formula before numbers.
Worked example
The question: a train covers 180 miles in 3 hours. At the same rate, how long for 300 miles?
Your answer was 900. The correct answer is 5 hours.
First: what was the intended relationship?
Why: Rate is 180/3 = 60 miles per hour, so time is distance divided by rate: 300/60 = 5 hours.
Now find where the work diverged
Why: The answer 900 is 300 x 3 — distance multiplied by time instead of divided by rate. The arithmetic in that multiplication is flawless.
Assign the category: Setup, not Arithmetic
Why: This matters. If you log it as Arithmetic you will drill computation, which was never the problem, and miss the same question again next week.
Verify the category by naming the fix and testing it
Why: The Setup fix is 'write the relationship before any numbers'. Writing 'time = distance / rate' first would have made the error impossible — so the category is correct.
Correct classification is what makes an error log worth keeping.
Trade off
Not all six cost the same. Fill in the blanks.
Comparison matrix
| category | cost per instance | how fast it is to fix |
|---|---|---|
| Pacing | 1 point, plus the questions after it | Fast — it is one rule, not a topic |
| Setup | 1 point, and it repeats across a whole topic | Slow — needs the habit of writing relationships first |
| Arithmetic | 1 point, isolated | Fast — verify in Desmos |
| Desmos opportunity | 0 points directly, but 60-90 seconds each time | Fast — it is a pre-decision |
Missing information
A student says: 'I got Q40 wrong. I think it was a careless mistake.'
Discussion prompt
You cannot assign a category from that. What is the minimum information you need, and why is 'careless mistake' not a category?
Answer:
You need the work itself — the written setup and the computation — plus how long it took. Without the work you cannot separate Setup from Arithmetic; without the time you cannot see a Pacing or Desmos-opportunity miss at all.
'Careless' is not a category because it names a feeling about the error rather than the error. Every one of the six categories can feel careless in the moment. The log only helps if the label points at a fix.
Section
Section 8
Pattern
This is the reusable recipe. It applies to every question in every module.
Eight steps. Six of them are decisions about what not to do.
Step zero
The next time you sit a timed set — six questions is enough to feel it — start here.
Discussion prompt
Before you look at question 1: say your plan out loud. What are the four checkpoints, and what is your pre-decision script?
Answer:
Checkpoints: Q7, Q11, Q15, Q18 — targets about 24, 18, 11 and 6 minutes remaining.
Script: 'Hand, Desmos, or skip?' — said before anything is written.
Track as you go: question number, pre-decision, did you hit 60 seconds, correct or not, and the error category if not.
Check
Answer from the rule, not from instinct.
Check your understanding
You are on question 14. Fifty-five seconds in, you have an equation written down, but the algebra keeps producing fractions you do not recognise and you cannot say what your next move is. What does the 60-second rule tell you to do at sixty seconds?
Answer: A
Why: The rule fires on 'no clear path', and being unable to name your next move is exactly that — having written an equation is not the same as knowing what to do with it. Marking preserves the work so the return visit is fast, and moving immediately protects the questions you have not read yet.
Check
Twenty-two questions, thirty-five minutes. Do this one in your head.
Check your understanding
You finish question 11 and the timer shows 14 minutes remaining. About how many seconds do you have for each of the remaining questions, and are you ahead or behind pace?
Answer: A
Why: Eleven questions remain and 14 minutes is 840 seconds, so 840/11 is about 76 seconds each. The module's natural pace is 2100/22, about 95 seconds, so 76 is roughly 20% short — you are behind by about 4 minutes, or two and a half questions' worth of time.
Check
One line from an error log. Give it a category.
Check your understanding
A student writes: 'I knew it was a circle area question. I wrote A = 2 pi r, got 12 pi, and picked the matching choice. It took 40 seconds.' What is the error category?
Answer: A
Why: The student recalled circumference (2 pi r) in place of area (pi r squared). The recall of the formula is the failure, which is exactly what the Geometry category names, and its fix is to write the formula down before substituting any numbers.
Hypothesis
Before your next timed set of six questions, commit to a number. This is how you find out whether your self-model is calibrated.
Predict first
Of those six questions, on how many do you predict you will hit the 60-second mark with no clear path?
Correct: Most students predict 1 and actually hit 2 to 3 — the prediction is the data, not the number.
Why: The value here is not the guess but the gap between the guess and the result. Under-predicting means your internal clock is running slow, which is the same distortion that produces 'I only spent a minute on it'. Write your prediction down before you start and compare it afterwards; if you predicted 1 and hit 3, your pacing problem is a perception problem, and the four windows are the fix.
Concept
Independent work. No notes open, and the same procedure you just ran.
Pull one question of each type from your own most recent practice test — ideally ones you missed — and redo them from scratch.
| question type | the move to write first |
|---|---|
| Rates | time = distance / combined rate — before any arithmetic |
| Mixtures | amount before + amount added = amount after, over the total volume |
| Inference / statistics | is this asking for a parameter (population) or a statistic (sample)? |
| Geometry | write the formula first, then substitute |
Three rules while you work: setup before arithmetic, apply the 60-second rule, log every miss.
Explain it to yourself
They were not chosen at random.
Discussion prompt
Look at the four homework question types. What do they have in common, and what is the single habit all four are testing?
Answer:
All four are Setup-heavy rather than arithmetic-heavy. Every one of them has a relationship that must be written down before any number appears.
The habit under test is therefore one sentence: write the relationship, then substitute. The 60-second rule runs in the background, but the target here is the setup.
They are also the four families where a wrong setup still produces a plausible-looking answer — which is exactly why they need a habit rather than more practice.
Connect it up
One page, from memory. This is the last thing before the recap.
Draw it
Sketch the whole 60-second rule as a flowchart: start at 'new question', include the pre-decision (three branches), the 60-second test, the mark-and-move path, and where the return sweep joins back in. Mark where the four pacing checkpoints sit.
Exit ticket
One question before you close the deck.
Predict first
Which of the three steps will be hardest for you to actually do on test day?
Correct: For most students it is Step 2 — stopping is harder than starting.
Why: Steps 1 and 3 are mechanical: you either said the script or you did not, you either tapped the flag or you did not. Step 2 requires overriding a feeling in the moment it is strongest, which is why it needs a test ('can I name my next move?') rather than willpower. Whichever you picked, that is the one to consciously rehearse in your next timed practice — name it out loud before you start.
Recap
Everything in this deck flows from three lines.
| you can now | the move |
|---|---|
| Choose a method before working | Hand, Desmos, or skip — said in one second |
| Stop directionless work | At 60 s: can I name my next move? |
| Recover a skipped question | Mark for Review, then a planned sweep |
| Catch a pacing drift early | Check at Q7, Q11, Q15, Q18 |
| Turn a miss into a drill | One of six categories, every time |
Next step: a full 20-question timed drill, with your hand / Desmos / skip pre-decision recorded for every single question.
Want this taught 1-on-1? Alexander tutors SAT Prep — $55/session, free consultation.