Tags in Dapple are coloured labels you add to submissions or applicants to group, filter and track them. Create them in Settings → Organisation Settings → Tags: choose Submission Tags or Applicant Tags, select Add Tag, then give it a label and colour. You can also choose whether the tag is added automatically, and whether it's Visible to reviewers — so judges can see, filter and group the submissions they review by category, region or anything else you tag. Tags are available across every project in your organisation.
What's the difference between Submission Tags and Applicant Tags?
| Submission Tags | Creator Tags |
Applies to | One submission in one project | An applicant, across every project |
Examples | Fiction, Shortlist, USA, Eligible, Paid | Alumni, Mentor, Previous Winner, VIP |
Visible to applicants | No | No |
Can be visible to reviewers | Yes, if you turn it on | Yes, if you turn it on |
Looks like | Coloured pill | Coloured pill with a small person icon |
How do I create a tag in Dapple?
Go to Settings → Organisation Settings → Tags.
Select the Submission Tags or Creator Tags tab.
Select Add Tag.
Enter a Label, such as "Fiction 2026".
Pick a Colour that stands out from your other tags.
Turn on Visible to reviewers if your reviewers should see this tag.
Choose an Auto-add option.
Save.
How do I edit an existing tag?
In Settings → Organisation Settings → Tags, select the pencil icon next to the tag. Change the label, colour, reviewer visibility or auto-add setting, then select Save Changes. Changes apply everywhere the tag is used.
What does Visible to reviewers do?
With Visible to reviewers on, reviewers can see the tag on the submissions assigned to them, and filter and group by it in their Review Account. With it off, the tag is only visible to your team. Tags are off for reviewers by default, so nothing changes until you turn it on.
It's most useful for categories. Tag each entry with its category, make the tags visible, and judges can work through one category at a time instead of one long list.
What can I use reviewer-visible tags for?
Use case | Example tags | How it helps reviewers |
Categories | Fiction, Poetry, Non-Fiction | Judge one category at a time and compare like with like |
Geography | USA, UK, Europe, Asia-Pacific | Apply regional criteria or see where a submission comes from |
Eligibility checks | Eligible, Eligibility Confirmed, Late Entry | Know your team has already checked a submission |
Format or medium | Video, Print, Installation, Audio | Prepare for the right kind of review — time, equipment, viewing |
Funding level or track | Small Grant, Large Grant, Early Career | Score against the right expectations for each track |
Priority | Priority Review, Resubmission | Know which submissions to look at first |
Language | Welsh, Spanish, Translation | Route to, or flag for, reviewers who read that language |
For awards, see How to See All Entries in Each Awards Category in Dapple — tag every entry with its category, make the tags visible, then filter by tag and bulk assign each category to its judges.
Which tags should I keep hidden from reviewers?
Anything that could identify the applicant or influence a score. Keep these hidden, especially if you run blind review:
Applicant Tags such as Alumni, Previous Winner, Mentor or VIP.
Internal notes such as Follow-up, High Priority or Paid.
Outcome tags such as Shortlist, Rejected or Selected, until the round is over.
Anything based on personal or demographic information.
Should I turn on auto-add?
Auto-add can apply a tag automatically when paired with the agent feature, so you don't have to tag submissions by hand — for example, a "Grant proposal" tag could automatically be added to this and then using an automation route to the correct review round. Choose an option from the Auto-add dropdown only when a tag should be applied every time.
How do I tell tag types apart in the dashboard?
Both appear as coloured pills in the submissions list. Creaot Tags have a small person icon. Submission Tags don't.
Best practice for tags
Add the year to tags for recurring programmes, e.g. "Fiction 2026".
Keep Creator Tags broad and long-lasting, and Submission Tags specific to a project or round.
Use the same names for category tags and category form options.
Only make a tag visible to reviewers if it helps them review — not because it's useful to your team.
Tag categories before you assign reviewers, so judges can filter from their first login.
Use distinct colours, and review your tag library once a year.
Where to go next