PHILADELPHIA PILOT · LIVE PARCEL BETA
Know what a site
could support before
the first call.
Select a parcel, compare approval paths and trace every conclusion back to an official source. The first US edition translates Urban.ai’s site-review logic into a city-specific development feasibility workflow.
Philadelphia only · Residential and mixed-use first · English edition
ILLUSTRATIVE DEVELOPMENT SNAPSHOTEXAMPLE DATA
01 · PRODUCT WORKFLOW
One site, two questions:
what fits and what must happen next?
The US edition replaces Korea’s program-eligibility decision with a zoning envelope, approval path and risk screen tailored to each city.Choose parcels
Search an address, select adjacent lots and define the land basis for every calculation.
Identify the path
Separate by-right, special-exception, variance and prerequisite-review routes instead of treating them as interchangeable options.
Trace the evidence
Separate calculated outputs, public records, user assumptions and items requiring professional review.
02 · INTERACTIVE FOUNDATION
Compare a sample
development path
Pick a fictional Philadelphia site, then compare a code-compliant concept with one that requests zoning relief. Values below are product-demo assumptions, not city records.STATUSExample data onlyUse the parcel beta above for live public records.
By-right
Designed to follow the applicable zoning rules. A zoning permit is still required.
Special exception
A use the code permits only after ZBA review against stated criteria. It is not a variance.
Variance
A request to depart from zoning rules. Hardship must be proved and approval is uncertain.
PARCEL SELECTIONExample: West Philadelphia
101102103104105106107108109110111112LANCASTER AVEN 41ST ST
- Base district
- CMX-2
- Combined area
- 6,780 sf
- Selected
- 3 parcels
- Current use
- Retail + vacant lots
The proposed use and scale are framed as a by-right case, but the three parcels cannot be treated as one zoning lot until the legal lot configuration is confirmed.
PRELIMINARY PATHPrerequisite review required
EXPECTED NEXT PATHLot consolidation + zoningFinal routing requires current zoning, overlays, dimensional standards and project-specific facts.
ITEMS TO VERIFY
- Consolidation must be completed
- Ground-floor use and transparency rules apply
- Confirm any overlay before relying on the yield
DATAExample onlyTITLE / SURVEYNot reviewedBUILDING CODENot evaluated
03 · DATA CONNECTION PLAN
Every result should show
where it came from.
The analyzer distinguishes official records, calculated outputs, user assumptions and manual-review items. Partial connections never imply that an approval path has been determined.Data itemOfficial sourceIntended outputStatus
Parcel boundariesDepartment of RecordsParcel ID · GIS geometry · mapped areaLive beta
Zoning + overlaysPhiladelphia City Planning CommissionBase district · overlays · cited rulesBase district live
Property recordsOffice of Property AssessmentUse · building area · assessed valueLive beta
Permits + violationsLicenses and InspectionsPermit history · open violationsNot connected
Historic + flood screensHistorical Commission · FEMAPrerequisite review flagsNot connected
Automatic analysis stops when the record is ambiguous.
Parcel/account mismatches, unresolved overlays, prior variances, nonconforming uses, Unity of Use, incomplete consolidation and missing survey dimensions must be routed to manual review.
04 · BUILD ROADMAP
Philadelphia first.
City adapters next.
The shared product shell can expand nationally, while zoning rules and municipal data remain city-specific modules.US entry point, product workflow and interactive example scenarios.
Real address search, DOR parcel map, base zoning and OPA property records.
Overlays, allowed uses, dimensional standards, rule dates and source-linked approval-path classification.
Risk layers, editable assumptions, manual-review flags and a versioned downloadable report.