Understanding Submitter Fields vs. Submission Fields
When building forms in Reviewr, it is important to understand the difference between Submitter fields and Submission fields. Although they may appear similar, they serve very different purposes within the platform.
For best results, all forms in Reviewr should utilize Submitter fields, the Submission Name field, and the Submission Company field. Understanding the difference between Submitter fields and Submission fields helps administrators better identify, organize, search, and manage submissions throughout the review process.
Submitter Fields
Submitter fields are tied directly to the user account created in Reviewr. These fields store information about the individual submitter themselves.
Common Submitter fields include:
Submitter Name
Submitter Email
Submitter Phone
Submitter Address
Submitter's Birthday
Submitter's Organization
When a submitter enters information into these fields, that information becomes associated with their Reviewr account and can automatically populate in future submissions or forms where the same fields are used.
For example:
The Submitter Name field pulls from the first and last name entered during account creation.
The Submitter Email field pulls from the email address used to create the account.
Because these fields are account-based, they are designed to represent the person submitting the application, not the application itself.
The Submitter Name also displays within the Manage Submissions table, helping administrators identify who submitted each application.
Submission Fields
Unlike Submitter fields, Submission fields are tied to the individual submission record itself rather than the user account.
There are three Submission fields available in Reviewr:
These fields are intended to help identify the actual submission, project, organization, nomination, or entry being submitted.
This distinction is important because Submitter fields and Submission fields are not the same thing.
Submitter fields identify the person submitting.
Submission fields identify the submission itself.
This becomes especially important for programs where submitters may submit on behalf of a team, organization, nominee, business, or project.
Submission Name
The Submission Name field is one of the most important identifiers within a submission and is highly flexible.
Depending on the type of program being managed, the Submission Name can represent many different things, including:
Applicant name
Nominee name
Team name
Project title
Competition entry
Grant proposal name
Research title
For scholarships or simple applications, the Submission Name is often set to match the Submitter Name. However, for grants, competitions, fellowships, awards, or calls for entries, it is often more useful to use a descriptive title that helps administrators quickly identify the submission.
The Submission Name displays throughout the platform, including within the Manage Submissions table.
Submission Company
The Submission Company component is another important Submission field.
This field displays within the Manage Submissions table under the Organization column and can be used in many different ways depending on the needs of the program.
Common uses include:
Organization or company name
Current school
College or university applicant plans to attend
Department or institution
Team or group name
Program affiliation
Despite the name “Submission Company,” this field does not need to represent a company specifically. It can be used however needed to provide additional identifying information for administrators and reviewers.
Best Practice
Using the Submission Name and Submission Company fields strategically can make submission management significantly easier for administrators and reviewers.
Because both fields display prominently within the Manage Submissions table, they are valuable tools for helping teams quickly identify, organize, search, and filter submissions throughout the review process.
I prefer this response

