📚 Part of the series Application Building Phase I: Core components

The second step in the application building phase of your Slate application is creating an application round.

You will need to create round(s) if you are importing applications from a third-party or using the Slate-hosted application.

What is an application round?

A round is an application type. For your institution this might mean Undergraduate, Graduate, or some other high-level distinction.

Periods and rounds allow for control over the application process. For example, you can limit the number of applications a person can submit (ex. multiple or just one) per round or per period.

📖 Further reading:

• Learn how periods and rounds work together

• Learn how to create application periods, which are required to have rounds

Best practices for setting up your rounds

When you establish a period and round structure, keep the following in mind:

Less is more

The applicant must select their round at the outset of their application experience. To avoid overwhelming them with options, we recommend operating with as few rounds as possible. This also reduces your year-to-year round maintenance, like the inactivation and creation of new rounds.

If your applicants need clarification about which round to select on the /apply page, use fewer rounds, or only one. Then, you can manage application types at the field level. Manage application term values as an application-scoped field (covered in Creating Application-Scoped Fields and Prompts), not in the round.

Make the applicant’s choice of round obvious to them

In theory, you could make as many rounds as you have application types, reducing the number of conditional fields you’d need in the application; in practice, distinct rounds work best when it is clear to applicants which round they should select. They will be able to see and select a round if it is marked as active.

If an applicant is confused about which round they should choose, take this as a hint that these application types should be represented by a field and prompt selected from within the application itself and not at the round-level.

Let applicants differentiate their applications with custom fields

Use custom fields to represent narrower data.

It makes for a better user experience when applicants can share information through custom fields on custom application page-scoped forms, rather than forcing them to switch application types at the round level.

Data points that identify distinct populations or types of applicants (for example, enrollment term, a program of study, international, transfer, or scholarship qualifiers) can be captured and queried for within the application using custom application-scoped fields on application-page scoped forms and do not require the creation of separate rounds.

Creating an application round

Once you establish a period, you can configure and associate one or more rounds with it.

To create a round:

1. Select Database from the main navigation.

2. Select Application Rounds.

3. Select Insert. A popup appears.

4. Configure the following settings:

   • Status: Inactive

     • Activate the round when you’ve finished testing the application.

     • If you import all applications, the round should always be set to Inactive.

   • Period: Select the active period that you created previously. In the screenshot below, the Period is called Active.

   • Name: Enter a name for your application round, for example: Undergraduate Application

   • Short Name: Optionally enter an internal “short name” that appears as a tab on the applicant’s person record. In this case, 2024 UG.

   • Order: Dictates the order in which rounds appear to the applicant. In this case, 5.

   • Round Key: Use this in application logic, automation, and communications for your application. Enter a year-agnostic code, like UG for Undergraduate.

   • Allow Multiple: Do not allow multiple applications

   • Locked: Unlocked

   • Hidden: Allow applicants to see their applications in this round

   • Protected from Rank: Rankable

     

      

5. Click Save.

🔁 To create a Graduate application round, repeat these steps, changing the Name, Short Name, Order, and Round Key accordingly.

Result

• You’ve created an inactive Undergraduate application round for the active application period that restricts the applicant to a single application per period.

• You may have also created a Graduate application round with the same settings.

Your requirements may differ from the settings we’ve selected here. See the full list of settings below to understand if your setting selections should differ:

Application round setting descriptions

Status

• Required

• Set the status to Inactive until the Slate-hosted application is ready to go live. Rounds that are active are visible and selectable from the /apply page.

• If all applications are being imported, the round should always be set to Inactive.

Folder

• Optional

• Keep your database organized by using folders.

• Select Other to create a new folder.

Period

• Required

• Ties the round to an application period

Name

• Required

• The round name visible to applicants

• Enter a descriptive name, like Undergraduate Application.

Short Name

• Optional

• Visible to internal users only

• Overrides the display name of the round on the application tab of records

Order

• Required

• Integer value that dictates the display order of the application rounds to applicants

Round Key

• Optional

• Enter a short-code that will identify this round type.

• For example, UG for undergraduate and GR for graduate, or ED for early decision and RD for regular decision.

• Use the round key in application logic, automation, and communications for your application.

• Omit year information so you can use the same round key for future rounds

Round Path

• Optional

• Overrides certain shared application files for a particular round

• Use-cases are limited

Deadline (ET)

• Optional, for Slate-hosted applications only

• The date and time (in Eastern Time) after which applications cannot open, edit, or submit applications and their submission fees in this round

