Developer presents large mixed‑use and inclusionary housing plan; officials and residents raise sewer, school and traffic concerns

A developer and township planning staff gave a public presentation July 7 on a proposed master plan that would add a large mix of housing types and neighborhood amenities; the presentation drew sustained questions about sewer capacity, school costs and traffic safety.

For the record, the developer identified himself as Cio Los Santos, senior vice president of development for Rousseau (speaker 6). He described a multiphase project that would include single‑family homes, townhouses, stacked multifamily and broader public amenities such as trails and a central boulevard along Route 173 and Route 78. The developer said the concept area is slightly more than 100 acres and showed color‑coded map zones (orange, green and blue) to indicate differing densities and where the inclusionary affordable units would be located.

Why it matters: the plan as described would substantially increase housing supply and population in the township and trigger infrastructure and service impacts (sewer, schools, emergency response and traffic) that residents and elected officials said must be analyzed before any zoning changes or approvals.

What the developer presented and what remains unresolved

• Numbers and phasing: presenters repeatedly used several different totals as examples: a baseline settlement figure of 250 affordable units was discussed by the planning official (speaker 5), the developer cited build‑out figures that ranged from roughly 1,000 to 1,270 units in different parts of the presentation, and the team described an initial phase of about 325 units (roughly 200 multifamily plus 125 stacked units) as a likely early build. The developer said one phasing approach is to begin with parcels that can be served by existing sewer capacity and then seek to buy additional plant capacity for later phases. The transcript records multiple, varying figures; the project team characterized the numbers as conceptual and subject to engineering and permitting.

• Sewer capacity and the 65‑unit set‑aside: planning staff explained that under the settlement approach 65 of the affordable units are located in areas currently serviceable by the sewer plant’s cited capacity (presenters referenced a 75,000‑gallon‑per‑day figure). The developer said remaining affordable units would be enabled by an overlay zone and by acquiring additional sewer capacity if necessary.

• Inclusionary mechanics: the presenter (speaker 5) said the proposal relies on inclusionary zoning rules that require market‑rate units to subsidize the affordable set‑aside; language in the presentation emphasized an overlay district to permit higher density in parts of the study area while keeping lower‑density development adjacent to existing homes.

• Design, amenities and accessibility: the developer highlighted on‑site amenities (amphitheater steps, trails, a central clubhouse and public plazas), said rental units would be adaptive for accessibility, and described an intent to include both for‑sale and rental restricted‑income homes as part of the mix.

Public‑safety, schools and traffic concerns

Residents and some committee members repeatedly pressed the developer and planning staff for specifics on off‑site impacts.

• Schools and costs: a resident asked how the project would affect the school district; speakers referenced rough student‑generation estimates and the need for a formal community‑impact or school‑impact statement as part of any development application. One attendee summarized the concern bluntly: “It’s a traffic nightmare,” reflecting worries about safe student transportation on Route 173 and potential busing needs.

• Traffic: multiple participants cited Route 173 as a safety concern and asked that a traffic‑impact study accompany any formal application. The developer acknowledged that off‑site improvements and traffic mitigation would be studied as part of the application package.

• Emergency services: a speaker with long fire‑service experience noted increases in call volume and asked how fire and rescue coverage would scale; the developer said design and access points would be addressed and that the project team would study ingress/egress for emergency vehicles.

Process and next steps

Planning staff and the developer repeatedly emphasized that this meeting was a public input session only and that no zoning amendments or approvals were requested tonight. The presenter said: “There is no action that’s gonna be taken today. This is truly a public input session.” The team described the next steps as submission of a formal development application that would include traffic, sewer and community‑impact studies, engineering details and a phasing plan tied to plant capacity and market conditions.

Representative quotes

• “We are not under a time clock... This is truly a public input session.” — Planning official (speaker 5).

• “We’re going to phase this — if there is not enough sewer capacity, you get the duration; we adjust what you don’t have to serve.” — Developer Cio Los Santos (speaker 6).

• “It’s a traffic nightmare.” — Resident commenter (speaker 7), urging attention to safe student routes and traffic mitigation.

What the committee did (and did not) decide

Committee members listened, asked clarifying questions and took no zoning or approval actions on the development tonight. Multiple routine consent items and resolutions on the agenda were moved and approved earlier in the meeting (see “Votes at a glance” below). The planner and developer said final technical studies will accompany any formal application and the planning board process will follow statutory notice requirements.

Ending note

Officials asked that residents’ written comments and technical questions be submitted to staff so they can be addressed in subsequent hearings; the committee closed public comment and completed its remaining procedural business without further action on the project.