End-to-end parcel analysis
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.
This walks one address through Bucky's full chain — parcel facts, local rules, feasibility, and a decision — in one workflow. The goal is a defensible go/no-go on that site before you commit time, fees, or capital.
1. Screen on the map
Open Explore and search the address — or use Drop pin or Draw area from Layers. Read the Framed parcel card: zone, height, setbacks, and overlays, each marked Found, Estimated, or Missing. See site exploration and Prompting BuckyAssist for example prompts.
If the card 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.
Looking for sites rather than checking one address? Start from a saved search instead, then frame the lots that match.
2. Read the parcel
If the site clears the first look, choose Create project on the card. The project's Overview carries the parcel read: lot area, lot dimensions, and the lot number the jurisdiction uses. These are the physical facts everything downstream depends on — check the source status if a dimension looks off.
3. Read zoning with citations
Ask Bucky Assist What can I build here? Read the permitted uses and the
envelope limits (height, setbacks, site coverage, FSR), and check the
status behind each one — see
Zoning. A cited limit is traceable to
the bylaw; a value derived from a cited rule shows the rule it came from;
treat anything unverified_default, not_extracted, or
site_specific_schedule as a question, not an answer.
4. Read feasibility
Read the project's Overview — what Bucky found, Project blockers, Project opportunities, and Next steps — and ask Bucky Assist about anything that matters to your decision. See feasibility. 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, orconditional_unresolved. Note what needs verification before you commit further — see Citations and confidence. - Go — create 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. Once the project has direction, 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.
Decision support, not a permit
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 — the vocabulary behind each step.
- First week with your team — the same chain, run by a firm instead of one person.
- Coverage — check before you run this on an address outside a market you already know.
Last updated on