Where the Time Actually Goes

Chapter 1 mentioned that running out of time usually doesn't come from being slow everywhere; it comes from a handful of specific moments, a hard passage, a reread loop, a stuck comparison between two answers, quietly spending the time meant for what comes later. This chapter is where that idea becomes a concrete, usable system.

This chapter is not about becoming a faster person. It's about deciding where another look is actually worth the time. Years of student reports show the same painful pattern, over and over: a student who can answer accurately without a clock loses points anyway, because one passage, one reread, one rhetorical question, or one pair of plausible choices quietly ate the time that later questions needed.

Nothing here is stopwatch obsession. The idea underneath everything in this chapter is simple enough to hold in your head mid-section: classify the decision in front of you. Some questions are one-pass questions. Some deserve exactly one specific second look. Some should be answered with your best current guess, marked, and left for later. Knowing which one you're looking at, in the moment, is most of what pacing actually is.

Source note. Official facts in this chapter, section timing, question counts, and the no-penalty guessing rule, reflect current ACT policy verified August 21, 2026; confirm current timing on your admission ticket before test day. The recurring behavior patterns described below (rereading, mid-section hesitation, coverage loss) are drawn from patterns test-takers have reported over time, not from a formal study, and are presented as common experience rather than official ACT findings.

Find the exact place where time stops buying useful information.

Ask students what went wrong on a slow section, and a few answers come up again and again, and they're worth naming directly, because each one points to something specific and fixable rather than a vague need to "go faster."

"Untimed, I score much higher" can indicate the knowledge is there, but recognizing and retrieving it is too slow once a clock is actually running. "I always leave the last Reading passage" can indicate time was disappearing earlier in the section, in small amounts, and only became visible at the very end. "I read faster and got worse" can indicate a shallow first read made every answer choice look plausible, so more time went into rereading than the faster read ever saved. "I read carefully and still ran out" can indicate comprehension was fine, but rereading, answer-choice debate, or detail-hunting was the actual expense. "English normally feels easy, then I ran out" can indicate the rhetorical and placement questions, not the grammar questions, absorbed disproportionate time. "I had extra time in practice but not on paper" can indicate bubbling, page turns, and real test-day nerves changed the pacing that untimed or digital practice never tested. "I got almost everything I attempted right" can indicate accuracy was never the problem; coverage was. "I changed answers at the end and regretted it" can indicate review turned into generalized doubt instead of targeted checking. "I keep checking the clock" can indicate the checking itself, not the difficulty of the questions, was consuming attention. And "one hard passage ruined the section" can indicate a single local difficulty turned into a pacing and emotional cascade that spread past the passage that actually caused it.

None of these are about being slow. They're about where, specifically, time stopped buying useful information and kept getting spent anyway. That's the question this whole chapter answers.

It helps to know the actual shape of the current test rather than a remembered version of it.

The enhanced ACT was built to give more time per question than the legacy test did. That doesn't make pacing irrelevant; ACT's own practice-test review still asks whether you ran out of time, and current student reports still describe unfinished English and Reading sections. The average above is a planning fact, not a countdown. A punctuation question might take seconds. A sentence-placement question might require reading most of a paragraph. A clean Reading detail question with an easy locator might be fast; a cross-text synthesis question might not be. Good pacing means letting the cheap questions stay cheap, so the expensive ones have somewhere to draw their time from.

Spend more time only when the next look can settle something.

Every question you meet is in one of three states, and naming which one you're in is the actual skill this chapter teaches.

The real distinction here is not easy versus hard. A hard question can still have a clear, productive next step. An easy-looking question can quietly become a time trap if you're rereading it without knowing what would actually settle it.

Know when a question is finished. A finished question doesn't require certainty; it requires a completed decision. You know a question is finished when the controlling grammar rule is identified and the sentence works once you substitute the answer in. When the requested rhetorical goal is satisfied by exactly one choice, and you could state the reason why. When the relevant Reading evidence has been located and one choice matches its scope and strength. When two finalists have actually been compared on the one dimension that differs between them. Or, just as validly, when the only doubt left is purely emotional, a "what if I missed something" with no specific missing check attached to it. That last kind of doubt is not a reason to keep looking. A finished question does not need to feel perfect. It needs a completed decision.

Give a second look one job. A second look only pays for itself if it has an actual target. "Read it again" is not a target; it's a way of spending time without buying anything.

Once the specific target is resolved, the question is finished. There's no separate step where you reread everything else "just in case."

Leave when another look is no longer producing information. There's a recognizable moment when more time stops helping, and it's worth being able to name it in real time. It looks like this: the same sentence has been reread and nothing new was noticed. The same two answer choices have been compared more than once without you actually naming what separates them. You're scanning the passage without a locator or a specific question to answer. You're trying to remember a rule instead of using the structure that's sitting right there in the sentence. You're rereading an entire paragraph for a question whose evidence is already localized to one place. You're double-checking an answer because it came quickly, not because there's any actual evidence of a problem. Or you're trying to make an answer certain when the task only ever required the best-supported answer.

