Querying for Applicants by School

You can query for applicants by school to understand where applications are coming from and how different high schools contribute to your admissions pipeline. Use this information to support counselor outreach, school visit planning, territory strategy, and school-based funnel reporting.

Try a Slate example 💼

Copy this Suitcase ID and paste it in Database → Suitcase Import to import this query:

f1d21f6c-1659-41bd-893a-09bc71b6842a:slate-admissions-showcase

💡 Tip

Find this query and other importable examples in the Admissions Showcase environment.

Reviewing applicants by school

School-based applicant reporting helps admissions teams see where students are coming from and compare activity across high schools. You can use this approach to review applicant names, application statuses, intended academic interests, and school location details in one result set.

The example focuses on applications in active review or decision stages. It joins each application to the applicant person record and related school information so each row includes both applicant and school context.

Building the query

Use the Application base so each row represents one application. Join to the person record for applicant details, then join to school information for high school context.

1. Go to Queries / Reports.

2. Select New Query.

3. Configure the following settings:

   • Name: Enter a descriptive name, such as Applicants by School.

   • 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, address, and school details available to the query.

1. Select Join and create a join to Person.

2. Select Join and create a join to Person / Address by Rank Overall.

3. Set Rank: 1

4. Select Join and create a join to Schools.

Adding filters

The status filter keeps the results focused on applications that are still active in the admissions process or have reached a decision stage.

1. Select Filter.

2. Add the Status filter.

3. Set Status: IN Awaiting Payment, Awaiting Materials, Awaiting Decision, Awaiting Confirmation, Decided

If each staff member should review only their assigned applicants, add the Person / Staff Assigned filter and set Staff Assigned: IN Current User.

Adding exports

Add exports similar to these so reviewers can identify the applicant, review application context, and compare school details. Field names may differ in your database.

• Person: Staff Assigned, First, Last, Entry Term, Prospective Major

• Application: Status

• Schools: Name, City, Region, Country

Using the query

Use the query when you need to:

• Analyze application volume by high school.

• Support school-based outreach and counselor follow-up.

• Review application statuses across source schools.

• Plan travel, school visits, or territory coverage.

• Identify high schools that may need additional engagement.

Customizing the query

After importing the query, adjust it to match your reporting and recruitment strategy. You can:

• Add entry term, application round, or application type filters to focus on a specific applicant cohort.

• Add school region, country, state, CEEB code, or school type exports for more detailed school analysis.

• Change the status filter to compare submitted, incomplete, admitted, or deposited applications by school.

• Add counselor assignment, territory, or visit-history fields to support travel planning.

📝 Note

This example assumes standard application statuses and school records connected to applicant person records. Make a copy before editing the imported query, and test changes before using it for production reporting or outreach.