Margate DRC declines to recommend approval of Carolina Club redevelopment applications pending unresolved traffic, compatibility and documentation issues

The Development Review Committee of the City of Margate on Aug. 26 declined to recommend approval of three linked applications for the redevelopment of the Carolina Club Golf Course at 3011 Rock Island Road, citing unresolved traffic analyses, compatibility concerns for a proposed multifamily pod and incomplete application documentation.

The three applications under reconsideration were a development agreement (application 2400400067), a land‑use plan amendment (application 2400400057) and a rezoning (application 2400400056), all submitted for the same project by the applicant’s agent, Matthew Scott of the law firm Greenspoon Martin, on behalf of Rosemergie Acquisition LLC. Andrew Penny, the city’s senior planner, told the committee that because several substantive comments remain open the committee must find the applications do not yet demonstrate compliance with the Unified Land Development Code and the concurrency management system.

The committee’s negative recommendation followed a round of staff responses to written comments and an update from the applicant on outreach and revisions. Matthew Scott said the applicant had held three virtual meetings with surrounding homeowners associations and an open house at the Holiday Springs Clubhouse, and that the team had revised the master plan to show two potential locations for a future fire station. Fire representative David Scholl told the committee the city’s position is that “regardless of what that comes out, we need land set aside on the developer’s agreement.”

Scott also said the applicant intends to add deed restrictions to limit some uses in the commercial retail pod and to clarify that developer, not the city, will pay for certain public improvements. He told the committee the applicant would revise the development agreement language to make that explicit.

Staff raised three categories of unresolved concern that led to the committee’s recommendation: outstanding traffic study items, compatibility between proposed mid‑rise multifamily buildings and adjacent single‑family neighborhoods, and incomplete application documentation. Penny read language from the Unified Land Development Code (section 40.322) explaining that the committee must approve an application only upon demonstrating compliance with all applicable laws, including the concurrency management system. Planner comments cited section 40.03(b)(1) and related rezoning criteria, and noted that the proposed Pod C could allow buildings of up to six stories under the requested zoning — a scale staff and nearby associations said could have adverse impacts on privacy and sunlight for single‑family neighbors. Scott said the project team had told the master association it would commit in the development agreement to “not exceed 4 and 5 stories for the multifamily” while negotiations continue.

Public‑works and engineering reviewers emphasized that documentation submitted for each application must stand alone. Kurt Kaiser of Deese told the committee, “These applications need to stand on their own, and all the documentation needs to be… with that application,” warning that cross‑referencing files could hamper public records searches and future reviews.

When the committee took a roll‑call recommendation on each application, staff members recorded negative recommendations. Penny summarized the committee’s position to the applicant: “The committee is not ready to recommend approval of your applications today.” He advised the applicant it could either move forward to the next review body with the negative recommendation or resubmit after addressing comments at the staff level.

The committee adjourned after brief general business and a welcome to Mark Young as the new building code services director.