Should I use automated tagging?
Automated tagging allows you to automatically apply tags to entries to help manage and organise your program. Tags can be applied based on:
- The option(s) an entrant selects in an optionable field, or
- A specific trigger event in Award Force
Both methods can be used together depending on your workflow.
To learn more about tags, see our Ultimate guide to tags.
Auto-tag based on an optionable field
Optionable fields include drop-down lists, radio buttons, and checkbox lists. This method is useful when you want to:
- Track demographic responses
- Allow entrants to “enter” multiple categories
- Classify or segment entries automatically
To configure automated tagging from a field:
- In the Manage workspace, go to Entries
- Click Edit form
- Create or edit an optionable field (see: Field configuration)
- In the 'Options' section, toggle on Auto-tag
- Add the tag you want applied for each option
- Click Save
When an entrant selects an option, the system applies the tag based on the option’s value.
Auto-tag based on a trigger
Award Force provides a set of system events that can automatically apply tags when they occur.
To configure an automated tag based on a trigger:
- In the Manage workspace, go to Settings > General > Tags
- Create a new tag or open an existing one
- In 'Automatically apply tag when', select the event that should trigger the tag
- Click Save
When the selected action occurs, Award Force will apply the tag to the entry automatically.
Available triggers
These system events can automatically apply a tag when they occur:
Entry activity
- Entry submitted – an entry is successfully submitted
- Entry resubmitted – an entry is resubmitted
- Entry archived manually – an entry is manually archived
- Entry tagged – an entry is tagged
- Entry moderated – an entry is approved, rejected, or marked undecided
- Entry duplicate confirmed – the primary or secondary entry in a duplicate pair is identified
Payments
- Payment success – payment is successfully completed
- Payment pending – payment has been started but not completed (e.g. invoice or offline payment)
Review stages
Triggered when any of the following occur:
- A review stage starts
- A reviewer clicks Proceed
- A reviewer clicks Stop
Use case: if you use multiple review flows for the same entry, you may later need to filter by the outcome. Because the Entries can only filter by one review status at a time—and entries can hold more than one status—we recommend applying automated tags when an action stage is triggered or when reviewers select Proceed or Stop. These tags allow you to filter applications reliably, regardless of how many review statuses they hold.
Judging
- Assignment completed – a judge completes their assignment for a score set
Good to know
- Automated tagging works well with multi-stage judging, workflows, and perpetual seasons.
- Tags applied through automation are invisible to entrants and judges unless explicitly enabled for judges. If you need judges to see tags, check out our guide: How can I allow judges to see tags?
- Tags are extremely powerful when paired with judging panels, filters, or notifications.
- Optionable-field tagging uses the field’s value, not its label.
- You can remove an auto-tag rule at any time by editing the tag configuration.