That's the moment to leave. The clock isn't punishing difficulty. It's punishing unproductive repetition, which is a very different thing, and recognizing the difference is what lets you leave a hard question without feeling like you're giving up on it.

Keep fast local questions fast and protect time for passage-level decisions.

The current English section gives more time per question than the old 75-question form did, but the passage format still creates uneven question cost. Clean grammar questions are often where time can be saved. Questions that widen the reading window, purpose, relevance, add/delete, sentence placement, paragraph order, transitions across a larger span, and stated-goal questions, can require substantially more time.

A useful pacing rule is: don't spend rhetorical-question time on grammar questions. A student who takes a full minute confirming a clean subject-verb agreement question is borrowing that minute from a placement or purpose question later in the same passage that actually needed it.

Save wider context for the questions that need it. Three moments are worth walking through directly, because they show the difference between the three decision states in practice, not just in theory.

Finish in one pass when the answer is already settled. "A collection of letters from the expedition, together with several field notebooks, reveals how carefully the team recorded daily weather conditions." Suppose the choices are reveal, reveals, have revealed, revealing. The phrase "together with several field notebooks" sits visually close to the verb, but it doesn't replace the subject. The subject is "a collection." Once that's identified, "reveals" finishes the question, and rereading the surrounding paragraph again adds nothing at all. That's what one-pass means: not rushing, but refusing to buy evidence the sentence never actually asked for.

Take a second look only when one specific check can settle the question. "The first community garden occupied a vacant lot beside the library. Within two years, residents had added raised beds, a tool shed, and a weekly produce table. ___, the project became a model for similar gardens in three neighboring districts." If the finalists are "Consequently" and "Similarly," the second look has exactly one target: what relationship actually connects the garden's expansion to its becoming a model elsewhere? The second sentence is a result of the first, not a parallel example alongside it. That one named check settles the question. There's no reason to reread the whole passage looking for more.

Mark and return when the decision is still unresolved. A sentence-placement question asks where a sentence beginning "This unexpected resistance..." belongs, and you've only read the first half of the paragraph, where none of the available positions yet contain a clear antecedent for "this." The productive move isn't to stare harder at the sentence you already have. It's to keep reading. The answer may become cheap the moment the event actually being called "resistance" shows up later in the paragraph. This is a genuine return question, because later context can hand you information the earlier part of the paragraph simply didn't have yet.

Protect the end of Reading from one expensive passage.

The decade-long argument about ACT Reading usually gets framed as skim versus read carefully, and student reports show exactly why that argument never resolves: both approaches can fail. Some students lose time reading every sentence as if they're preparing for a seminar. Others skim so aggressively that every question turns into a four-way search and the passage ends up getting reread in scattered fragments anyway.

The actual target isn't a reading speed; it's a usable map. After a first read, you should know roughly what the passage is about, where it moved, who owns each important viewpoint, and roughly where the major pieces of evidence live. The exact speed that gets you there is personal. The real test of whether your method is working isn't how it feels; it's whether the questions get cheaper once you're answering them.

A more substantial first read can genuinely save time, if it prevents repeated lookups and makes eliminations immediate later. For other students, a faster first read works just as well, because they naturally retain structure without needing to slow down for it. Neither one is the correct universal method. What matters is whether your particular approach is actually making your questions cheaper, which is something worth checking honestly in timed practice rather than assuming from general advice.

Run your own strategy trial instead of adopting someone else's answer. Since no single reading strategy wins for everyone, settle the question for yourself with a small, structured trial rather than a guess. Take four full Reading passages, ideally from different practice sets so familiarity doesn't distort the comparison. On two of them, read the entire passage closely before looking at any question. On the other two, read quickly for the map, structure and viewpoint only, then go straight to the questions and locate evidence as each one demands it. Time each passage separately, and score each one separately. Then compare both methods on the two numbers that actually matter: how many minutes each one took, and how many questions each one got right. If one method is both faster and at least as accurate, that is your answer. If they are close, run the trial again on four new passages before deciding; a single four-passage sample can be noisy. What you are looking for is not which method feels more comfortable, but which one your own timed, scored data actually supports.

Read enough to make the questions cheaper. Coming out of a first read, a small number of things are actually worth carrying forward: who or what the passage is mainly following, what changed, developed, was compared, or was argued, where the passage shifted, which viewpoint belongs to whom, and roughly where the major examples, studies, objections, or results live. For paired passages, what Passage A is doing on its own, before Passage B even enters the picture. None of this means memorizing every detail. A passage map is an address system, not a storage system; its whole job is helping you find things again quickly, not holding everything in memory at once.

