The digital SAT lets you flag a question and jump freely between questions within a module — but only until you submit it. This guide covers how to use flagging with intention and how to structure your final review pass for the best return on your remaining time.

How flagging works on the digital SAT

Within a module, you can mark any question with a flag and move on, then use the question navigator to jump back to it later — as long as you haven't submitted that module yet. Once a module is submitted, it's locked permanently; there's no going back to fix an answer, even if you realize your mistake seconds later. This makes flagging the single most important in-module tool you have for managing uncertainty.

What to flag versus what to just answer and move on

Not every question you hesitate on needs a flag — flagging too much clutters your review list and wastes review time re-reading questions you were actually fine on. A useful rule:

  • Flag it if you're unsure between two answer choices and want a second look with fresh eyes.
  • Flag it if you guessed and there's a real chance you'll have time to return and solve it properly.
  • Don't flag if you're confident in your answer, even if the question took you a while to solve.
  • Don't flag a question you already know you can't solve even with more time — flagging it won't change that, and it's better to guess and move on immediately, following strategic guessing instead.

A good gauge is to ask yourself, at the moment you're about to move on: "If I had two extra minutes at the end, would I actually make progress on this?" If the honest answer is yes, flag it. If the honest answer is "probably not, I just don't know this content," a flag is wasted review time later.

Structuring your final review pass

Save your last several minutes of each module specifically for flagged questions, not for starting anything new. When you get there:

  1. Use the navigator to jump straight to your flagged questions instead of scrolling through the whole module.
  2. Tackle the ones you remember being closest to solving first — these give you the highest return per minute remaining.
  3. For questions where you're stuck between two choices, re-read the question stem specifically, since misreading is a common reason for being stuck between two options that both seemed plausible.
  4. If time runs out before you finish your flagged list, make sure every flagged question still has some answer bubbled in — a flag doesn't submit an answer for you.

A flagged question with no answer selected is still a blank question. Always bubble in your best guess the first time through, then improve on it during review if you get the chance.

A concrete example of a productive review pass

Imagine you finish the main pass of a module with four minutes left and three flagged questions. Rather than opening them in the order you originally saw them, quickly recall which ones felt "close" versus "stuck." Say question 6 you narrowed to two choices but ran out of time to pick, question 14 you fully blanked on, and question 19 you solved but weren't sure about a sign. Spend your first, most valuable minute on question 6, since you're one small decision away from a point. Spend the next minute on question 19, since re-checking a specific sign is fast and targeted. Only spend remaining time on question 14, since a full blank is the least likely to convert into a point regardless of how much time you give it. This ordering — closest-to-solved first — consistently produces more recovered points than reviewing flagged questions in the order they appear.

Flagging and the adaptive module structure

Because your performance in Module 1 affects the difficulty (and scoring ceiling) of the adaptive Module 2, it's worth being extra careful with your review pass in the first module specifically. A flagged question you fix correctly in Module 1's review time isn't just one more point — it can also affect which question pool you see in Module 2. This is one more reason not to rush through Module 1 just to "bank time," since sloppy answers there can compound.

How many questions is too many to flag?

There's no fixed cap, but as a practical guide, if you find yourself flagging more than five or six questions in a 22-question module, that's usually a sign you're flagging out of general uncertainty rather than genuine, recoverable doubt. A long flagged list means your review time gets spread thin across many questions instead of concentrated on the few most likely to convert into points. If your flag count runs consistently high in practice, it's worth tightening your own criteria — reserve the flag specifically for "one step away from solving" or "torn between two choices," not for every question that felt slightly uncomfortable.

Building a flagging habit through practice

The flag-for-review workflow feels unfamiliar the first few times you use it, which is exactly why it's worth rehearsing before test day. Timed SAT Math practice sets that include a question navigator and flag feature let you build the muscle memory of flagging, moving on, and returning efficiently — so on test day it's an automatic habit rather than something you're learning in real time under pressure.

Frequently asked questions

Can I go back to Module 1 after starting Module 2?

No. Once a module is submitted, it's locked permanently, and there is no way to return to it after you've moved on to the next module.

Does flagging a question change my score if I never revisit it?

No. A flag is purely an organizational tool for you — it doesn't affect scoring on its own. What matters is the answer you have selected when the module is submitted, flagged or not.

Should I flag questions I answered quickly and confidently?

Generally no. Reserve flags for genuine uncertainty so your review list stays short and focused, letting you spend your limited review time where it actually helps.

What order should I review flagged questions in?

Review the ones you remember being closest to solving first, since they offer the highest chance of converting into a point per minute spent. Save fully blanked questions for last, since they're the least likely to be resolved even with extra time.