We are equipped to handle this through community moderation.
We have pretty low volume review queues here. SSD wrote in this answer:
Reviewers can just take bites out of it, and bow out when decision fatigue rears its head. Pressing Skip when at all unsure helps a lot in that regard, too. Others will pick it up and take care of a few more, until the whole queue has been reviewed. Crowdsourcing at work!
It's much preferable for the queue to balloon occasionally, and be handled by the normal crowdsourcing mechanisms it has for precisely such events, than for people to refrain from flagging when they see something that deserves a flag. All that refraining results in is different people having to—redundantly—each stop and ponder how much flagging is “too much,” wasting user energy that would be better spent just about anywhere else on-site or off, just so that we can, inexplicably, prevent the flood-management measures designed into the system already from needing to be used.
We should be just fine to handle it without moderator assistance, and as I am writing this, things seem to be moving through the queue smoothly:
Image of the review queue.
It's best to do it in small to medium sized batches.
Because:
If you send in more questions than we have active reviewers with votes remaining, that's a problem. In hindsight, I should have saved some close votes just in case I needed to close something more pressing before my votes reset.
