---
title: "Querying for Territory Activity"
slug: "querying-for-territory-activity"
status: "new"
updated: 2026-06-18T20:18:55Z
published: 2026-06-18T20:18:55Z
canonical: "knowledge.technolutions.net/querying-for-territory-activity"
---

> ## 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 Territory Activity

You can query for territory activity to review the people in a territory, where they are located, where they attend school, and the status of their first application. This kind of query can help counselors prioritize follow-up, compare activity across geographic markets, and prepare territory-level pipeline reports.

#### 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
271ced23-da3d-47af-a01d-a457f6dc529b:slate-admissions-showcase
```

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

## Reviewing territory activity

This query starts from the Person base and adds related address, school, and application information. The result is one row per person, with columns that help you review a territory list without opening each record.

The example includes exports for reference ID, name, person status, email, primary address city and state, school name, geomarket, prospective major, entry term, application major, and application status. Your database might use different field labels or territory structures, so choose equivalent local fields when you rebuild the query.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Querying on territory activity.png)

## Building the query

### Creating the query

1. Go to **Queries / Reports**.
2. Select **New Query**.
3. Configure the following settings:
  - **Name:** Territory activity
  - **Folder:** Select the folder where the query should be saved.
  - **Type:** Configurable Joins
  - **Base:** Person
4. Select **Save**.

### Adding joins

Add joins to bring the person's primary address, first application, and first school into the query. These joins make territory, school, and application columns available for exports and optional filters.

1. Select **Join**.
2. Create a join to **Address by Rank Overall**.
3. Name the join **Address by Rank Overall**.
4. Set **Rank** to **1**.
5. Select **Save**.
6. Select **Join**.
7. Create a join to **Application by Rank**.
8. Name the join **Application 1**.
9. Set **Rank** to **1**.
10. Select **Save**.
11. Select **Join**.
12. Create a join to **School by Rank Overall**.
13. Name the join **School 1**.
14. Set **Rank** to **1**.
15. Select **Save**.

### Adding optional filters

The example query includes inactive filters that can be activated when you want to narrow the territory view. Leave these filters inactive if you want a broad review list, or activate the filters that match your reporting goal.

#### Staff Assigned

1. Select **Filter**.
2. Under **Person**, select **Staff Assigned**.
3. Select **Continue**.
4. Set the filter to `IN`.
5. From the list, select **Current User**.
6. Set **Status** to **Inactive** if this filter should remain optional.
7. Select **Save**.

#### Person status

1. Select **Filter**.
2. Under **Person**, select **Status**.
3. Select **Continue**.
4. Set the filter to `IN`.
5. Select the person statuses that should appear in the query results.
6. Set **Status** to **Inactive** if this filter should remain optional.
7. Select **Save**.

#### Geomarket

1. Select **Filter**.
2. Under **Address by Rank Overall**, select **Geomarket**.
3. Select **Continue**.
4. Set the filter to `IN`.
5. Select the geomarkets that should appear in the query results.
6. Set **Status** to **Inactive** if this filter should remain optional.
7. Select **Save**.

### Adding exports

Add exports that help reviewers identify the person, understand where the person is located, and see the person's application context. The exact labels in your database might differ.

- **Person exports:** Reference ID, First, Last, Status, Email, Prospective Major, and Entry Term.
- **Address by Rank Overall exports:** City, Region or State, and Geomarket.
- **School 1 exports:** Name.
- **Application 1 exports:** Application Major and Status.

After adding the joins, filters, and exports, select **Preview Results** to confirm that each person appears with the expected territory, school, and application details.