A review bucket groups a space’s submissions, such as tracks, categories, or panels, and assigns the review team that evaluates them. You can create buckets yourself, then add ordered rules so Rhythm places each new submission in the right bucket automatically.
Prerequisites
You need the permissions your administrator grants for review settings and review buckets in the Console. Without those permissions, you cannot open these pages.
What It Controls
Every space that uses reviews has at least one bucket. Each new submission lands in exactly one bucket, even when more than one bucket seems reasonable. Rhythm chooses the bucket by checking your placement rules, then uses the space’s default bucket when no rule matches.
Where to Find It
Go to Spaces › Setup › Reviews › Buckets to create and manage buckets. Go to Spaces › Setup › Reviews › Settings to choose the default bucket, then use the Bucket Assignment Rules section on that same Settings page to route submissions automatically, including into a special path such as a re-audit bucket.
Create a Bucket
- Go to Spaces › Setup › Reviews › Buckets.
- Select the option to create a bucket.
- Enter a Name: and an ID:.
- For each of the space’s review rounds, choose the Review Team that should judge submissions in this bucket for that round.
- Save.
Result
The bucket is added to the space, and you can choose it as a placement rule target or as the default bucket.
Warning
Saving a bucket rewrites the team assignment for this bucket in every round of the space, not just the round you were viewing. A staff member who can edit buckets but cannot edit rounds still changes every round’s team assignment this way.
Use the same Buckets page to reorder your buckets by dragging them into the order you want.
The Settings
| Setting | Options | Default | Effect |
|---|---|---|---|
| Default Bucket: | Any bucket in the space | None until you save one | Where a new submission lands when no placement rule matches it |
| Bucket assignment rules switch | On, off | Off | Turns automatic placement on. When it is on, you need at least one rule; Rhythm turns it back off if you save with no rules left |
| Rule Name: | Free text | Blank | Names the rule in the rules list |
| Rule Type: | Rule set, expression | — | Lets you build the condition by pointing and clicking, or by typing a formula |
| Rule Set: / Expression: | Depends on the type | Empty | The condition Rhythm checks against the space, the submitter’s contact and organization, the source record, and the submission |
| A multi-select field in a Rule Set or Expression | Depends on the field | — | A rule matches only the exact combination of selected values it names; a submission with several selected values does not match a rule written for only one of them |
| Target bucket | Any bucket in the space | None | Where a submission goes when this rule’s condition is true |
| Rule order | Drag to reorder | Creation order | Sets which rule Rhythm checks first |
Dependencies and Precedence
Rhythm checks your placement rules from top to bottom and stops at the first true condition. Later rules do not apply to that submission. Put your most specific rules first, then use the default bucket for anything left over. If a submission matches none of your rules, it lands in the space’s default bucket instead.
Tip
Because Rhythm stops at the first match and each submission lands in only one bucket, plan your rule order carefully when submissions could fit more than one condition. Put the rule for the more specific or more important group first.
A rule’s target bucket and the default bucket must belong to the same space as the rule. Rhythm will not save a rule or default bucket that points to a bucket from another space.
Build each rule’s condition around the real business reason a submission should take a special path, such as a score crossing a threshold or another measurable review outcome. Avoid arbitrary groupings so the rule still makes sense when you or someone else reviews it later.
If the field you are matching allows more than one selected value, such as a multi-select session track, the rule matches only the exact combination it names. A submission with two tracks selected needs a rule written for that same pair to move correctly on reprocessing. As the number of possible combinations grows, writing a separate rule for each one quickly becomes impractical.
Warning
The dropdown for choosing a rule’s target bucket can behave unreliably depending on your browser. When the browser is zoomed in significantly, the dropdown has failed to show a usable list or accept typed bucket names; zooming back out restores it. Separately, the same dropdown can appear empty in a smaller browser window, especially once a space has five or more buckets. Enlarging the browser window, or using full-screen, has made the list appear again. If buckets seem to be missing from this dropdown, try these display fixes before assuming the buckets themselves are misconfigured.
Change Impact and How to Revert
Changes to the default bucket, the placement rules switch, the rule list, or the rule order only affect submissions made after the change. Submissions that have already been placed stay where they are. If you need existing submissions checked against your current rules, ask an administrator to reprocess placement for the space.
You cannot delete a bucket while it is the space’s default bucket. Choose a different default bucket first, then remove it.
Permissions
You need the permission your administrator grants for review settings to change the default bucket and placement rules. You need the permission for review buckets to create, edit, or reorder the buckets themselves.
Validation and Errors
| What you see | What it means |
|---|---|
| The Default Bucket: list is empty and settings will not save | This space does not have a bucket yet. Create at least one bucket first |
| The rule table will not save with the switch on | You need at least one bucket assignment rule when the switch is on |
| Bucket id must start with space_id value and : delimiter | The bucket’s identifier must begin with the space’s own identifier and a colon |
Rhythm still accepts an expression rule with a syntax error when you save it. The error appears later, when Rhythm tries to place a submission using that rule. Check a new expression rule against a real submission soon after you save it.
Related
See "Related" in the sidebar for help building the review teams your buckets assign work to, viewing the submissions in your buckets as an administrator, and using rules and expressions elsewhere in Rhythm.