Reader Review Forms (Legacy)


The procedures described in this article follow a legacy process. Refer to this article only for general concepts; follow the procedures described in the Workflow Review Forms article when creating review forms. Workflows created using the legacy process cannot be managed using the Workflows (New) tool and vice versa.

Reader review forms are used to capture application ratings and comments during the reading process. Reader Review forms may be associated with a specific bin and will display to the right of the Reader.  Once the form is submitted, it will be associated with the applicant and the form results can be displayed in the Reader.  Multiple forms may be submitted on an applicant.


Configuring a Reader Review Form is a two-step process:

  1. Create a Reader Review Form using the Form Builder.
  2. Associate your Reader Review Form with a Reader Bin.

Create a Reader Review Form

  1. Click Forms in the top navigation bar.
  2. Click New Form.
  3. Enter the following User configurations in the pop-up window:
    • Page Title - The Page Title will display as the name of the form.
    • Folder - Keep forms organized by saving review forms in a Review Forms folder.
    • Status - Set the Status to Confirmed/Active.

On the Form Management screen, click Edit Form to begin building a Reader Review form.

Form Components & Properties Description
Form Fields

Reader Review form fields should only be mapped to system fields in special circumstances. Reader fields mapped to System fields will result in overwritten data, as there is a single value per application. An entry by Reader two will overwrite the entry by Reader one. Use only when appropriate. 


Before adding fields to your Reader Review form, be sure to change the scope of the form to Reader. On the Edit Form screen, click Edit Properties to set the scope.

Default Fields

Always remove the default fields (e.g. First Name) when creating the review form. Reader Review form data is automatically assigned to the applicant. 

Form Fields

Use the Form Builder palette to add questions to the Reader Review Form.

  • Enter a unique field label and export key for every field on the Reader Review Form. This will make it easier to identify and export Reader Review Form data.

    For example, if there are multiple comment fields on the form, give each one a unique label (e.g., Academic Comments, Extracurricular Comments) and a unique export key (e.g., aca_comments, extra_comments). 

Configure the form fields as follows: 

  • Status - Status should be set to Active.
  • Type - Select a compatible format type for your field.
  • Label - Provide a unique label that will display on each field name.
  • System Field - Reader Review forms may be mapped back to a system field or left unmapped. Only select a system field when appropriate. Otherwise, leave this setting blank. 
  • Export Key - If a System Field was selected, the Export Key will pre-populate. If not, provide a unique export key name.
  • Data Type - Select the appropriate Data Type. Note: If the field is storing a numeric value, be sure to select either Int (integer - no decimal) or Real (decimal number). This will allow the use of the value in a calculation on the form and filter on the numeric values.
  • Prompts - If the field is mapped to a system field, the prompts will pre-populate. If not, list the possible values if the field has option values.
  • Default Value - Configure a default value if the form field should display a particular value when the form is opened. 
  • Options - Carefully consider how each Option setting will affect a Reader Review form field:
    • Required - Determine which fields should be required on the review form.
    • Internal Only - This setting is for public-facing forms and should not be used on a Reader Review form field.
    • Read Only - Use this setting for read-only fields that should display (and not update) data from the student record.
    • Hidden - This setting is used for calculated fields.
    • Disabled - This setting is not necessary for a Reader Review form.


Limit the number of required fields and the use of conditional logic on a Reader Review form. Make it easy for a reader to complete the form. Avoid using a Reader Review form to display values.

Associate a Reader Review Form with a Reader Bin

  1. Click Database in the top navigation bar and select Reader Review Forms.
  2. Click Insert.
  3. Enter the following User configurations in the popup window:
    • Show In Bin - Select the Reader Bin where your Reader Review form should appear.
    • Into Bin (optional) - A Reader Review form may display conditionally based on the next bin a reader selects. For example, the review form can display only if the reader selects 'Portfolio Review' as the next bin. 
    • Form - Select the desired Reader Review form to display.
    • Required - Decide if the Review Form is required. A reader will not be able to send an application to the next bin if the Required setting is set to Yes and any required fields on the Reader Review Form are not completed. Note: If No is selected, the Reader Review form will be collapsed in the Reader by default. Any required fields will only be required if the reader elects to display the form.

Configure the Review Form Process

One-to-Many One-to-One Many-to-One

If the same Reader Review Form is used at multiple stages of the reading process, configure the same form to display in multiple bins:


Consider the reading process when configuring the Required setting on Reader Review forms. Forms may not all need to be required to submit responses.

Mapped vs System Fields


Reader fields mapped to System fields will result in overwritten data, as there is a single value per application. An entry by Reader two will overwrite the entry by Reader one. Be careful and use only when appropriate. Mapped fields in a Reader Review Form should be Application or Person scoped.


Remember that all Reader Review Form data is available to query on (including mapped and unmapped fields) by adding Reader Form exports and Reader Form Value filters from the Slate Template Library.

There are three reasons to map to a custom or Slate standard field on a Reader Review Form:

You wish to display Reader Review form fields on the person record
A specific data point on the form is to be used in a calculation

Step I. Create a Reader Review Form

  1. Add a mapped reader rating form field


Step II. Create a second Reader Review Form

  1. Add the mapped reader form field that was added on Reader Review Form 1.
  2. Mark the field as 'Hidden'
  3. Add a second reader rating field
  4. Add a third form field to house the total rating


Reader one form
(as displayed
in Reader)
Reader two form
(as displayed
in Reader)
Review Rating 1
and Reader Rating Total
as 'Read Only'
The most recently submitted data from multiple Reader Review forms should display


Mapping these ratings to a system field can be filtered upon for the most recent rating, regardless of which form set the value.

Was this article helpful?
11 out of 20 found this helpful