As a review team administrator, you can use the Portal to move a submission to another review bucket or round, or update its review status. Your space’s settings determine which fields you can change.
Prerequisites
- You must be a review-team administrator, and you must open the submission from your administrator view.
- Your space’s review settings control which fields appear on this page. Moving between buckets, moving between rounds, and setting review status can each be turned on or off separately. If all three are off, the page shows only the submission’s name.
Change the Bucket, Round, or Status
- Open the submission from your administrator submission list.
- Choose Update Review Information.
- Change Review Bucket:, Review Round:, or Review Status:, depending on which fields your space makes available.
- Choose Save Changes.
Result
Rhythm saves your change and returns you to the submission’s administrator view.
Review Status: includes six values: Draft, Submitted, Alternate, Approved, Declined, and Withdrawn. You can choose any value, regardless of the submission’s current status. This field was previously labeled Abstract Status in the Portal, and was renamed to Review Status to make the distinction below clearer.
Review Status is separate from the submission or abstract’s own final status. It shows what your review team recommends, not a decision that takes effect automatically. Staff still need to apply the actual outcome from the Console by changing the submission or abstract’s real status, based on your team’s Review Status. See Change a Submission's Status or Change an Abstract's Status. Members and submitters do not see Review Status; they see only the submission’s overall final status. Because Review Status and the actual status are different fields, changing Review Status here does not trigger acceptance, approval, or decline emails. Those emails are tied to the actual status, which only staff change from the Console.
A Console query’s Review Status filter can offer fewer values than this Portal field. That means a status you set here, such as Approved, may not appear the same way when you filter or output Review Status from a query. If a query’s results do not match what you set in the Portal, check whether the value you need is available in that query’s Review Status options before assuming the status was not saved.
If you expected an approval or decline email after changing Review Status here, remember that Submissions & Reviews uses a different process model from Abstracts. Abstracts has its own approval process, with decision emails tied to the abstract’s actual status. Review Status in this space is only the review team’s recommendation.
Warning
If you move the submission to a bucket your own team does not review, you lose access as soon as you save. The submission disappears from your administrator list because that list only includes submissions in the buckets and rounds your teams cover. The page warns you before a bucket change, but not before a round change, even though moving to a round your team does not cover has the same effect. Make sure you want to move the submission before you save.
Side Effects
Once you can open this page, it does not check your role again. When you save, Rhythm sends the submission’s whole record back, not only the fields you changed. After you move a submission, see Manage Reviewers on Your Team's Submissions if you also need to change who is assigned to it in its new bucket or round.
This page changes one submission at a time. To move many abstracts to a different round at once, run a query and use Bulk Changes › Mass Updates in the Console. Choose the Round field (round_id), not Review Round (review_round_id), because choosing the wrong field can produce a foreign-key error. The same corrective mass update works if you discover that a group of abstracts landed in the wrong round and need to be moved together. For updating many abstracts at once, this Console bulk update is easier than changing them one at a time from the Portal.
To resend an abstract’s approval or decline email without changing anything else, change the abstract’s actual status back to Submitted and save. Then change it again to Approved/Pending Presenter Acceptance or Declined and save. Each save re-triggers the matching email. Do this from the abstract’s own record in the Console, not from this page, because this page changes only Review Status.
If Something Goes Wrong
| What you see | What it means and what to do |
|---|---|
| The bucket, round, or status field is missing | Your space’s review settings do not allow team administrators to change that field here. Ask whoever configures the space to turn on the right setting |
| Unable to save submission | The save failed. Check that you chose a bucket and round that belong to this space |
| A form-errors message names a field you cannot see | A field your space usually hides can still block the save if it has no value. This can happen when a submission has no round at all. Ask whoever configures the space to check the submission’s round |
| The submission disappears from your list after saving | This is expected if you moved it to a bucket or round your team does not cover. Ask an administrator of the new bucket’s team to find it, or use search |
Related
See "Related" in the sidebar for the rest of what a review team administrator can do in the Portal, and for how buckets and placement rules decide where a submission starts out.