You find a site that pencils, then lose an hour flipping between the code, your sketch, and a scratch pad to see if it fits. Height, FAR, density, setbacks, parking. Each lives in a different section, with its own definitions and traps. Most teams run a quick sanity check before they spend real time on design or call counsel. The snag is that "quick" rarely is, and it is easy to miss a constraint or misread a table. Due Diligence ~10 min to run Assess Zoning Feasibility Vic prompt Use Vic to assess zoning feasibility for a proposed 5-story multifamily building with 80 units on a 1.2-acre downtown parcel. Purpose A 60-minute manual zoning review is reduced to roughly 10 minutes, allowing faster go/no-go decisions on sites under consideration. Inputs Property Address Required Proposed Development Required Outputs A table listing each constraint with allowed limits, proposed requirements, status, and math shown, plus a plain-English bottom-line statement and any flags. Time saved Turns roughly an hour of manual work into about ten minutes. How it works Give Vic two things: the property address and a plain description of what you want to build. That can be as simple as use, stories, unit count, and any basics you have on the program. Then run: "Use Vic to assess zoning feasibility for a proposed 5-story multifamily building with 80 units on a 1.2-acre downtown parcel." The task checks your proposal against six core constraints: permitted use, height, floor area ratio, density, setbacks, and parking. It returns a table with each constraint, the allowed limit from the code, your proposed figure, and the math tying them together. Each line is labeled Pass, Fail, or Flag so you can scan it in seconds. You also get a one-sentence bottom line that says whether the concept clears zoning as proposed, plus any flags that need a closer read. The output includes a link to the source zoning code or ordinance so you can verify the section without hunting. This is not a substitute for formal due diligence. It is a fast, consistent screen you can run on every site that crosses your desk. It keeps early conversations anchored to what the code allows instead of what a sketch suggests. What comes back and how to use it Constraint table with math shown. You see the allowed value, your proposed value, and the calculation. It is clear where a miss comes from, not just that it exists. Pass, Fail, Flag labels. Pass means it fits as proposed. Fail means it does not. Flag marks items that need interpretation or more detail, where most early reviews stall. Plain-English verdict. A single sentence you can paste into an email or an IC memo to explain the result without walking through the full table. Source link. A direct path to the zoning section used, so you or counsel can confirm the read. The payoff is speed and consistency. A careful manual pass takes about an hour. This runs in about ten minutes and leaves a cleaner record of what you checked. Go or no-go calls come faster and are easier to defend. There is a discipline benefit too. The task always checks the same six constraints, so you stop skipping items when you are rushed. If something is off, the table shows it, and you can choose to adjust the program, pursue a variance, or move on. Use it at the top of the funnel. Run it when a broker sends a teaser, when you sketch a concept, or before you ask design for a first pass. If the table comes back clean, you start the next step on firmer ground. If it does not, you learned that in ten minutes instead of after a week of work.