Mendon planning commission reviews subdivision frontage, private-lane rules amid annexation questions

Mendon Planning and Zoning commissioners on Tuesday reviewed the city—s subdivision ordinance language that requires new lots to have road frontage and discussed how a separate private-lane clause applies only to preexisting lots.

Commissioners and staff said the current rule that every new lot must have frontage on a road (the commission noted a 110-foot frontage standard in the subdivision code) prevents creating new lots that are served only by private lanes or shared access. That requirement, they said, has resulted in repeated permit denials when property owners try to split lots and use private lanes for access.

The matter matters because citizens and some council members have asked the commission to consider changes for larger existing lots where shared access or private lanes might improve housing affordability. Staff told the commission those requests should first be sounded out with city council; if council is disinterested, planning staff said there is little point in drafting ordinance amendments. Staff also said recent changes to the state annexation law have added urgency to clarifying how new lots, forced annexation and utility access interact.

During the discussion staff summarized three key constraints: the subdivision code—s frontage requirement, an existing private-lane clause that permits private lanes to provide access only to preexisting lots (not to create new lots), and a general-plan reference that planning staff recalled as discouraging interblock development. Staff noted inconsistent wording across the subdivision code, zoning code and general plan has created confusion for applicants and staff.

Commissioners flagged specific points for revision: clarify whether —3frontage—4 is measured from the property line or the street edge (the commission favored —3property line—4 to reduce ambiguity); state explicitly that private lanes may serve only preexisting lots; define the maximum number of lots a private way may serve (the draft language referenced —no more than two lots— in one place); and align the ordinance with applicable fire-code requirements for lane width, surface and turnaround.

The commission recommended sending the draft language and a short summary of the issues to the city attorney, city engineer and to two staff reviewers (Eric and Kirk in the meeting) for technical review. Commissioners said they will not spend substantial staff time drafting an ordinance if the city council will not support changes. Several commissioners urged staff to first gauge council interest before committing to a lengthy drafting process.

Staff noted that applicants who wish to pursue a split that depends on private-lane access may ultimately need to seek judicial relief if denied under current code; staff said that outcome has occurred on multiple past applications. Commissioners asked staff to propose clarified wording for the subdivision ordinance that preserves the city—s intent to avoid small, inner-block lots while allowing clear exceptions for existing preexisting lots.

The commission also briefly discussed related technical items to be revised in the subdivision chapter: removing a provision that could be misread to permit elimination of curb and gutter; clarifying what constitutes a —3completed—4 swale (vegetated, gravel or other surface) and assigning developer installation and maintenance responsibilities; and restoring a previously lost provision regarding edge-of-property requirements that disappeared during earlier doc revisions.

No ordinance change was adopted at the meeting; staff was directed to send the draft sections to the engineer and city attorney for review and to report back. The commission approved the previous meeting—s minutes by voice vote earlier in the session (the transcript records unanimous approval but does not list a roll-call tally).