When a reviewer responds with a rejecting response, the item doesn't advance on its own. It moves to Pending submittal manager action and waits for a decision from the submittal manager. This article covers the three decisions and what each one does.
A rejection, and the decision made in response to it, both become part of the submittal record. Choose the option that reflects what you intend to happen to the item.
Who can do this
Access level required: Manager.
Applies to: GC internal users acting as the submittal manager on the item.
Not available to: Viewer and Coordinator access levels, or portal users.
Prerequisite: the item is in Pending submittal manager action.
How an item gets here
An item moves into this status when a reviewer applies a rejecting response, for example Rejected As Noted, Revise and Resubmit, or Not Required (your company sets the names). The item's court moves to the submittal manager, a Submittal rejection notification is sent to them, and the log shows View Rejection in the Status column.
Your three options
Step 1: Open the item. On the rejected review step, click Actions.
Step 2: Choose one of the options below.
Send back to submitter
Use this when the item should be revised and resubmitted.
Click Actions > Send back to submitter.
Enter a Reason (required). Add a New due date if you want one.
Click Send Back.
The Revisions required notification is sent to the submitter when you send the item back. It isn't sent when the reviewer rejects the item, so the submitter doesn't know a revision is needed until you send it.
On the Submission step, the item shows Revision required with your reason. Every file from the rejected revision moves to Rejected Documents, with the final document first. This includes revised files a reviewer uploaded, the files they superseded, and the original submission.
Reject and cancel
Use this when the item is no longer needed or shouldn't be resubmitted, including when a reviewer responded that it isn't required.
The item is cancelled. Its document receives a Cancelled watermark, the item becomes read-only, and everyone who had access keeps view-only access. See RedTeam Flex - New Submittals: Cancel and Restore Items.
Move to next workflow step
Use this when you need another reviewer's input, or when you have decided to proceed past the rejection. You must enter a reason, which is recorded with the item and shows in History.
What happens next
Send back to submitter: the item returns to the submitter for revision. The submitter sees the status Pending revisions and a View Rejection button in the RedTeam Portal.
Reject and cancel: the item moves to Cancelled and an Item cancelled notification is sent to everyone who had access.
Move to next workflow step: the item advances to the next step and your reason is recorded with the item.
Things to know
An inactive submittal manager blocks the item. If the submittal manager on the item becomes inactive before taking action, the item's status changes to Blocked and the Court column shows the submittal manager with a notice that the person is inactive. Assign an active submittal manager to clear the block.
Submitters can't replace their own documents. Once a submitter confirms a submission, they can't swap the files. A RedTeam Flex user has to send the item back for revision. Expect submitters to contact you when they notice they submitted the wrong file.
Moving to the next step doesn't erase the rejection. The reviewer's response stays on the item's record.
Reviewer feedback reaches the submitter through the document viewer. A submitter opening a rejected item sees the reviewer's feedback there, and can comment and mention the submittal manager or the reviewer with questions.