To bulk-move submissions between stages in Dapple, tick multiple submissions in the Submissions view, click the action button, choose Move Stage, and pick the destination stage. You can only bulk-move submissions within a single project — selecting submissions from multiple projects shows a warning. Stage automations on the destination stage (messages, tags, webhooks) fire for every moved submission.
When to bulk-move stages
You've reviewed a batch and they're all ready to advance to the next stage.
A reviewing panel has reached consensus and you're moving everything to Shortlist or Not Selected.
A deadline has passed and you're advancing everything received before that point.
You've filtered by a tag, score, or assignee and want to advance the filtered group together.
Method 1: From the Submissions list view
Open the Submissions view.
Apply filters to narrow to the submissions you want to move.
Tick the submissions, or use Select All.
Click the action button.
Choose Move Stage.
Pick the destination stage from the list (only stages within the project appear).
Confirm — a summary shows how many submissions will be moved.
Important: bulk-move only works on submissions in the same project. If you select submissions across multiple projects, Dapple shows a warning and won't let you proceed.
Method 2: From the Stages view
Open the project's Stages board.
Click the three-dot menu on the stage column you want to move from.
Choose Move all to…
Pick the destination stage.
Confirm — a dialog shows how many submissions will be moved.
Stage-level move is the fastest option when you want to advance everyone in one column — for example, everyone in Longlist to Shortlist.
What happens when stages move in bulk?
Stage Automations on the destination stage fire for every moved submission — messages send, tags apply, webhooks trigger.
Reviewers assigned to the destination stage's Review Panel get the submissions (if Request Feedback is configured).
Creator-facing stage labels update — creators see the new status the next time they sign in.
Submission history records the bulk move so you can audit changes later.
Best practice
Always apply filters before bulk-moving. Selecting blindly is the most common cause of accidental mass moves.
Double-check the destination stage in the confirm dialog — once moved, you'd need to bulk-move back to undo.
If creators get a notification on stage change, prep the message template first so the bulk-move sends the right copy.
For pre-decided cohorts, set the message template's Allow Replies toggle deliberately — disable replies on rejection messages.