Drop a pin or paste a property. Bucky resolves the parcel, zone, overlays, and lot facts from local sources — not a generic summary.
Permitted uses, setbacks, height, coverage, parking, and the likely approval path, with citations attached. If the site does not work, you find out here.
Save the site. Ask BuckyAssist in that project's context. Carry cited facts into a report or memo for the next person who has to decide.
Using Bucky with your team
The same file carries the site from first look through entitlement and team formation. Start with one champion and one address. Parties join as the work needs them — not all at once. Bucky is the pre-development record, not the construction job site.
The champion signs in, picks an address the team already knows, and keeps the analysis in a project.
Parcel, zoning, overlays, and the likely path — cited. If the site does not work, you find out here, not in a kickoff meeting.
Send a viewer invite or a share link to the person who needs to see it. Track everyone else without giving them a login.
Do not staff the whole deal on day one. The project stays the sourced record; people attach when that stage actually needs them.
| Stage | What you do in Bucky | Who you add |
|---|---|---|
| Screen | Scout addresses, compare options, kill weak sites early. | Champion only. No parties yet. |
| Go / no-go | Save a project. Read zoning, overlays, and feasibility with citations. | Share a viewer with a client or principal if they need to see the live read. |
| Definition | Scenarios, envelope, program, assumptions — kept on the same project. | Colleagues who will work in Bucky. Track the owner as a stakeholder. |
| Entitlement | Approval path, cited memos, and the open questions for the next hearing. | Planner, neighbours, council contacts as stakeholders. Do not give the city a seat. |
| Team formation | Link the firms you may hire. Find services when you are ready to build. | Partner companies (no login). A workspace only if they will work in the file. |
| Toward shovel-ready | The project remains the record of facts, assumptions, and decisions. | No new roster. Construction execution is not Bucky. |
| This person | What to do |
|---|---|
| A colleague who will run analysis | Add them to the project team (contributor or admin). |
| A client or principal who needs to see the site | Invite as a viewer, or send a share link. They see the workspace; they do not run it. |
| A planner, lender, or neighbour you are tracking | Add as a stakeholder. No login. No seat. |
| An architect or builder you may hire | Link them as a partner company. Give them a workspace only when they need one. |
| The whole office on day one | Do not. One live project first. |
Week 1: one project on an address you know. Week 2: one internal invite if someone else will work in Bucky. Add seats when sharing is habitual — not before.
Bring an address your team is evaluating. We'll walk the same path: site facts, feasibility, and what you'd share next.
Book a demo