Pacing, Triage, and Question Order

A standard Reading and Writing module contains 27 questions and lasts 32 minutes. [1] The full-clock average is about 71 seconds per question, but that includes any review. A useful starting plan is to reserve about 3 minutes, leaving 29 minutes for first visits: 1,740 seconds divided by 27 is about 64 seconds. Neither average is a deadline for a particular item. A clear punctuation decision may take much less time; a difficult comparison may deserve more.

For a sequential route, try the remaining-clock checkpoints below in practice. A first visit ends when you select an answer and move on, even if that answer is provisional and marked for review. The checkpoints protect time for questions you have not reached. They do not certify that the first 9 or 18 answers are correct, and they do not require you to abandon a nearly completed solution to meet a number. If your route jumps around, count first-visited items instead of using the displayed question number.

At a checkpoint, ask what remains: unvisited questions, useful flagged checks, and any unanswered items. For a quick first-pass estimate, subtract your planned review reserve from the remaining seconds, then divide by the number of unvisited questions. With 11 minutes left, 8 unvisited questions, and a 3-minute reserve, the estimate is 480 divided by 8, or 60 seconds each on average. The flags still need attention within the reserve; the calculation has not made them disappear.

Adjust the plan to the work, not just the arithmetic. Several familiar editing items may allow you to recover time; an unfamiliar passage may require selective deferral. Do not spend every spare second simply because a formula permits it. The reserve is a proposed starting point and can shrink when necessary. If you use approved different timing, build and rehearse the plan from your actual Bluebook settings. Standard-time checkpoints should not replace your approved arrangement.

The relevant question is not just how long you have spent. It is what the next few moments are likely to accomplish. Productive work changes the decision: you locate the actual subject, identify the comparison group in a table, or find a qualifier that separates two choices. A stall repeats the same activity without new evidence: reading the entire passage again, alternating between two answers, or hoping an unfamiliar word will suddenly become familiar.

Use a three-part check: name the remaining uncertainty, name an action that could resolve it, and judge whether the clock can support that action. For example, "I need to check whether the finding applies to one site or every site" suggests a focused reread. "I still dislike both answers" does not yet supply a plan. If there is time, one purposeful attempt may turn that vague uncertainty into a useful check. If it produces no progress, stop renewing the same unsuccessful attempt.

The time already spent is gone whether you continue or move on. Ninety seconds of productive work can justify a short final check; ninety seconds of circular rereading does not create a claim on another ninety seconds. Conversely, a fast initial answer can deserve a revisit if you notice a concrete defect. Decisions should respond to evidence and remaining work, not to a rigid elapsed-time rule or a desire to make the previous effort feel worthwhile.

When deferring, select the best-supported answer available, then mark the question if a useful revisit is possible and move on. Retain a compact check such as "compare the two authors' claims" or "check the table's units"; do not rewrite the passage. A provisional answer can still be wrong, but a review mark alone is not an answer. Later, rank marked questions by the usefulness and feasibility of the next check. The question that consumed the most time does not automatically deserve the first return.

A useful default is to work forward, selecting provisional answers and deferring selectively when a question stalls. This route limits navigation and makes it easier to see how much of the module remains. It does not require equal time on every question. It also avoids deciding in advance that an entire skill is either easy or expendable. A familiar-looking grammar item can be difficult, while a reading question can have a clear, directly supported answer.

An alternative route may help a particular student, but it must solve an observed problem. For example, a student who repeatedly runs out of time before reaching editing questions might test completing identifiable editing items earlier, then returning to reading. The route needs a clear return point and a way to track unvisited questions. Recognize tasks from their stems and answer choices; do not assume a fixed question number marks the start of a grammar block. Simply jumping to a later displayed number does not mean you have completed the earlier work.

Test routes on fresh, reasonably comparable mixed material under the same timing. Keep other major conditions stable, and alternate which route you try first across practice sessions. Record correct answers, unanswered items, accuracy by skill, time to first-visit completion, and navigation problems. A route that finishes sooner but creates more careless errors may be a poor trade. A route that feels calmer deserves consideration, but that feeling should be checked against what actually happened.

One comparison is a clue, not a verdict: different forms may vary in difficulty, and one unfamiliar passage can affect a small sample. Repeating the same questions under a new route mixes the effect of order with memory. Selecting only your easiest questions makes the comparison even less useful. Prefer the simplest route that repeatedly supports accurate completion in your practice. If no alternative has shown a clear benefit, retain the familiar route for the test instead of making a last-minute experiment.

Being behind a checkpoint is information, not a verdict on the module. First replace "I am too slow" with a count: time left, unvisited questions, and unanswered items. Then identify the behavior to change. If repeated rereading caused the delay, shorten unproductive loops; if one difficult question caused it, do not let that exception turn into a rule for every remaining item. Keep enough reading to identify the task and the evidence. Skipping essential context can create errors without recovering useful time.

Recalculate once, then act. Suppose 6 minutes remain and 6 questions are unvisited. Preserving 2 minutes leaves 4 minutes, or 40 seconds per new question on average. That estimate signals the need for focused solving and selective provisional answers; it does not require six guesses or exactly 40 seconds on each item. If a strict reserve would leave almost no first-pass time, reduce it. The purpose of a reserve is to support completion and useful review, not to keep an untouched block of time while accessible questions remain unseen.

As time becomes scarce, check that each question has a selected answer. There is no penalty for guessing. [5] Use supported eliminations when available, but do not spend the final seconds inventing a reason to prefer a letter. Once selections are complete, prioritize checks with a realistic chance of changing the decision: an unchecked comparison row or a possibly missed word can be more useful than reconstructing an unfamiliar argument from the beginning. This is a qualitative judgment about remaining work, not an estimate of SAT point values.

Within the current module, you can return to questions; after leaving the module, you cannot return to it. [2] Finish that module's work before the boundary. If time remains, do not change a supported answer merely because it has been selected for a while. Review needs a specific question and a stopping point: "Does this option reverse the authors?" is actionable; "Read everything again until I feel certain" is not. When the module ends, carry forward your routine, not an attempt to solve a question you can no longer change.

Keep these checks in mind

• Use checkpoints to notice a developing time problem. They are approximate rehearsal targets, not individual question deadlines.

• Continue when you can name a useful next check and afford it; defer when more time is producing no new evidence.

• Select a provisional answer before moving on. A review mark identifies work to revisit; it does not answer the question.

• Keep a route only if fresh practice supports it after accounting for accuracy, omissions, and navigation cost.

• Near the end, ensure every question has a selected answer, then spend the remaining time on specific, feasible checks.

Begin with four short drills, one per lesson, then complete twelve multiple-choice questions, three per lesson. Labels distinguish SAT-format questions from strategy decisions. Give the evidence or stated condition that decides each item. Model drill responses are examples; another well-supported response may also work.