Developer outlines 1,750‑acre master‑plan, proposes zoning overlay and park/occupancy triggers in Grantsville

Sean Johnson, the property owner, and Leila (Layla) Rosales of Terracina Design presented a proposed Deseret Zoning Overlay District for a large master‑planned community in Grantsville at a Planning Commission work session Thursday evening.

The proposal covers a roughly 1,750‑acre site and would establish an overlay to lock in unit counts, commercial acreage and park acreage for a multi‑phased community the applicant said could take 15–20 years or longer to build out. Johnson said the overlay would fix the total number of residential units, commercial acreage and park areas, and that unit totals could only be reduced after approval.

The presentation said the site is currently zoned mixed use and the overlay would specify permitted uses and design standards. The developer described roughly 82 acres slated for commercial development within the site (the team said a strict reading of the city code’s “major street” frontage could imply about 99.5 acres of commercial), multiple commercial types (general, neighborhood and flex commercial), a central oval feature and a large community park concept. Terracina’s presentation included proposed architecture standards, dark‑sky‑compliant lighting, medians and a 30‑foot landscape buffer along collectors.

Johnson said the plan ties parks and other public improvements to issuance of certificates of occupancy (COs). Under the proposal, neighborhood parks associated with a development area must be 100% complete before the city issues the 50th percent certificate of occupancy for homes in that area, and the first phase of the community park would be complete before issuance of the community’s 1,500th certificate of occupancy. The team said those triggers are intended to ensure on‑time delivery of parks rather than “promises” that never materialize.

The applicants also described infrastructure needs they estimate at roughly $120–$150 million, including about three miles of sewer line, a water storage tank and storm drainage for the new community.

Requested code deviations and changes

Terracina listed roughly four general deviations, eight code‑compliant items and nine enhancements. Among deviations discussed in the meeting were: - Reduced front, side and rear setbacks for some product types (applicants said the garage setback would remain 25 feet, but they seek to allow living space or porches to project forward by 10 feet on some front‑loaded homes). - Smaller minimum lot sizes for some alley/rear‑loaded product types (they proposed 2,400 square feet in some alley‑loaded detached‑townhome units) and reduced lot frontage (example request: 45‑foot frontage instead of 50 feet on some lots). - Reduced easement widths where feasible, “to 5 feet or as approved by utility providers,” with the caveat that applicants would meet any utility provider’s actual requirements.

During the presentation Terracina said it would withdraw two deviation requests before the next submittal: a requested reduction to multifamily height (they will revert multifamily height to 35 feet) and a parking deviation for multifamily visitor parking (they said they will follow code parking standards). The team also said it will add timing requirements for installation of residential front‑yard landscaping.

Parks, open space and affordable housing

The applicant said the plan proposes about 39.5 acres for a community park (conceptual) plus roughly 78.3 acres of neighborhood parks and about 264.2 acres of open space and 63.4 acres of common area. Using the city’s capital facilities plan standard (4 acres of park per 1,000 population), the applicant said their calculation yields a park level of service that exceeds what the plan requires. The team also proposed dedicating 20 acres for moderate‑income housing, which the presenter estimated could accommodate roughly 100–300 units depending on product type; commissioners urged the developer and staff to express affordable housing commitments as a unit count or percentage rather than acreage.

Design standards and other enhancements

The overlay would add design standards for architecture, elevation differentiation (to prevent repetitive facades), increased common‑area requirements for apartments/condominiums (presenters proposed increasing required common area from 10% to 20%), sign and lighting standards, and prohibition of vinyl fencing in favor of natural materials.

Questions and concerns raised

Commissioners and staff pressed the applicants on several topics: - Code definitions and “front yard” requirement: City representatives and commissioners stressed the city’s code definition that a front yard must front a street. Several commissioners said the proposed rear‑loaded or alley‑fronting lot types may not meet that definition without an approved deviation. One commissioner said, “You can’t call it a front yard if it doesn’t meet our front yard definition.” - Density and net vs. gross acreage: Commissioners asked the team to reconcile their density calculations with the city’s net‑area methodology. One commissioner said the developer’s numbers appeared to use gross acreage and urged a net‑area analysis. - Easements and utilities: Commissioners expressed skepticism that utility providers would agree voluntarily to substantially narrower easements and urged the team to coordinate with providers; presenters said they would meet whatever the provider requires. - Infrastructure and geotechnical concerns: Commissioners and at least one resident noted that the site sits on an alluvial fan and asked how the applicant will address stormwater, drainage and potential flood risks. One commissioner asked whether the project team had consulted the Utah Department of Environmental Quality; the applicant said engineering work is ongoing and that these topics will be addressed in subsequent engineering review. - Maintenance and water for landscape buffers and medians: Commissioners asked who would maintain the large landscape buffers and medians and whether the developer would supply irrigation water. The applicants said they expect to provide water for the landscape buffer and would convey the dedicated streets and tree lawns to the city for maintenance consistent with standard practice.

Process and next steps

The presentation was given in a work‑session format; no formal action or vote was taken at the meeting. Presenters said they will revise the overlay text in several ways (retracting the multifamily height and parking deviations, adding timing language for landscape installation, and other clarifications) and return for further planning commission review and subsequent city council consideration. Commissioners and staff said they expected additional meetings to reconcile definitions, density methodology and infrastructure conditions before any formal approval.

Quotes (selected and attributed)

“My name is Sean Johnson, owner of the property,” Johnson said when introducing the project. He described the project as a long‑term “master plan community” and said the overlay is intended to “tie down the unit count. It ties down the commercial space. It ties down the park space.”

Leila Rosales of Terracina Design summarized requested deviations and said the team would “scratch” the parking deviation and keep multifamily height at code (35 feet) in the next submittal.

One commissioner cautioned on definitions: “You can’t call it a front yard if it doesn’t meet our front yard definition,” and urged alignment between proposed product types and the city’s code.

Ending

The Planning Commission called the presentation a work session and paused action to allow further revisions and follow‑up review. The applicants said they will make the described edits and return for additional discussion; the commission set further consideration for a subsequent meeting. No formal vote occurred at the Feb. 20 work session.