--- title: "End-to-end parcel analysis" description: "Walk one address from a map search through a cited zoning and feasibility read to a go/no-go — the full chain in one workflow." last_updated: "2026-08-17" --- This walks one address through Bucky's full chain — parcel facts, local rules, feasibility, and a decision — in one workflow. The goal of this walk isn't to find a good site; it's to make screening cheap enough that killing a weak one costs you an afternoon, not six weeks. ## 1. Screen on the map Open the **Projects map** and search the address, drop a pin, or draw an area. Use **Project Scout** to explore the block and get an early **Site summary** before you commit to anything. See [site exploration](/docs/platform/site-exploration) and [Prompting BuckyAssist](/docs/guides/prompting-buckyassist) for example prompts. If the site summary already looks wrong for what you need — zone doesn't allow the use, lot too small, obvious constraint — stop here and screen the next address. Nothing is saved yet, so there's nothing to clean up. ## 2. Read the parcel If the site clears the first look, open the [parcel](/docs/platform/parcels) read: geometry, dimensions, and the jurisdiction's identifier for the lot. These are the physical facts everything downstream depends on — check the [source status](/docs/resources/citations) if a dimension looks off. ## 3. Read zoning with citations Ask Project Scout **"What can I build here?"** or **"Review zoning"**. Read the permitted uses and the envelope limits (height, setbacks, site coverage, FSR), and check the **status** behind each one — see [Zoning](/docs/platform/zoning#what-you-see). A `cited` limit is traceable to the bylaw; treat anything `unverified_default` or `not_extracted` as a question, not an answer. ## 4. Assess feasibility Ask Scout to **assess development potential**, or open the full [feasibility](/docs/platform/feasibility) panel on your framed site. This is where the parcel's physical facts and the zoning's rules meet the numbers — the step that tells you whether the idea is actually workable, not just allowed. ## 5. Decide: go, no-go, or not yet Three outcomes, all legitimate: - **No-go** — the read disqualifies the site. You've spent an afternoon, not a retainer. Screen the next address. - **Not yet** — the read depends on values that are `unverified_default`, `not_extracted`, or `conditional_unresolved`. Note what needs verification before you commit further — see [Citations and confidence](/docs/resources/citations). - **Go** — use **Review & create** to save the project (if you haven't already), and move to who sees it next. ## 6. If it's a go: bring in the team, then services Decide who needs a seat before you invite anyone — see [people on a project](/docs/platform/people). Once the project has direction, [services](/docs/platform/services) is how you connect it to builders, designers, and architects. If you need to hand the read to a client, lender, or committee, turn it into a deliverable — see [how to read and export a feasibility report](/docs/guides/feasibility-report). Every step above produces decision support, not a permit, appraisal, or legal opinion. The citation status behind each value tells you what still needs human verification. ## Where to go next - [Core concepts](/docs/getting-started/core-concepts) — the vocabulary behind each step. - [First week with your team](/docs/guides/first-week-with-your-team) — the same chain, run by a firm instead of one person. - [Coverage](/docs/resources/coverage) — check before you run this on an address outside a market you already know. ## Sitemap See the full [sitemap](/sitemap.md) for all pages.