> ## 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.

# Read a Study result

> What each part of the Zoning Analysis tab tells you, and how Urbee shows what it could and couldn't establish.

When a run finishes, open the Study and choose the **Zoning Analysis** tab.
On a wide screen, a rail on the left jumps between sections. Sections with
nothing to show are hidden.

## Verdict

The verdict is at the top:

| Verdict | Meaning |
| - | - |
| ✓ **Permitted** | Allowed as of right |
| ⚠ **Permitted with conditions** | Allowed with conditions or a special approval |
| ⚠ **Requires rezoning** | Not allowed in the current district without a rezoning |
| ✕ **Prohibited** | Not allowed |
| ? **Undetermined** | Urbee couldn't settle it from the cited code and your inputs |

Below the verdict are a short summary, the **District**, the
**Confidence**, and the number of verified **Citations**. **Refine →** opens
the Advisor on that finding.

### Confidence

Confidence shows as **High**, **Medium** or **Low**. It's rated on the
**weakest step** of the run, not the average, because one shaky input makes
the whole read shaky. Click the confidence chip to see which step was
weakest and the scores behind it.

## Findings

* **Risks**: issues to watch. You can mark each one mitigated or accepted,
  or dismiss it.
* **Feasibility**: an overall rating, estimated timeline, conditions, and
  the factors for and against (on "Plan a New Project" runs).
* **District**: the base district the parcel falls in, any overlays, and
  whether the parcel is split across zones.
* **Regulatory Stack**: the federal, state, regional and municipal layers
  Urbee composed for this Site, and the map facts it found for each (see
  below).
* **Use Permission**: why the proposed use is or isn't allowed, with
  citations.
* **Site Regulations**: dimensional standards such as minimum lot size,
  setbacks, height, coverage and FAR, plus any overlay changes.
* **Parking**, **Watershed**: where the jurisdiction has them.
* **Trigger Ledger**: which filings your Program triggers (see below).
* **Permit Pathway**: the filings required, who decides them, why each is
  required, and the estimated critical path.
* **Sources**: every citation behind the result. See
  [What a citation guarantees](/guides/citations).

### The Trigger Ledger

Each row is a filing the town's code may require, marked **Required**,
**Not required** or **Undetermined**. An **Undetermined** row names the input
that would settle it. Enter it with **Settle this**, then **Save & preview**,
and re-run the Study to update the Permit Pathway and Items.

A **Not required** row is only a clean ruling-out when Urbee has verified
every clause of the provision. Where it hasn't, the row says so.

### What "not assessed" means

Urbee is explicit about the limits of what it checked. In the Regulatory
Stack, a layer marked **Urbee has not assessed this layer** or **GIS facts
only — regulatory nexus not assessed** is **not** a finding that its
requirements don't apply. Each layer lists what was searched.

## When Urbee can't cite a value

Urbee never fills a gap with a guess. Instead you'll see:

* **Not found**, with the sources Urbee searched;
* **—** where a code states no figure, with the note the code gives;
* **You entered this** or **From your site file** for numbers you provided.
  They're shown as yours, never as a code requirement.

## If the Program changes

If you edit the Program after a run, a banner says **The Program has changed
since this run** and names the date the results reflect. Click **Re-run** to
bring the Trigger Ledger, Permit Pathway and Items up to date.

## The Items tab

**Items** turns the result into work. Every filing, decision, risk and gap
from the run becomes an item, with authority, due date, owner and
readiness:

| Readiness | Meaning |
| - | - |
| Not ready | A filing that isn't prepared yet |
| Needs attention | An open risk or gap, or a blocked item |
| Ready | The filing's checklist is done, or a qualifying document is linked |
| Filed | In review with the authority |
| Accepted | Resolved |
| Not applicable | Dismissed |

Readiness comes from each item's state; you don't set it by hand. Switch to
**Timeline view** to see dated filings in phases, with the critical path
marked. Items also appear in [My Work](/guides/my-work).