Reviewing & Approving Submissions

Submission Reviews has two tabs: Pending, every submission currently in Submitted status waiting on you, and Resolved, everything already Approved, sent to Revise, or Rejected — your history of past decisions. Submissions can be selected individually or in bulk for any of the three actions below. See Submission Statuses & Message History for what each status means and how they connect.

Approve

Approve publishes the submission's question into the real Question Bank exactly as the contributor wrote it — there is no content-editing step for the reviewer. What you do control at approval time is the question's directory: keep the folder and tags the contributor's submission carried, or override them, and set the language and labels. This is your one chance to place the question correctly before it enters the live bank.

Revise vs. Reject

Both require a feedback message, but they mean very different things to the contributor:

• Revise — the idea is right but the execution needs work: unclear wording, a scoring mistake, a missing distractor. It reopens the submission for the contributor to fix and resubmit — use it whenever a rewrite would fix the problem.
• Reject — terminal, no path back. Use it when the submission shouldn't become a question at all: off-topic, a duplicate of something already in the bank, or fundamentally wrong regardless of rewording.

Because approval never edits content, Revise is also your only lever for getting a content change — if a question is almost right but one thing needs fixing, Revise with a specific message rather than approving and planning to fix it afterward yourself.

When in doubt between Revise and Reject, ask whether a rewrite by the original contributor could realistically fix it. If yes, Revise — you keep their domain knowledge and they learn what you're looking for. If no, Reject cleanly rather than leaving a hopeless submission cycling through Revise.

Good to know