By default, creators are not automatically notified when you change a submission's stage in Dapple. They see the updated stage when they sign in to their Creator Account. If you want creators to know about a stage change, send them a message via the Messages tab or set up a Stage Automation to send a templated message when the submission enters that stage.
Do creators get an automatic notification when I change a stage?
No, not automatically. Stage changes happen silently from the creator's perspective. The next time they sign in to their Creator Account, the new stage is visible. This is intentional — it gives you full control over when and how you communicate stage changes.
Which actions trigger automatic notifications to creators?
Action | Creator notified automatically? | Notes |
Submission received | Yes | Confirmation email sent on successful submission |
Payment confirmed | Yes | Receipt sent by Stripe immediately after payment |
Status changed (New → In Progress etc.) | No | Manual message required unless Stage Automation is set up |
Stage changed | No | Manual message required unless Stage Automation is set up |
Message sent by organiser | Yes | Email delivered immediately |
Submission recalled | No | Creator is not notified automatically |
Submission deadline reminder | Yes | If automation is set or sent manually |
How do creators see stage changes?
They sign in to their Creator Account.
Their dashboard shows the current stage of every submission.
The stage label is whatever you've set in Project Settings → Stages → creator-facing label.
In this example, the
How to communicate stage changes to creators
You have two options for notifying creators when their submission moves:
Approach | Best for | How |
Manual message | Specific decisions where the message needs personal context | Open the submission → Messages tab → write or pick a template → send. |
Stage Automation | Bulk announcements like 'You've been shortlisted' or 'Submissions are closed' | Project Settings → Stages → Configure Automation → Send Message → pick a template. |
Full automation guide: How to Set Up Stage Automations in Dapple
How to customise what the creator sees for each stage
Open the project → Project Settings → Stages.
Click into the stage you want to customise.
Below the stage name, find 'Displayed to creator as…'.
Click Edit and add the creator-facing label.
Save.
Use this to make stage labels creator-friendly. An internal stage called 'Round 2 — Shortlist Review' might display to the creator as 'Currently being reviewed'. They don't need your internal naming.
What about Drafts?
Draft is a creator-only status. It represents submissions a creator has started but not yet submitted. Drafts appear in the creator's account so they can come back and finish — your admin workspace doesn't see drafts (only completed submissions). Creators can resume, edit, and submit drafts at any time.
How do I customise which status changes trigger notifications?
Dapple does not have a global toggle for status-change notifications — notifications are driven by Stage Automations you set up, or messages you send manually. To control notifications per stage:
Add a Stage Automation for each stage where you want automatic creator notifications.
Leave stages without an automation if you don't want creators notified when submissions reach that stage.
Use bulk message for ad hoc notifications that don't fit neatly into a stage transition.
Can I stop creators from being notified at all?
There is only one automatic notifications — submission confirmation cannot be disabled. All other notifications (stage changes, status updates, feedback sharing) are manual or automation-driven, so they only fire if you trigger them. If you want a silent stage (no creator notification), simply don't add a Stage Automation for it and don't send a manual message.
Best practice
Plan your stage labels before you go live — creator-facing labels are part of the experience.
Use Stage Automations for big stage transitions where you want every creator notified consistently (Shortlist, Selected, Not Selected).
For multi-round contests, send a final batch message after each round rather than per-decision messages — clearer for creators.
Don't ghost rejected creators. A short, kind rejection message is much better than silence.
Where to go next