--- title: "Querying for Applications Missing Parent or Guardian Information" slug: "querying-for-applications-missing-parent-or-guardian-information" status: "new" updated: 2026-06-18T22:05:32Z published: 2026-06-18T22:05:32Z canonical: "knowledge.technolutions.net/querying-for-applications-missing-parent-or-guardian-information" --- > ## 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 Applications Missing Parent or Guardian Information You can query for applications that do not have a parent or guardian relationship on the applicant record. Use this approach to identify records that need follow-up before review, communication, or enrollment workflows depend on family or guardian information. #### Try a Slate example 💼 Copy this [Suitcase](/docs/suitcase-import) ID and paste it in **Database → Suitcase Import** to import a pre-made example query: ```SuitcaseID 96a35ace-9a32-4090-986a-8307c196b99e:slate-admissions-showcase ``` > [!NOTE] > 💡 Tip > > Find this query and other importable examples in the [Admissions Showcase environment](/v1/docs/showcase-environments). ## Finding applications missing parent or guardian information This query starts from the **Application** base so each row represents an application. It then joins to the applicant record and the application round, limits results to active rounds for applicants, and uses a subquery filter to find applicant records with no related person categorized as a parent, step-parent, or legal guardian. Results can help admissions teams identify records that need data cleanup, applicant follow-up, or additional family information before downstream processes depend on those relationships. ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Querying for Applications Missing Parent or Guardian Information.png) ## Building the query ### Create the query 1. Go to **Queries / Reports**. 2. Select **New Query**. 3. Configure the following settings: - **Name:** Applications Missing Parent or Guardian Information - **Folder:** Applications - **Type:** Configurable Joins - **Base:** Application 4. Select **Save**. ### Add joins Create the joins that make round information and applicant-level fields available to the query. 1. Select **Join**. 2. Create a join to **Lookup Round**. 3. Select **Join**. 4. Create a join to **Person**. ### Add the parent or guardian subquery filter The subquery filter is the core of this query. It checks the applicant's related person records and returns only applications where no relation has a type in a parent or guardian category. 1. Select **Subquery Filter**. 2. Configure the subquery to look for relation records from the **Person** join. 3. Add a filter for the relation type category: - **Category:** Legal Guardian, Parent, Step-Parent 4. Set the subquery condition to **Not Exists**. 5. Name the filter **Parent/Guardian Relation category**. ### Add filters Add filters that keep the results focused on applicant applications in active rounds. 1. Select **Filter**. 2. Add the following filters: - **Person / Status:** Applicant - **Lookup Round / Active Status:** Active ### Add exports Add exports similar to these so the results give staff enough context to review and follow up on each record. Export names and field labels may differ by database. - **Person Reference ID** - **Person Staff Assigned** - **Person First** - **Person Last** - **Person Entry Term** - **Application Round** - **Person Status** ## Using the query Run the query to review applications that do not have a parent or guardian relation on the applicant record. These records may need applicant outreach, family contact updates, or relationship cleanup before communications or review processes use parent or guardian data. ## Customizing the query - Add an entry term, application round key, or application cycle filter to focus on a specific cohort. - Add application status filters if you only need submitted, incomplete, or active applications. - Add exports for email, phone, mailing address, or staff assignment if the results will support outreach. - Adjust the relation categories if your database uses different categories or relation type conventions for parents and guardians. - Add age, student type, or population filters if parent or guardian information is required only for certain groups. > [!WARNING] > 📝 Note > > Test the query before using it for production communications. Parent and guardian requirements vary by institution, population, and local data-entry practices.