To see your highest-scoring submissions in Dapple, open Reviews in the left-hand sidebar, turn on Group Reviews by Submission, then sort by Rating — highest first. This works once every reviewer has marked their review Completed, since an average score only settles once all of a submission’s reviews are in. To act on the ranking — for example, moving your top 50 submissions to the next stage in one go — switch to the Submissions list, turn on the Current Review column under Field Visibility, sort by score, then use the bulk stage change.
How do I see average review scores for all my submissions?
Open Reviews in the left-hand sidebar. By default this shows one row per individual review, which is useful for reading specific feedback but not for ranking. Turn on Group Reviews by Submission — the toggle above the list — and Dapple collapses every reviewer’s score into a single row per submission, with a Status (All Completed, or X/Y Completed) and an average Rating.
Click Reviews in the left-hand sidebar.
Turn on Group Reviews by Submission.
Click the sort dropdown in the top right (it defaults to Started — new first) and choose Rating — highest first, or Rating — lowest first to see where reviewers disagreed.
Use Filters or Project to narrow the list to a single Review Panel if you’re ranking one round at a time.
Status matters here: a submission marked X/Y Completed still has an outstanding reviewer, so its average can still move. Wait until the submissions you care about show All Completed before treating the ranking as final.
When should I use the Reviews page instead of the Submissions list?
Use the Reviews page to see the ranking. Use the Submissions list to act on it.
Use the Reviews page when… | Use the Submissions list when… |
You want a quick, ranked read of average scores across one or more Review Panels. | You want to act on the ranking — select multiple submissions and move them in bulk. |
You need to read individual reviewer feedback comments alongside the score. | You need the score sitting next to everything else about the submission — creator, files, tags, payment. |
You’re sense-checking results before deciding on a cut-off. | You’ve settled on a cut-off and are ready to change Stage for a batch. |
How do I add review scores to the Submissions list?
The Submissions list doesn’t show review scores by default. Turn them on through Field Visibility.
Click Submissions in the left-hand sidebar.
Click More in the top right of the toolbar.
Click Field Visibility.
Toggle Current Review on. This adds a column showing each submission’s average score for the active review round.
Close the Field Visibility window.
Click the Current Review column header to sort the list by score, and click it again to flip between highest-first and lowest-first.
Field Visibility settings are saved in your browser, not against your account. If a teammate opens the Submissions list and doesn’t see the Current Review column, they need to turn it on themselves. Score is a separate toggle in the same menu — it covers overall scoring across review rounds, while Current Review reflects the round that’s currently active, so use Current Review for ranking an in-progress panel.
How do I move my highest-scoring submissions to the next stage in bulk?
Once Current Review is visible and the list is sorted, select submissions and move them with a single bulk stage change instead of opening each one individually.
With the Submissions list sorted by Current Review (highest first), select the checkbox next to each submission you want to advance — for example, the top 50.
Open the bulk actions menu that appears once at least one submission is selected.
Choose to change Stage and select the destination Stage.
Confirm. All selected submissions move to the new Stage in a single action.
Please note that the reviews will all need to be completed in order to move them. To do this, follow these instructions.
Re-check the count once the bulk action completes — it should match the number of submissions you selected.
Best practice for ranking and acting on review scores
Wait for All Completed status before ranking — partial averages on X/Y Completed submissions can still shift.
Check the Reviews grouped view first to see the spread of scores before picking a cut-off, such as top 50 versus top 20%.
Sort by Rating — lowest first occasionally, not just highest — it surfaces submissions reviewers disagreed sharply on.
Filter by Project or Review Panel before bulk-moving, so submissions from a different round aren’t swept in by a similar score.
Remember Field Visibility settings are per browser — turn on Current Review again if you switch devices or browsers.
Confirm the new Stage after a bulk move before messaging creators, in case any submissions need a second look.