The Applications Started but Not Submitted query returns active applicant applications that have not been submitted. Use it to identify applicants who may need reminders, counselor outreach, or other follow-up before an application deadline.
Try a Slate example 💼
Copy this Suitcase ID and paste it in Database → Suitcase Import to import this query:
6bcb25c3-18f0-4c02-b25c-76f066192942:slate-admissions-showcase💡 Tip
Find this query and other importable examples in the Admissions Showcase environment.
Reviewing started applications
Applicants often begin an application before they are ready to submit it. This query helps admissions teams find those in-progress applications so they can understand early funnel engagement and support applicants who may need a timely reminder.
The query focuses on applicant records, active application rounds, and applications where the submitted status is Not Submitted. This keeps the results focused on applications that are still in progress.
Building the query
The query uses the Application base, so each row represents one application record. It joins to the person record for applicant details and to the lookup round for round status.
Go to Queries / Reports.
Select New Query.
Configure the following settings:
Name: Enter a descriptive name, such as
Applications Started but Not Submitted.Folder: Select the folder where the query should be saved.
Type: Configurable Joins
Category: Records
Base: Application
Select Save.
Adding joins
Add joins that make applicant and round details available to the query.
Select Join and create a join to Lookup Round.
Select Join and create a join to Person.
Adding filters
The filters limit the results to active, unsubmitted applications for applicant records.
Select Filter.
Add the Person / Status filter.
Set Status: IN
ApplicantAdd the Submitted Status filter.
Set Submitted Status: Not Submitted
Add the Lookup Round / Active Status filter.
Set Active Status: Active
Adding a subquery export
The imported query includes a subquery export named Application is Submitted. This export returns Y if the application has a submitted status and N if it does not. Because the main query filters for applications that are not submitted, this column usually returns N. Keep it if you want a visible confirmation column, or remove it if the filter is enough for your review process.
Select Subquery Export.
Configure the following settings:
Name:
Application is SubmittedType: Dependent subquery
Output: Existence
Value If Exists:
YValue If Not Exists:
N
In the subquery, select Filter and add Submitted Status.
Set Submitted Status: Submitted
Select Save.
Adding exports
Add exports similar to these so reviewers can identify the applicant, review application context, and confirm whether the application has been submitted. Field names may differ in your database.
Person: Reference ID, Staff Assigned, First, Last, Updated Date
Application: Application Major, Entry Term, Application Round
Subquery export: Application is Submitted
Using the query
Use the query when you need to:
Identify applicants who started an application but have not submitted it.
Create reminder or nudge campaigns for incomplete applications.
Support counselor outreach before deadline-driven application cycles.
Review early funnel engagement and applicant intent.
Customizing the query
After importing the query, adjust it to match your application cycle and outreach strategy. You can:
Add filters for entry term, application round, population, or application type.
Add application start date or updated date filters to focus on recent activity.
Add counselor assignment, territory, source, or region exports for targeted outreach.
Add contact fields if the query will support a communication campaign.
📝 Note
This example assumes standard application submitted status behavior and an applicant person status. Make a copy before editing the imported query, and test changes before using it for production communications or reporting.