This article focuses specifically on administrators assigning the individuals who can return an application back to an applicant. For an overview of the entire return for revisions process, see this article: Return for Revisions Routing Step Type

Only one revivewer can be assigned to a Return for Revisions routing step per application. 

• A common choice is to have it be the same reviewer for all applications, such as a staff member or committee chair.
• Or, you can assign a specific user who has a direct connection with the application, such as an advisor or director.
• This reviewer can be assigned to a single application (individually) or in batches, both described below.

Note: Applications still need to have been accepted into the review process (status: Accepted) before any reviews can be assigned, including assigning a reviewer to a Return for Revisions step.

Assigning to a Single Application

• From the Data Grid, click the title of the application.
• Click the Reviewers button on the right.
• Find the step you designated as a Return for Revisions Step. 
• Click the Assign Reviewer button.
• Enter the reviewer's email address.
• Enter a Review Deadline. This should be the date that they need to have a decision on whether or not the application needs to be returned for edits.
• Click the Send or Include in Digest button. The language on the button will vary based on where your return step lies in your overall workflow, Send for a first step (A below), Include in Digest for any step after the first (B below).

Assigning in Batches

• From the Data Grid, check the box next to each application you need to assign.
• From the Batch Actions menu dropdown, select Assign Reviewers to Applications.
• In the Select Routing Step dropdown, select whatever you called your Return for Revisions step.
• In the modal that pops up, enter the reviewer's email address.
• Enter a Review Deadline.
• Click Send or Include in Digest. The language on the button will vary based on where your return step lies in your overall workflow, Send for a first step (A above), Include in Digest for any step after the first (B above).

Managing the Process

• Once a reviewer is assigned to a Return for Revisions Step, it will show as in review, either with status Assigned or Reviews Active, depending on other routing step(s) assignment(s).
• If the reviewer chooses to NOT return the application for edits, it proceeds to the next routing step(s), if any.
• If a reviewer chooses to return the application to the applicant for edits, it will show with a special status on the Data Grid: Returned for Revisions (shown below).
• The application will not proceed to any next routing step(s) until it is resubmitted.
• Once the applicant re-submits, the application proceeds to the next routing step (if applicable), and its status becomes either Reviews Active or Reviewed, depending on other reviews that have been assigned and/or completed.

Tip: If an administrator wants to re-submit the application for an applicant so it can proceed to the next routing step(s), they should follow these instructions: Edit or Submit Returned Application as an Administrator

Tracking Submission Dates

• Data Grid - Date Submitted column shows the original (i.e., first) application submission date.
• Excel Reports - Submission Date is the original (i.e., first) application submission date.
• Admin interface - Submission Date is the the original (i.e., first) application submission date.
• Activity Log - Resubmission date(s) will show as entry in log as: "{applicant name} resubmitted an application..."

Have more questions about this topic? Go to the Community Forum to pose the question to other users or submit a support ticket to InfoReady.