Admin - Feature Spotlight: Visibility Conditions in Forms

Visibility Conditions allow you to control when questions, sections, or entire pages appear in your forms—based on how someone answers earlier questions or who they are.

While Reviewr has always supported advanced conditional logic behind the scenes, this functionality is now directly available to clients inside the form builder. That means you can independently create smarter, more dynamic forms without needing Reviewr support to configure it for you.

Unlocking visibility conditions gives you more control, cleaner submissions, and a better experience for everyone involved.

Key benefits include:

This is especially powerful for organizations running multiple scholarships, grants, awards, or program tracks within the same event.

Visibility conditions can be applied at the question, section, or page level directly within the form builder.

Here are a few common ways clients are using it:

If an applicant selects “Community Grant”, only the questions related to that grant appear.

Applicants answer a short set of questions, and Reviewr automatically:

Use visibility conditions to:

You can show or hide content based on:

How to get started:

For full tutorials and guides on how to use visibility conditions in forms:

Visibility conditions determine when a question, page, or component should be visible within a form. The form evaluates each condition and displays the element when the result is true, or hides it when the result is false.

Below are the available visibility condition options and examples of when each may be useful:

Always True

This is the default setting. The condition is always true, meaning the question or section will always be visible to all users.

​Example: A general contact information page or introductory text that all applicants should see.

Always False

This condition is always false, meaning the question or section will remain hidden from submitters and reviewers unless the condition is manually changed. This can be used to hide items that are no longer needed or temporarily unavailable.

​Example: A discontinued scholarship section that you want to remove from view without deleting it entirely.

Answer to Choice Question

This condition links visibility to a specific response from a previous multiple-choice question. You’ll select the “powering” question and the specific answer option that should make the current question visible.

​Example: If an applicant selects “Community Grant” on a “Which grant are you applying for?” question, only the questions related to the Community Grant will appear.

Multiple Answers to Choice Question

Similar to the previous option, this condition allows visibility based on multiple selected responses. You can choose one powering question and select several response options that will make the current question visible.

​Example: If an applicant selects “Coaching Program” and “Equipment Grant” from a list of available programs, questions related to both selections will appear.

Type of User

This condition controls visibility based on user type. You can specify which users (Admin, Submitter, Reviewer, Reviewer Manager, or Reviewer System Administrator) should be able to view the question or section.

​Example: You may want to hide the submitter's personal information, so you would only allow submitters and admin to view this question.

Viewed Within a Date Range

This condition makes a question or section visible only during a specified date range. Once the date range has passed, the element will no longer appear to users.

​Example: Display a “Final Submission Confirmation” page only between the application deadline and the reviewer start date.

Event-Level Blindness Settings

This condition applies the event’s global blindness configuration, ensuring that the question or section follows the visibility rules already defined at the event level. It’s useful for maintaining consistency across forms without needing to manually recreate the same visibility logic.

​Example: If your event has a blindness rule that hides organization names across all entries, applying this condition will automatically hide any “Organization Name” field wherever it appears in the form.

Belongs to a Group

This condition allows visibility only for users assigned to a specific group. You’ll select which group has access to view the question, page, or section.

​Example: If your event has multiple categories (e.g., “Student Grants” and “Professional Grants”), you can make category-specific questions visible only to users in the corresponding group.

Form is Submitted

This condition is true when the form has been submitted. It can be used to display follow-up messages or reviewer-only sections that depend on the submission being complete.

​Example: Display a “Post-Submission Review Notes” section that only becomes visible once an applicant has officially submitted their form.

Minimum Word Count

This condition checks the word count of a selected question’s response. You’ll select the question to monitor and specify the minimum number of words required to pass this check.

​Example: Require applicants to write at least 250 words in their essay response before the next section becomes visible.

By unlocking visibility conditions for clients, Reviewr gives you the ability to:

If you’ve ever thought “I wish this question only showed sometimes”—now you can make that happen yourself.