---
title: "Querying for Started (but Not Submitted) Applications"
slug: "applications-started-but-not-submitted-query"
status: "new"
updated: 2026-06-18T22:20:53Z
published: 2026-06-18T22:20:53Z
canonical: "knowledge.technolutions.net/applications-started-but-not-submitted-query"
---

> ## 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.

# Querying for Started (but Not Submitted) Applications

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](/docs/suitcase-import) ID and paste it in **Database → Suitcase Import** to import this query:

```SuitcaseID
6bcb25c3-18f0-4c02-b25c-76f066192942:slate-admissions-showcase
```

> [!NOTE]
> 💡 Tip
> 
> Find this query and other importable examples in the [Admissions Showcase environment](/v1/docs/showcase-environments).

## 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.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Query for applications started but not submitted.png)

## 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.

1. Go to **Queries / Reports**.
2. Select **New Query**.
3. 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
4. Select **Save**.

### Adding joins

Add joins that make applicant and round details available to the query.

1. Select **Join** and create a join to **Lookup Round**.
2. Select **Join** and create a join to **Person**.

### Adding filters

The filters limit the results to active, unsubmitted applications for applicant records.

1. Select **Filter**.
2. Add the **Person / Status** filter.
3. Set **Status:** IN `Applicant`
4. Add the **Submitted Status** filter.
5. Set **Submitted Status:** Not Submitted
6. Add the **Lookup Round / Active Status** filter.
7. 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.

1. Select **Subquery Export**.
2. Configure the following settings:
  - **Name:** `Application is Submitted`
  - **Type:** Dependent subquery
  - **Output:** Existence
  - **Value If Exists:** `Y`
  - **Value If Not Exists:** `N`
3. In the subquery, select **Filter** and add **Submitted Status**.
4. Set **Submitted Status:** Submitted
5. 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.

> [!WARNING]
> 📝 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.