Review count thresholds in Dapple decide when a submission is marked complete inside a Review Round — set on the Deadlines & review counts step of the Review Round setup wizard. Turn on "Require all panel members to review" to wait for every active Review Group member's feedback, or turn it off to set a custom minimum and, optionally, a maximum. Reaching the threshold marks a submission complete internally, but doesn't stop reviewers submitting feedback afterwards. The same step also sets the reviewer due date, covered in full in How to Set a Due Date for Reviewers.
Where do you set review count thresholds in Dapple?
Review count thresholds sit on step 3 of the Review Round setup wizard. Open Workflow & Reviews, click + Add review round on the relevant stage (or open an existing round's settings), and move to this step. The step covers two things: the reviewer due date, and the thresholds that decide when Dapple marks a submission complete. This article focuses on the thresholds.
What does "Require all panel members to review" do?
Turn on "Require all panel members to review" and Dapple won't mark a submission complete until every active member of the Review Group has submitted feedback. It's the strictest setting — nothing gets missed, but one slow reviewer holds up every submission they're assigned.
Turn it off to set a custom minimum instead. This suits larger Review Groups where you don't need every member's input before moving a submission on.
How do minimum and maximum reviews per submission work?
With "Require all panel members to review" off, two fields appear:
Minimum reviews per submission — how many reviews are required before Dapple marks the submission complete. Defaults to 1.
Maximum reviews per submission — once this limit is reached, no further feedback can be started for that submission. Leave blank for no limit.
Set the minimum to your real decision-making bar — three independent scores, for example, rather than one. Set a maximum when over-reviewing is the actual risk: a large Review Group working through a small submission pool (most leave this blank).
Does reaching the threshold stop reviewers submitting more feedback?
No. Once the minimum is met, Dapple marks the submission complete internally — but that's a status, not a lock. Any reviewer who still has the submission assigned to them can submit feedback after the threshold is passed. If you need a hard stop, don't rely on the threshold. Move the submission to a different stage or close the round instead.
What are the reviewer due date options in Dapple?
The same step sets the reviewer due date, with three options: No due date, Specific date, and Days from submission. Days from submission suits rolling or drip-fed submissions — for example, when a Stage Automation sends submissions into the round continuously — since each reviewer's countdown starts from when their own submission arrived, not a shared calendar date. Full instructions, including what reviewers see, are in How to Set a Due Date for Reviewers.
What should you consider when setting review count thresholds?
Strong threshold settings avoid two failure modes: a submission stuck waiting on one reviewer, and a submission over-reviewed by more people than you need. Before saving, check:
The minimum matches your real decision-making bar, not just "more than one"
Maximum is left blank unless over-reviewing is a genuine problem for your programme
Turning off "Require all" doesn't remove anyone from the round — it only changes when it's marked complete
Internal completion isn't a hard stop — lock the stage separately if reviewers must not submit after a point
Where to go next