Time management is not a knowledge problem, and learning more content does not fix it. It has its own arithmetic, which almost nobody has done: 134 minutes divided between four modules gives each question a budget, and knowing the time per question is what lets you tell — while sitting there — whether three minutes on one question is a disaster or perfectly fine.
Each section is two modules, and each module is timed separately — so the budget that matters is the one inside a module, not across the section.
Two modules, 32 minutes each
71seconds a question, on average
32 minutes ÷ 27 questions in a module — the time per question that module allows
Where to be
Two modules, 35 minutes each
95seconds a question, on average
35 minutes ÷ 22 questions in a module — the time per question that module allows
Where to be
The average is not the instruction. Questions are not equal, and watching a 71-second budget on every one of them costs more attention than it saves — especially for the reader who is already anxious about the clock. The three checkpoints are the useful form: one glance, one comparison, and you know whether anything needs to change while it is still early enough to change it.
Not the order these are usually taught in. The first costs nothing, needs no practice, and saves more than the rest put together.
A wrong answer and a blank are both worth zero, so a blank is a guaranteed nothing where a guess on a multiple-choice question is a one-in-four chance. If a module is getting away from you, stop working at three minutes remaining and spend them filling every empty answer. This is the single highest-value minute in the whole test and it needs no preparation.
Decide within about fifteen seconds whether you know how to start. If you do not, flag it and skip — a question you cannot begin does not become easier by being stared at, and the three unopened questions behind it may be ones you would have got. Almost everyone who runs out of time ran out of it on a question they were never going to get. Skipping is not giving up: the flag is there so you can come back with whatever time the rest of the module leaves you.
Watching a per-question budget costs more attention than it saves and rattles the reader who needs it most. Three checkpoints in a module is enough to catch a problem while it is still fixable, and each one is a single comparison: am I at that question yet?
Reading and Writing passages are short and each carries one question. Rereading a paragraph before knowing what is being asked is the commonest way to spend ninety seconds on a seventy-second question. Read it once at normal speed, read the question, then go back to the one sentence that decides it.
The graphing calculator built into the testing app is Desmos, it is available on every Math question, and that is not a reason to use it on every Math question. Typing a two-step arithmetic problem into a graphing tool is slower than doing it, and setting up a graph to solve something you could factor in your head is slower still. Reach for it when it does something you cannot: graphing an intersection, checking a messy root, working a system you have already set up.
Pacing is a habit and habits do not appear on test day because you intended them to. A timed round where the only pressure is speed trains the recognition step — knowing immediately what kind of question this is — which is where the time actually goes. Untimed practice trains the method; only timed practice trains the decision to move on.
Pacing is a habit, and habits do not appear on test day because you meant them to. Untimed practice trains the method; only timed practice trains the decision to move on, which is the one that actually runs out of clock. A sixty-second round where speed is the only pressure isolates the recognition step — knowing immediately what kind of question this is — and that is where the minutes go.