> ## Documentation Index
> Fetch the complete documentation index at: https://help.urbee.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Jurisdictions

> Which towns Urbee covers, and how to check a jurisdiction's code version, provisions and updates in the app.

## Where Urbee works today

| Jurisdiction | Code |
| - | - |
| Austin, TX | Austin Land Development Code |
| Brookline, MA | Brookline Zoning By-Law |
| Littleton, MA | Littleton Zoning Bylaw |
| Peabody, MA | Peabody Zoning Ordinance |
| Plymouth, MA | Plymouth Zoning Bylaw |
| Salem, MA | Salem Zoning Ordinance |
| Worcester, MA | Worcester Zoning Ordinance |

In any of these towns you can [start a Study](/guides/run-a-study) and
[compare Sites](/guides/site-screen).

For the Massachusetts zoning towns, Urbee also checks state rules that sit on
top of local zoning, such as MGL c. 40A, and screens state and federal map
layers, including FEMA flood zones.

<Note>
  Code versions change as towns amend their codes, so this page doesn't list
  them. The **Jurisdictions** area in the app always shows the current
  version for each town.
</Note>

## The Jurisdictions area

Open **Jurisdictions** in the sidebar. The **Active** tab lists every town
where you can run zoning Studies, with:

* **Code version**: the version Urbee has verified, with a link to the
  publisher's current page.
* **Corpus**: how many sections of the code are verified in Urbee.
* **Code provisions**: how many of the process facts Urbee tracks for that
  town are covered. Covered means either **cited** or **confirmed absent**,
  where the code has nothing on the point and Urbee shows the sources it
  searched. Each town has its own checklist, so the percentages aren't
  comparable between towns.
* **Stack**: the layers Urbee composes, such as Federal · State · Municipal.

Click a town to open its page:

* **Overview**: a process brief covering who decides what, statutory clocks,
  what you'll need before filing, where the rules live, and where the data
  comes from. **Export PDF** saves it to send to a client. Urbee draws a
  timeline clock only when a statute or adopted regulation states one;
  otherwise it says no deadline is set.
* **Code Provisions**: every process fact, with its evidence. Expand a row to
  see the verbatim citations, or the sources searched for a fact confirmed
  absent.
* **Compare**: two jurisdictions side by side, row-aligned. Gaps show
  **Not curated** rather than being hidden.
* **Updates**: code amendments from the publisher, and every change to
  Urbee's data for the town. An amber **Posted by publisher — not yet in
  Urbee's corpus** tag means the town has published a change that Urbee
  hasn't verified yet.

## Watch a jurisdiction

Click **Watch** (or the bell in the table) to follow a town. You'll get a
notification for each change, and a daily email digest you can turn off
under **Settings → Notifications**. See
[Notifications](/guides/notifications).

## Status words

| Status | Meaning |
| - | - |
| **Codified** | The amendment is reflected in the code Urbee has verified |
| **Pending codification** | Adopted by the town, but not yet in the publisher's code text |
| **Watching** | A known data limit Urbee re-checks at every refresh |
| **Released** | A change to Urbee's own data |

## Need another town?

The **Available to add** tab lists towns whose publishers Urbee can already
read. Use **Request onboarding** on a town, or **Request a jurisdiction** for
any town that publishes on eCode360, Municode or as an ordinance PDF.