The Alumni Interviews query returns application records with assigned alumni interviewers. Use it to review interviewer assignments, monitor alumni volunteer participation, and identify applications that may need follow-up during the interview process.
Try a Slate example 💼
Copy this Suitcase ID and paste it in Database → Suitcase Import to import this query:
0874e3c7-676d-4f87-b726-16906f59cc3d:slate-admissions-showcase💡 Tip
Find this query and other importable examples in the Admissions Showcase environment.
Reviewing alumni interviews
Alumni interviewing processes often depend on several connected pieces: application records, person records, school details, and a custom dataset that stores alumni volunteer information. This query brings those details together so admissions teams can see who is participating in the interview process and which applications are associated with each interviewer.
The query can help teams coordinate outreach, monitor interviewer engagement, and review coverage across schools or regions. It can also serve as a starting point for a more focused assignment, training, or follow-up list.
Building the query
The query uses the Application base, so each row represents one application record. It joins to the person record, primary school, rank-one application, and the alumni volunteer dataset row connected to the application.
Go to Queries / Reports.
Select New Query.
Configure the following settings:
Name: Enter a descriptive name, such as
Alumni Interviews.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 person, school, application, and alumni volunteer details available to the query.
Select Join and create a join to Person.
From the Person join, create a join to School by Rank Overall. Name the join
School 1and set Rank:1.From the Person join, create a join to Application by Rank. Name the join
Application by Rankand set Rank:1.Create a join from the application to the related dataset row field that stores the assigned alumni interviewer. In the imported example, this join is named
Applicant Interviewer - Alumni Volunteers.
Adding filters
The active filter limits the results to records where the assigned alumni volunteer is active.
Select Filter.
Add the Applicant Interviewer - Alumni Volunteers / Active Status filter.
Set Active Status: Active
The imported query also includes inactive filters that can be activated when needed:
Person / Staff Assigned: IN
(Current User)Person / Status: IN selected person statuses
Application by Rank / Status: IN selected application statuses
Adding exports
Add exports similar to these so reviewers can identify the applicant, school, application status, assigned staff member, and alumni interviewer. Field names may differ in your database.
Person: Person Reference ID, Name, Person Status, Staff Assigned
School 1: School, School City, School State
Application: Application Major, Application Status
Applicant Interviewer - Alumni Volunteers: Alumni Volunteer, Alumni Interview Role
Using the query
Use the query when you need to:
Review active alumni interviewers and the applications assigned to them.
Monitor interviewer participation during the application cycle.
Identify coverage gaps by school location, region, or staff assignment.
Build a focused communication or follow-up list for alumni interview coordination.
Customizing the query
After importing the query, adjust it to match your alumni interviewing process. You can:
Replace the alumni volunteer join with the related dataset row field used in your database.
Add or activate filters for assigned staff, person status, application status, entry term, round, or region.
Add contact information for alumni volunteer outreach.
Add geographic fields to support regional assignment or coverage review.
📝 Note
This example assumes your database has an alumni volunteers custom dataset and an application-scoped related dataset row field that connects applications to alumni volunteer records. Make a copy before editing the imported query, and test changes before using it for production communications or reporting.