---
title: "Setting Application Deadlines"
slug: "deadline-management"
description: "Manage application deadlines in Slate using round settings, conditional logic in application pages, and submission requirements to ensure timely and organized application processes for different student groups and programs."
tags: ["Applications", "Rounds"]
updated: 2026-05-26T15:35:00Z
published: 2026-05-26T15:35:00Z
canonical: "knowledge.technolutions.net/deadline-management"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Setting Application Deadlines

> [!NOTE]
> 📚 Part of the series **Application Building Phase I:**[**Core components**](https://knowledge.technolutions.net/docs/application-building-checklist#phase-1-core-components)

There are five options for managing application deadlines in the [Slate-Hosted Application](/v1/docs/introduction-to-the-slate-hosted-application):

1. **On the round:**A setting on the round can set the same deadline for all applications within that round.
2. **On the application page:**A combination of form-based prompt logic, Conditional Logic, and application logic offers more control.
3. **In prompts:**Set individual prompts to expire with prompt expiration dates.
4. **With submission requirements:**Similar to the previous option, create application logic that requires prompts not be expired.
5. **With translation codes:**For when your Slate-Hosted Application has some combination of the following:
  - Multiple deadlines (more than 15)
  - Frequent program-wide deadline extensions
  - Deadlines are determined based on at least three prompt-based fields (program, entry term, campus, full-time/part-time status, online/in-person instruction, etc.)
  - Slate-Hosted Application is live and accepting applications year-round

Which option you choose will depend on the nuances of your application.

## Option 1: Setting deadlines at the round level

For the Slate-hosted application only, a deadline can be configured on an application round. If a deadline is set, applications in the round cannot be opened, edited, or submitted by the applicant after this date and time. The deadline also applies to the application fee.

> [!NOTE]
> 💡 You can set a [grace period](/v1/docs/creating-application-rounds#payment-grace-period-days) to let applicants submit fees beyond the deadline for application submission. If left blank, this grace period defaults to 1 day.

Setting a deadline on the round works well if there is a broad-based deadline for a large group of students, such as first-year or transfer applicants, or if rounds are program or term specific, such as *2019 Fall First-Year* or *MBA*.

📖 [Creating rounds](/v1/docs/creating-application-rounds)

To set a deadline on a round:

1. Go to **Database** → **Application Rounds**.
2. Select the round to be edited.
3. **Deadline (ET)** - Enter the date and time of the application deadline.

[![Rounds Popup](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/exz5atrfuejydvahhnz0wmceclip0.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/exz5atrfuejydvahhnz0wmceclip0.png)

## Option 2: Creating conditional logic on the application page

You can present different programs of study and entry terms using **conditional logic**on a custom application page.

Using **prompt conditions**, you can set program deadlines. Applicants will see different entry terms based on the program of study or major they select. Prompts using this conditional logic only appear if the specified date hasn’t yet passed.

To configure a deadline via prompt conditions:

1. Go to **Forms**.
2. Select an existing Slate-hosted-application-scoped form, or [create a new one](/v1/docs/creating-a-custom-application-page).
3. Select a form field you want to configure with prompt conditions.
4. Select **Edit Prompt Conditions.**
5. Select **OK**.
6. Select the prompt (or prompts) on which to add filters.
7. Select **Filter**.
8. Select **Current Date**.
9. Set the operator to `<`.
10. Enter the deadline for the selected prompt, such as `01/02/2026`.

[![Prompt Conditions Current Date Filter](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/rpeaupza9eiinnbfkodgwmceclip1.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/rpeaupza9eiinnbfkodgwmceclip1.png)
11. Select **Save**to save the prompt logic.
12. Select **Save**to save the form field.

> [!NOTE]
> 💡 Tip
> 
> To display a prompt within a set date range, add the *Current Date*filter a second time, and set the operator to `>` the first available date. Following the previous example, adding a filter for `Current Date > 07/31/2026` displays the prompt only between August 1 and January 1.

## Option 3: Submission requirements

To enforce deadlines at the point of application submission, use similar logic as outlined above, but instead create hard fail submission requirements in the Application Logic tool for each prompt value.

📖 [Submission requirements](/v1/docs/submission-requirements)

## Option 4: Prompt effective & expiration date/time settings

Prompts can also be configured with Effective Date/Time and Expiration Date/Time values to specify when a prompt should appear in ANY form or application page where it is being used.

> [!WARNING]
> 📝 Effective Date/Time and Expiration Date/Time are set in Eastern Time.

1. Select **Database** on the top navigation bar
2. Select **Prompts**.
3. Select the prompt on which an effective date and/or expiration date will be set.
4. Configure the following:
  - **Effective Date/Time** - Set the date on which the prompt should become available.
  - **Expiration Date/Time** - Set the date on which the prompt should become unavailable.

[![Prompt Conditions Current Date Filter](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/160xgqrssekh6k9kyhzjwmceclip2.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/160xgqrssekh6k9kyhzjwmceclip2.png)

## Option 4: Translation codes

Translation codes transform a target value into an export value. They can be used to enforce application deadlines. See [enforcing application deadlines with translation codes](/v1/docs/enforcing-application-deadlines-with-translation-codes) for a detailed breakdown.

Similar to Liquid Markup, Conditional Logic allows text or images to be displayed or hidden based on defined criteria.