You know the moment. A site looks promising, the concept fits on a scrap of paper, and someone asks, "are we even allowed to build this?" Then an hour disappears into code sections, tables, and half remembered ratios. This task cuts that stall. It runs your concept against the core zoning limits and shows the math, so you can decide whether to proceed, adjust, or walk. Due Diligence ~10 min to run Assess Zoning Feasibility for a Proposed Development Vic prompt Use Vic to assess zoning feasibility for a proposed 120,000 sf multifamily project on a 2.5-acre site at 4500 Main Street. Purpose Identifies zoning conflicts in roughly 10 minutes instead of the typical 60-minute manual review, so teams can screen sites faster and avoid early-stage surprises. Inputs Property Address Required Proposed Development Required Outputs A table listing each constraint with allowed value, proposed value, status, and calculations, plus a bottom-line verdict and zoning source link. Time saved Cuts a typical 60-minute manual review to about 10 minutes. How it works Give Vic two inputs: the property address and a clear description of the proposed development. That can be as simple as total square footage and use, or as detailed as units, height, and parking. Then run: "Use Vic to assess zoning feasibility for a proposed 120,000 sf multifamily project on a 2.5-acre site at 4500 Main Street." Vic pulls the applicable zoning rules and checks your concept against six constraints: use, height, FAR, density, setbacks, and parking. The output is a clean table with four columns for each item: the allowed value, your proposed value, a status of Pass, Fail, or Flag, and the calculation that ties it together. If something is close or depends on interpretation, it is flagged instead of forced into a pass. You also get a one sentence verdict in plain English. It answers the only question that matters at this stage: does the concept comply as proposed, or where does it break? Any flagged issues sit beneath the table so you can see where a small change might fix the problem. The zoning source link is included so you or counsel can go straight to the code section without hunting. This is a screening tool, and it behaves like one. It does not bury you in narrative. It shows its work. If FAR is tight, you see the site area, the allowed ratio, and the resulting cap next to your proposed square footage. If parking is short, you see the required spaces and your plan side by side. That transparency makes it useful in a deal meeting. You can point to the line item and decide whether to redesign or move on. The time savings are real. A manual pass through these six items takes about an hour once you factor in finding the right district, confirming definitions, and double checking the math. This runs in about ten minutes and produces a memo ready table. Teams can screen more sites in the same afternoon and keep momentum while options are still fluid. There is also a discipline benefit. Early stage concepts tend to drift. Density creeps up, parking assumptions lag, and setbacks get hand waved. A quick, repeatable check keeps the basics tied to the code. It is easier to adjust a concept on day one than to unwind it after design moves forward. Use it at three points. First pass when a deal hits your desk. Second pass after a quick massing or unit count revision. Third pass before you spend on deeper diligence. Each time, you get the same structure: six constraints, clear math, a verdict, and a source link you can trust.