Workflow Review Forms

Workflow Review Forms are used to capture ratings, evaluations, and comments during the reading process. These forms appear within the Reader and are associated with a specific workflow bin.

When a form is submitted, the responses are stored with the record and can be referenced later in the Reader or through queries. Multiple review forms may be submitted for a single record depending on your workflow design.

While commonly used for application review, Workflow Review Forms can also support other evaluation processes across your workflow.

Try a Slate example 💼

Copy this Suitcase ID and paste it in Database → Suitcase Import to import a pre-made example Reader Review Form:

2b143ead-0ef9-4317-a4d8-0715c8b7801d:slate-admissions-showcase

Configuring a Workflow Review Form

Setting up a Workflow Review Form involves two main steps:

Create the form using the Form Builder
Associate the form with a workflow bin

Step 1: Create a Workflow Review Form

Navigate to Forms in the top navigation
Click New Form
Configure the form:
- Page Title: This is the name displayed in the Reader
- Folder: Store forms in a dedicated Review Forms folder for organization
- Status: Set to Confirmed/Active
From the Form Management screen, click Edit Form to begin building

Configure Form Properties

Before adding fields, update the form’s scope:

Click Edit Properties
Set Scope to Reader Review Form (Applications, Person, or Dataset depending on what type of record you are viewing in the Reader)

Default Fields

Remove any default fields (such as First Name).
Review form data is automatically tied to the record and does not require identifying fields.

Add and Configure Form Fields

Use the Form Builder palette to add fields to your form.

Field Setup Guidelines

Provide a unique label and export key for every field
Use descriptive naming when multiple similar fields exist
- Example:
  - Academic Comments → aca_comments
  - Extracurricular Comments → extra_comments

Field Configuration

For each field:

Status: Active
Type: Select the appropriate field type
Label: Clear, descriptive field name
System Field:
- Leave blank in most cases
- Only use when intentionally writing back to a single-value system field
- ⚠️ Multiple readers will overwrite each other if mapped to the same system field
Export Key:
- Auto-populates if mapped to a system field
- Otherwise, enter a unique key
Data Type:
- Use Int or Real for numeric values
- Required for calculations and numeric filtering
Prompts:
- Required for fields with selectable options
Default Value:
- Optional starting value for the field

Field Options

Required: Use sparingly—only for essential inputs
Read Only: Display data without allowing edits
Hidden: Commonly used for calculated fields
Internal Only / Disabled: Not typically used for review forms

✨ Tips
Keep review forms simple and efficient.
Limit required fields and avoid heavy conditional logic so readers can complete evaluations quickly.
Workflow Review Forms are best used for capturing input—not displaying large amounts of data.

Step 2: Associate the Form with a Workflow Bin

Navigate to Database → Workflows
Select the Workflow you with to add the Review form to
Click the Review Forms tab
Click the pencil icon on the right side of the page
Drag and drop the Review Form widget to the bin on the right
- Show In Bin: Select the bin where the form should appear - click Show in Other Bins if more than one bin is needed
- Into Bin (optional):
  - Display the form only when routing to a specific next bin
  - Example: Show only when selecting Portfolio Review
- Review Form: Select the review form
- Required:
  - Yes: Must be completed before moving the record
  - No:
    - Form is collapsed by default
    - Required fields only apply if the reader opens the form
- Filters
  - Use filters to determine which records in your bin should display the Review form

Configuring the Review Form Process

Your workflow design determines how forms are used across bins.

One-to-Many

Use the same form in multiple bins

Ideal when the same evaluation criteria applies at different stages

One-to-One

Use different forms for different binsa

Best when each stage requires unique questions or scoring

Many-to-One

Use multiple forms in a single bin

Useful when multiple perspectives or evaluation types are needed at the same stage

Final Considerations

When deciding whether a form should be required, consider the reader experience and your process flow. Not every form needs to be required in order to capture meaningful feedback.