Here's what that actually buys you. A passage introduces an old explanation for bird migration, then describes tracking data that challenged it, then offers a newer explanation that accounts for the data. A student who only picked up names and dates on the first read reaches a question asking about the function of the tracking study and has to reread half the passage to answer it. A student who noticed the shape, old explanation, conflicting data, revised explanation, answers the same question almost immediately: the study supplies the evidence that creates the need for the revised account. The extra seconds spent noticing that structure on the first read weren't lost time. They bought a cheaper question later.

Carry a map of the passage, not every detail. The map also tells you when to stop rereading. Take a question like: "The passage most strongly suggests that the researchers were cautious about applying the result beyond the coastal population because..." You've located the final paragraph, where the authors note the sample came from a single coastal region and that broader populations may differ. Two choices remain: one says the sample may not represent other populations; the other says the researchers believed coastal conditions caused the observed behavior. The first stays exactly at the level of the limitation the passage actually states. The second invents a causal belief the passage never makes. Once that scope difference is named, another full-passage reread cannot improve the decision at all. The map already told you everything it had to tell you; what's left is a scope check, not a comprehension check.

Keep Passage A and Passage B separate. Paired-passage questions create their own specific time trap, and it's worth naming directly. A question asks how the author of Passage B would most likely respond to a claim in Passage A. The expensive mistake is rereading both passages from the beginning to "get back into" both of them. The efficient path is narrower: restate Passage A's claim first, then locate Passage B's position on that same specific issue. If B accepts the underlying phenomenon but argues that A overstates its cause, the relationship is a qualification or a challenge specifically at the level of causation, and the correct answer has to preserve both pieces of that, not just one. This is a two-source question, not a two-full-passage-reread question, and treating it as the second thing is where the time actually goes missing.

Use the clock as a landmark, not a metronome. Linear order, working through passages in the order they appear, is a reasonable default, because it minimizes navigation and protects you from spending planning time deciding what to do next instead of doing it. Some students do find real gains from tackling a stronger passage type first, or saving a reliably fast one for later. That can work. But it should be earned in timed practice, not adopted because of a general impression about which passage type is supposedly easier. Don't reorder your approach because of a single online post claiming humanities is easier or science is faster; a custom order belongs in your actual plan only once repeated, full-section timed data shows it improves both coverage and accuracy for you specifically. On digital testing, unnecessary jumping between passages also carries its own navigation cost, which is worth factoring in before deciding a custom order is worth it.

It's also worth being direct about what this chapter is not asking you to do. It is not asking you to calculate whether you're twelve seconds behind schedule on Question 17. Constant clock-checking fragments attention rather than protecting it. What actually helps is a few landmarks, learned during your own practice, that answer one simple diagnostic question: am I broadly on track. If a landmark gets missed, the right response isn't panic-speed. It's simply to stop buying low-value second and third looks for a while.

If one passage runs long, do not rush the next one blindly. Falling behind happens, and the response matters more than the fact that it happened.

Rushing the next passage to make up for a slow one often fails to recover the lost time and can spread the same problem into a second passage. Returning to your normal pace and tightening your revisits is the version that actually works.

Name the sequence so you can actually run it under pressure. The table above is easy to agree with calmly and hard to execute in the moment a passage has just run long. Turning it into a short, ordered sequence makes it usable under pressure: first, stop and notice, name to yourself that you are behind rather than letting the feeling stay vague; second, do not speed-read the next passage, return immediately to your normal, practiced pace; third, tighten revisits, allow fewer second looks at borderline answers for the next stretch rather than none at all; fourth, protect coverage, if time keeps shrinking, prioritize getting a reasoned answer on every remaining question over perfecting a few; fifth, if time runs out entirely, place an answer on everything still blank before the section ends. Rehearse this exact sequence in timed practice until it is automatic, since the version you can only remember when calm is not the version you need when a passage has actually just run long.

Return first to questions that are closest to solved.

A mark is not a queue number, and returning to marked questions in the order you marked them is usually not the most efficient way to spend remaining time. When time is available, return to whatever has the highest expected payoff first.

Mark what remains unresolved. On paper, a small symbol can distinguish a question with a specific unresolved issue from a pure guess you'd like to revisit if there's time. Online, marking for review flags the question itself, but not the reason it was flagged. Either way, train yourself to hold the actual reason in your head as you mark it: scope, source, transition, antecedent, "A versus B," or "need the final paragraph." A return is fast when you remember exactly what was left unfinished. Without that, the whole question effectively gets restarted from zero, which defeats the entire purpose of marking it in the first place.

