# Territory Management

A territory in CurbSight is a defined geographic area — typically one or more zip codes, a city, or a county — that you have built and maintained as your owned prospecting universe. The territory management system is how you organize, build, refresh, and assign territories across your team.

## Building a Territory

Territory build is fast. You enter a zip code (or list of zip codes) and CurbSight:

1. Identifies the county and the relevant GIS endpoint.
2. Queries the county ArcGIS REST API for every parcel in the zip code.
3. Pulls year built, square footage, exterior material, condition, owner name, and assessed value for each.
4. Joins the parcels against the NOAA Storm Events Database for hail/wind/tornado history.
5. Computes the composite score per property.
6. Renders the scored list in your dashboard.

For most US zip codes, this takes under 5 minutes end-to-end. New counties (where the GIS endpoint hasn't been integrated yet) take 1–3 days to add — request them and we will prioritize.

## Territory Refresh

Property data and storm data both change. CurbSight refreshes territories on a configurable cadence:

- **Property data:** Monthly refresh from county GIS (parcel data changes slowly — new construction, sales, value reassessments).
- **Storm data:** Continuous — every NOAA storm event update re-scores affected properties within hours of publication.
- **Imagery:** Refreshed on-demand when a property card is opened (Google Static APIs).

You can manually trigger a full territory refresh from the dashboard at any time.

## Coverage

Currently live (May 2026): Oklahoma counties — Tulsa, Wagoner, Kay, with more added monthly. Every county requires a one-time GIS endpoint integration.

In progress: Texas, Kansas, Missouri, Colorado, Nebraska — the hail-prone Central Plains region where roofing demand is strongest.

Targeted by end of 2026: National coverage of all 50 states. Many states have unified statewide GIS endpoints which makes coverage faster.

If your county is not yet supported, contact sol@curbsight.io. We will add it to the queue and notify you when it goes live.

## Territory Limits by Plan

- **Starter — 3 territories.** Typically 3 zip codes or one mid-sized city.
- **Pro — 10 territories.** A metro area or several counties.
- **Enterprise — Unlimited.** Multi-state operations.

A "territory" is a single defined geographic area. There is no hard property cap on a territory — a small rural zip might have 800 properties; a dense suburban zip might have 8,000. All count as one territory.

## Per-Rep Territory Assignment

On Pro and Enterprise, you can assign territories to specific users on your team. Reps see only their assigned territories in the dashboard. This is critical for:

- Multi-rep teams where each rep has a defined service area
- Franchise operations with multiple locations
- Lead-routing fairness (no two reps working the same block)

Assignment is managed from the admin dashboard.

## Admin Dashboard

The admin dashboard (Pro and Enterprise) gives the owner or manager a top-level view of:

- All territories across the team
- Properties scored, leads worked, conversion rates per territory
- Data freshness per territory (last refresh date)
- Per-rep activity and pipeline

This is where operations leadership lives during the day.

## What's Coming

- Self-service zip code ordering (drop in a zip → territory builds in real-time, no support ticket)
- Territory waitlist and priority queuing for new counties
- Bulk territory import for franchise operations
- Cross-territory route planning

## See Also

- [Property Intelligence Dashboard](./dashboard.md)
- [Interactive Map](./map.md)
- [Pricing](../pricing.md)
- [How Property Scoring Works](../scoring.md)