• You can set grace periods for fees with the next setting, Payment Grace Period (Days).

• Formatted YYYY-MM-DD H:MM. So, if you want the deadline to be 12:00AM Pacific on 12/15/2026, enter 2026-12-15 3:00.

• Use this setting if the deadline applies to a large group of students, like first-year or transfer applicants, or if your rounds are program- or term-specific, like 2019 Fall First-Year or MBA.

• 📖 Other ways to set application deadlines

Payment Grace Period (Days)

• Optional

• Enter the number of days after your specified submission deadline that you will accept an application fee payment.

• For example, if the application submission deadline is January 1, but you will accept application fee payments through January 15, enter 15 here.

Require Payment to Submit Application

• Optional

• Select Yes to require either payment or a waiver before the user can submit their application.

📖 Further reading: Require Payment to Submit Application

Allow Multiple

• Optional

• Select Allow multiple applications to let applicants submit more than one application to the same round.

• For Slate-hosted applications only

• 📝 Note: The same setting must also be configured on the application period to enable multiple applications per round.

Locked

• Optional

• Unlocked applications allow applicants to switch an application to a different round.  

• Locked applications cannot be moved to another round by the applicant.  

• For Slate-hosted applications only

• If multiple rounds share the same application questions and have different submission deadlines, select Unlocked.

• This configuration allows a potential applicant to change to a round with a later deadline if the original round has passed.

Hidden

• Optional

• Typically used by graduate institutions that refer applicants to other programs.

• Configuring a round as Hidden allows the applicant to not see this extra application during the review process.

• To display the hidden application at a later date, update the application to be in a visible round.

Protected from Rank

• Optional

• When there are more than one of a certain kind of object associated with a record, like applications, test scores, or addresses, Slate uses a set of rules to determine ranks for those objects. This usually comes up in querying, where you only care about the “rank 1” object.

• This setting defaults to Rankable, meaning the application is in the running for the aforementioned table ranking. This ranking determines which application is the highest-ranking, based upon application priority and application creation and submission dates.

• Set standard application rounds (applications for admissions and enrollment) to Rankable.

• Set applications for other items, such as summer high school programs or scholarships, to Do not rank.

• 📝 Note: Applications in rounds set to Do not rank do not appear in the Omni Search.

📖 Further reading: Determination of Table Ranks

Custom Status Portal

• Optional

• This setting overrides the Slate-delivered application status portal if a custom status portal is selected here.

Export Value

• Optional

• Configure up to 5 export values for the application round.

• Typically a short value or code that is used by external systems (such as an SIS) upon the consumption of application data from Slate.

Linking directly to a round

A direct round URL is a link that you can provide to a specific applicant population that prevents them from seeing other application rounds besides the one specified in the link.

When the applicant follows the link to the application management page, they see only one application available for creation, and all other active applications are hidden.

• admission.slate.edu/apply/

  • The default application management page URL you would provide to Slate University applicants who you want to see all active application types.

• admission.slate.edu/apply/?sr=RoundID

  • The direct round URL you would provide Slate University applicants for whom you want see only one specific application type.

Example: Undergraduate and graduate rounds

Say your database includes two rounds, a 2026 Undergraduate application and a 2026 Graduate application.

Rather than giving undergraduate applicants the option to apply to both types of application, you can provide a direct URL to the Undergraduate application.

When the applicant arrives at the application management page from the direct round URL, the only application type they see is the 2026 Undergraduate application.

The same would be true if you would like to hide the undergraduate application from a Graduate applicant, for which you would provide a direct URL to the Graduate application. When the applicant arrives at the application management page, the only application type displayed is the 2026 Graduate application.

Creating a direct round URL

To create a URL that takes applicants directly to a given round:

1. Select an existing round.

2. Set the Status to Inactive.

3. Copy the ID.
   

4. Following this URL format:

   yourschool.edu/apply/?sr=RoundID

   Replace RoundID with the ID of the round record that you copied in the previous step.

5. Use this URL wherever applicants should have access to the application management page.

To test the direct round URL:

1. Open a private browsing window in your browser

2. Paste the URL

3. Apply as a new applicant.

4. Repeat for each application round where you plan to provide a direct round.

➡️ Up next: creating application-scoped fields

You’ve created the large-scale structure that dictates whether applications in your database are active or inactive, and where they fall in the high-level organization of your institution.

Now, you’ll make the application-scoped fields that collect applicant information.

📚 Next article in this series: Application Fields