Protect the last passage before it becomes an emergency. The last passage often becomes an emergency because too much time was spent earlier on repeated second looks, though a difficult passage, slow intake, or format friction can also contribute. If you find yourself facing it with very little time left, don't try to solve it the way you'd solve a passage with plenty of time remaining. Get a basic map quickly, take the direct and evidence-located questions first, since those are the ones most likely to pay off fast, and keep answers moving rather than trying to fully resolve every question in order. The goal in that specific situation isn't a perfect pass through the passage; it's maximum coverage with the accuracy you can actually sustain at that pace.

Answer everything before the section closes. ACT scores correct answers and does not subtract anything for wrong ones. With no wrong-answer penalty, a blank answer has no scoring advantage. If the section is closing, answer every remaining question before returning to review. This isn't a last resort to feel bad about; it's simply the correct final action once the only alternative is leaving points on the table for free.

Review with a reason. Once coverage is secured, review should stay targeted. Start with the marked questions that were nearly solved, not the ones you have the vaguest memory of. Don't reread full passages unless the specific unresolved question genuinely requires passage-level structure to answer. And don't change a clean, already-settled answer just because the clock made you nervous. Change an answer when a rule, an evidence line, a scope mismatch, a source mismatch, or a piece of overlooked wording actually gives you a reason to. There's no useful rule that your first answer is always right, and no useful rule that changing an answer is usually a mistake. The actual rule is simpler than either folk belief: evidence before change, every time.

Build pacing from your own timing and error data.

A student scored at the top of English and Reading in digital practice, then ran out of time across both sections on the paper ACT. The content hadn't changed at all. Page turns, bubbling, visual navigation, and ordinary test-day nerves changed the execution underneath it. That's exactly why the last stage of preparation has to happen in the actual format you'll use on test day, not just with the actual questions.

If you're testing on paper, your practice needs to include real bubbling, not just marking answers in a booklet and checking them against a key. If you're testing digitally, your practice needs to include the real navigation habits: moving between the passage and the question, marking for review, glancing at the timer without staring at it, and resisting the urge to jump around more than necessary. Format friction is real, and it's specifically the kind of cost that only shows up once you practice in the format that will actually be waiting for you in the room.

Audit where the minutes actually went. After a serious timed practice section, the most useful thing you can do isn't just check which answers were wrong. Ask a more specific set of questions: did you finish every question, which separates a coverage problem from an accuracy problem. Where did time first become a problem, since the last unfinished question is almost never actually where the trouble started. Which questions got reread more than once, since that finds the repetition that's otherwise invisible after the fact. Which question types keep becoming expensive, which points to a mechanism-specific gap rather than a general speed problem. Which marked questions were actually close to solved, which improves how you prioritize your return next time. Which correct answers took too long, since a correct answer can still represent a pacing failure worth fixing. Which wrong answers were rushed only because time was already lost earlier, which separates the real, upstream problem from its downstream symptom. Whether your passage intake made the questions cheaper or more expensive. Whether format mechanics, bubbling, page turning, digital navigation, cost you time. And whether checking the clock itself changed your behavior in a way that hurt more than it helped.

The single most useful question in that whole list is this one: where did time stop buying useful information? That moment is almost always more actionable than a vague resolution to "read faster" next time.

Three broad patterns tend to show up in this kind of audit, and each one needs a different fix. If you're accurate untimed but incomplete timed, the bottleneck is execution and recognition speed, and the fix is timed passages and sections, deliberate one-pass/second-look/return decisions, and format-matched practice. If you finish on time but your accuracy falls off late in a section, the likely cause is rushing or fatigue following earlier overspending, and the fix is protecting your normal decision quality, finding where the early time leaks are, and practicing recovery specifically after a long passage. If you're inaccurate both timed and untimed, the problem is upstream of pacing entirely; it's a content or evidence problem, and the fix is returning to the relevant skill chapter, because no amount of speed practice repairs an unknown rule or a misunderstood question type.

Build a pacing system that belongs to the student. The path here runs in a specific, deliberate order, and skipping steps tends to undermine the ones that come after. First, learn the mechanism itself without forcing speed onto it at all. Then solve short sets with a clock present but no aggressive target attached to it. Then start noticing which questions are naturally one-pass for you and which ones repeatedly turn expensive. Then run full passages and actually record where the time goes. Then run complete English or Reading sections under the exact current timing. Then review not only the questions you missed, but the ones you got right slowly, and the ones you got right while still feeling uncertain. Then repeat all of this in the actual paper or digital format you'll use on test day. And finally, practice recovery on purpose: deliberately continuing normally after one difficult passage or one unresolved cluster of questions, so that the first time you have to do it isn't test day itself.

None of this makes the clock disappear. What it does is make the clock manageable, because by the time you're sitting in the room, the decisions themselves are already familiar: finish what's finished, buy one specific second look when it can actually settle something, mark and move when another look has no job left to do, return first to what's nearly solved, and make sure every question has an answer before time runs out. That's the whole system. It fits in your head, which is exactly the point.