RecordWell Data

_06252026-2211

Town of Mount Pleasant · Charleston County · meeting of Jun 25, 2026 · Minutes

Open the original document More from Town of Mount Pleasant

Text

Extracted automatically from the original. Tables and formatting may not survive; the original document is authoritative.

TREE TASK FORCE Thursday, June 25, 2026 8:00 a.m. Municipal Complex, Committee Meeting Room 100 Ann Edwards Lane, Mount Pleasant, SC 29464 MI NUTES Cl ick here to listen to the recording Discussion Topics 1. Call To Order Chair McKee called the meeting to order at 8:00 AM. Michelle Mansour, Deidre Kennedy, Edward Oswald, Shanna Harris and George Grice were all present when the meeting convened. David Quick arrived at 8:02 a.m. Chair McKee noted that the approach for the session would be to finalize all outstanding recommendations in preparation for the last draft of the report, with the intent that at the July meeting the task force would be prepared to formally accept the final report. He summarized that the group would work through all open items remaining on the recommendations list, beginning with the ordinance section, then reviewing the overall recommendations, and then proceeding through the document itself. Chair McKee noted that Dr. Stewart had helped prepare for the session with Ms. Farrell's assistance. He proposed time- boxing the first part of the meeting — the discussion on zoning ordinances — to approximately thirty minutes, and asked Dr. Stewart to serve as timekeeper. 2. Approval Of Agenda Chair McKee called for a motion to approve the agenda. Ms. Mansour moved to approve the agenda. Ms. Kennedy seconded the motion. The motion carried unanimously. 3. Approval Of Minutes From May 21, 2026 Meeting Chair McKee called for a motion to approve the minutes from the May 21, 2026 meeting. Ms. Mansour moved to approve the minutes. Ms. Kennedy seconded the motion. The motion carried unanimously. Tree Task Force June 25, 2026 Page 2 of 23 4. Public Comment [None] 5. Work Plan TTF 2026 Work Plan 5a. Continued Review And Discussion Of Tree Protection Zoning Ordinances And Policies (Single Family Residential) Chair McKee opened discussion on the zoning ordinance recommendations, providing an overview of the items that had already received general agreement from the task force and identifying the areas requiring further deliberation and decision. He proceeded through each item in sequence. Chair McKee noted that the task force had previously reached general agreement on providing additional detail in the ordinance regarding encroachment into tree protection zones, to be supported by a more detailed arborist report. He asked whether any members had remaining questions or concerns. No objections were raised, and the group confirmed consensus on this item. Chair McKee summarized the proposal to reduce the minimum caliper for mitigation trees from two and one half inches to one and one half inches, explaining that the intent was to make it easier for individual homeowners who are removing a tree to plant a replacement. The group Updated with notes from May meeting • Tree Protection Zone- allow flexibility/ reduction of 20 to 25%. Protection plan from arborist for construction period. Agreement • Reduce minimum caliper for mitigation trees to 1.5 inches. Agreement • Tree mitigation for single family nonconstruction- revise to 1 to 1 tree placement rather than inches when required. General Agreement: For single family non-construction only, without tree bank mitigation, and including Class III trees SEE SLIDE FOR ADDITIONAL DISCUSSION • Develop minimum tree density standard for plantings on single family lots involving construction General Agreement: For single family construction only- 160 inches/ acre or 20 trees/ acre SEE SLIDE FOR ADDITIONAL DISCUSSION • Reduce classification of laurel oaks (water oaks remain as is) Agreement • Allow photo evidence of dead treesand photo as proof of planting (policy not ordinance) Agreement for single family nonconstruction with option to still have a site visit or require an arborist report • Clarify ordinance language and fines for pruning, construction violations in the TPZSupport for staff to proceed with developing language with legal staff • Streamline ordinance language for capital projectsSupport for staff to proceed with no substantive changes to the current ordinance Summary: Staff Recommendations Tree Task Force June 25, 2026 Page 3 of 23 indicated no objection, and discussion of the specific scope of this reduction was deferred to a later portion of the meeting. Chair McKee introduced the proposal to simplify the mitigation process for single family nonconstruction cases — meaning cases where a homeowner is simply removing a tree, not as part of a permitted construction project — by replacing the complex mitigation formula and percentage calculations with a straightforward one-to-one tree replacement requirement. He noted that this recommendation had received significant input from staff regarding the resource-intensive nature of the current process. Chair McKee described the proposal to establish a minimum tree density standard for single family lots where construction is occurring, noting that this standard does not currently exist for this category of property, though it does exist for commercial construction and subdivisions. He noted the density would be set at one hundred sixty inches per acre or twenty trees per acre. Mr. Quick asked staff what the average lot size in Mount Pleasant would be, so the group could better understand the practical implications of the per-acre standard. Assistant Town Administrator Farrell responded that, on average across the town, lot sizes are in the range of approximately eight thousand square feet, which is roughly a quarter acre. She noted that this was typical of areas such as the Old Village, Park West, and Continued Discussion: Tree Density Develop minimum tree density standard for plantings on single family lots involving construction General Agreement: For single family construction only- 160 inches/ acre or 20 trees/ acre • If tree density is met, no replacement? • Should lots that have less than the tree density be required to plant to meet the minimum density? • Density still required for dead and dying or hazardous trees? • Removal of trees above 24 inches must be mitigated above the density? • 24 inch above go to BOZA regardless of density? What about 16 inch if that is changed? • Is payment to the mitigation bank allowed in lieu ? • What defines a tree for the purposes of calculating density (size, species, understory)? Tree Task Force June 25, 2026 Page 4 of 23 Rivertown, where lots generally range from approximately six thousand to nine thousand square feet. Mr. Quick calculated that on a quarter-acre lot, the standard would translate to approximately forty inches or five trees. Assistant Town Administrator Farrell acknowledged that this is not a large number in isolation but emphasized that this is already the standard applied to commercial and multifamily properties, and that the proposal would make the standard consistent. She referenced a recent public comment from a resident who had expressed frustration that homeowners with many trees faced additional mitigation requirements while others could simply plant to reach a maximum, suggesting the consistency argument had resonance in the community. Director Reed added that the town already requires one hundred sixty inches per acre for any residential subdivision of land and that, historically, it had not always been possible to track whether that density was preserved once subdivision lots were built out. She stated that applying the standard at the lot-construction phase made logical sense as a complement to the subdivision requirement. Ms. Kennedy raised the question of what counts as a tree for the purposes of calculating the minimum density — specifically, the minimum size and whether invasive species would be included. Senior Planner Lubert explained that the existing ordinance defines a tree, for purposes of tree protection, as any species that grows to meet a potential canopy of thirty feet or greater at maturity, explicitly excluding palms and understory species such as crape myrtles. Mr. Quick raised the question of whether invasive species would count toward the density minimum, noting that invasives still provide some ecosystem benefits such as shade and flood mitigation. Senior Planner Lubert clarified that under the current code, invasive species are required to be removed during commercial development and do not count toward the density for commercial properties. Assistant Town Administrator Farrell expressed concern about applying that same exclusion rigidly to small residential lots, noting the cost to homeowners of removing invasive trees and the practical complexity of telling a homeowner on a seven-thousand-square-foot lot that they cannot count a tree that is providing shade and reducing stormwater runoff. She noted the potential for the situation to feel punitive and expressed concern about the policy creating appeals to the Board of Zoning Appeals or litigation. Tree Task Force June 25, 2026 Page 5 of 23 Mr. Quick noted that there was already an existing nonconforming provision in the code — where if a project does not exceed fifty percent of the assessed value of the improvement, the property does not need to be brought entirely into code compliance. Director Reed confirmed this and explained that this threshold applies to all zoning provisions, including trees, setbacks, and flood regulations. She noted that every case and project is different and that staff already routinely performs this analysis when evaluating building permits. The group reached consensus that the current ordinance definition of a tree — anything that is a tree and not an invasive species — would be used as the basis for the density standard without modification, and that the existing nonconforming language would provide the necessary flexibility for smaller projects. Ms. Kennedy asked whether all of the additional questions on the slide needed to be resolved. Assistant Town Administrator Farrell indicated that she and Chair McKee had previously discussed that the task force does not need to resolve every implementation detail today; rather, staff needs good guidance from the task force, after which staff will draft the ordinance language. She noted that even after the ordinance is drafted, there may be unforeseen issues, but that the process allows for iteration. She also suggested that the task force, when presenting its report to Town Council, should request the opportunity for one workshop after staff has prepared the ordinance draft, in order to ensure alignment before the formal planning commission and public hearing process begins. Assistant Town Administrator Farrell raised the practical question of what happens when a homeowner wants to remove a significant tree — she used the example of a property owner who is at two hundred inches of canopy on a quarter-acre lot and wishes to remove a twenty-eight- inch red oak, which is the only tree keeping them from meeting the density maximum. She noted that under the current commercial framework, the removal of a twenty-four-inch tree requires mitigation above and beyond the minimum density, and that twenty-four-inch trees in commercial contexts are reviewed by the Design Review Board. She asked the group to consider whether the same structure should apply to single family residential. Tree Task Force June 25, 2026 Page 6 of 23 Chair McKee indicated his view that the same rationale applied — a twenty-four-inch or larger tree in good or fair condition on a single family lot should be required to go to the Board of Zoning Appeals for approval. He noted that any mitigation for such a tree would be on top of, and not in lieu of, meeting the density minimum. He clarified that the mitigation table as it currently exists for commercial properties would remain in place for these cases, and that this framework applies specifically to the construction scenario. Ms. Kennedy asked whether the intent was to increase the mitigation fees. Chair McKee clarified that the task force had not, as a group, agreed to increase the fee; the only fee-related discussions had concerned Laurel Oaks and Water Oaks. He confirmed that the current mitigation table would stay in place for the construction scenario, while the one-to-one replacement would govern the nonconstruction scenario. The group confirmed agreement that if the minimum tree density is met, no replacement is required, and that if a lot is below the density minimum and construction is occurring, planting to meet the minimum is required. Assistant Town Administrator Farrell sought clarification on whether the density requirement applies to all construction or only to projects meeting the fifty-percent-of-value threshold. Director Reed explained that the determination is made case by case, based on the fifty-percent threshold already used for all other code provisions, and that there is no straightforward rule because every lot, every project, and every situation is different. The group accepted this as sufficient guidance for staff to draft appropriate language. Tree Task Force June 25, 2026 Page 7 of 23 Assistant Town Administrator Farrell moved to the slide on one-to-one replacement for the nonconstruction scenario. She noted that several questions had already been addressed in earlier discussion and turned to a specific question: would one-to-one replacement apply to class four trees? The group confirmed agreement that class four trees — which includes invasive species — would not require replacement. No objection was raised. Assistant Town Administrator Farrell then raised the question of whether one-to-one replacement would apply to dead or hazardous trees. She noted that the existing ordinance excludes dead and hazardous trees from replacement requirements. Ms. Kennedy and others expressed support for requiring replacement even for dead trees, observing that the location of a dead tree is often a good location for a new tree, and that the cost of replacement under the new framework is modest given the reduced minimum size of one and one half inches. Mr. Oswald raised the concern that if a storm comes through and many trees are lost, requiring replacement for all of them could be burdensome. Chair McKee and others acknowledged that there would be natural disaster exceptions. Ms. Mansour observed that there is no mitigation formula involved — just a straightforward replacement — and that the cost of a one-and-one-half-inch replacement tree is minimal, noting that trees are available at giveaways for as little as twenty dollars. Chair McKee summarized the emerging consensus as: for class one through three trees, regardless of condition — including dead and hazardous trees — removal requires a one-to-one replacement, and there is no longer a mitigation table or fee for nonconstruction single family cases. He asked whether everyone was in agreement, and the group confirmed consensus, with some members acknowledging that this would likely generate public pushback but expressing the view that it was the right policy. Public Services Director Weis raised an important infrastructure concern: throughout this discussion about tree density and replacement planting, he noted that residential homeowners tend to want to plant trees along the edges of their properties, which is often where drainage easements, pipes, and rights of way are located. He expressed concern that trees planted near infrastructure would eventually need to be removed when pipe repairs are needed or when root systems damage sidewalks and infrastructure, thereby undermining the long-term canopy goals. He noted that mature trees above twenty feet need to be set back a certain Tree Task Force June 25, 2026 Page 8 of 23 distance from infrastructure, and asked that this consideration be incorporated into the ordinance or replanting plan requirements. Senior Planner Lubert noted that a replanting plan is already required under the current process, and that when reviewing such a plan, staff is able to overlay easement maps and flag prohibited locations. Chair McKee acknowledged that the specific setback distances from infrastructure get into a level of implementation detail that could be addressed as a language clarification in the replanting application, rather than a specific recommendation requiring further deliberation. The group agreed that the existing replanting plan review process, combined with language clarifications in the application requirements, would adequately address Director Weis's concern. Director Weis's point was acknowledged as important for the long-term success of the canopy program. Chair McKee noted that the proposal to move Laurel Oaks down one classification level — to the same tier as Water Oaks, in recognition of their shorter lifespan — had previously received general agreement. He noted that this change also reduces the complexity and potential for disputes about mitigation amounts, particularly given the shift to one-to- one replacement. No objection was raised. Chair McKee introduced the topic of whether to reclassify or increase protections for pine trees, specifically to distinguish between Loblolly Pines and Longleaf Pines. Assistant Town Administrator Farrell noted Additional Items for Discussion • Reclassifying/ Increasing Protection for Pine Trees • Current ordinances require that removal of Pine trees above 24 inches and in good or fair condition must be approved by BOZA . Pines less than 24 inches may be removed without mitigation . • Increasing protection levels on trees less than 24 inches on single family properties (require variance approval for 16 inch up?) • Current ordinances allow trees less than 24 inches to be removed with staff level approval and mitigated , regardless of condition. • BOZA approval required for trees greater than 24 inches Tree Task Force June 25, 2026 Page 9 of 23 that the protection of pine trees generates the most complaints she hears from the public. The discussion that followed centered on the difficulty of distinguishing between Loblolly and Longleaf Pines in the field and the enforcement challenges associated with that distinction. Senior Planner Lubert explained that the live crown ratio of most Loblolly Pines — that is, the proportion of the trunk with living crown — frequently falls below fifty percent, which by definition places most Loblolly Pines in class four under the current ordinance, meaning they effectively do not require replacement in most cases. Longleaf Pines, by contrast, are far rarer and more ecologically significant. Senior Planner Lubert cautioned that if Loblolly Pines were explicitly exempted from protection, and a Loblolly Pine were removed without a permit, it would be extremely difficult to cite the homeowner because the inspector would need to visually confirm with certainty that the removed tree was a Loblolly and not a Longleaf, without a stump or needles remaining as evidence. He noted that for this reason, it had been easier during the most recent ordinance update to simply protect all pines above a certain size threshold. Mr. Quick observed that he had watched Great Blue Herons and White Egrets nesting in Loblolly Pine trees at a nearby apartment complex throughout the spring, emphasizing that even Loblolly Pines provide valuable habitat. Assistant Town Administrator Farrell noted that historically pines were protected, then became unprotected, and were more recently given back protection at the twenty-four-inch threshold. She acknowledged that staff had initially been concerned about the re- addition of pine protections but had been pleasantly surprised that it had not generated as many conflicts as feared. The group discussed whether to apply the arborist report requirement so that the species could be identified and confirmed at the time of permit application, with the report indicating whether a tree is a Loblolly or a Longleaf. Senior Planner Lubert noted that having the arborist report would help, but that the enforcement challenge of confirming the species after the fact — if a tree was removed without a permit — remains difficult regardless. Mr. Oswald noted that going from a general pine protection to a Longleaf-specific protection would not meaningfully move the needle in terms of tree protection outcomes, given that Longleaf Pines constitute a very small percentage of the pines in Mount Pleasant. He indicated his Tree Task Force June 25, 2026 Page 10 of 23 preference for leaving the current ordinance as is rather than making a change. The group reached the consensus to make no recommendation for changes to the current pine tree protections, leaving the existing framework in place and moving on. This section of the meeting generated the most extensive and substantive debate of the session. The central question before the task Additional Items for Discussion • Reclassifying/ Increasing Protection for Pine Trees • Current ordinances require that removal of Pine trees above 24 inches and in good or fair condition must be approved by BOZA . Pines less than 24 inches may be removed without mitigation . • Increasing protection levels on trees less than 24 inches on single family properties (require variance approval for 16 inch up?) • Current ordinances allow trees less than 24 inches to be removed with staff level approval and mitigated , regardless of condition. • BOZA approval required for trees greater than 24 inches • Current ordinances allow trees less than 24 inches to be removed with staff level approval and mitigated, regardless of condition. (E) Detached house lots . (1) On individually platted lots for /with detached house dwellings , the following criteria shall be used to evaluate requests for the removal of historic and significant trees : (a) The tree location in relation to property boundaries , infrastructure, existing physical features ; (b) The condition of the canopy , overall health, and species; (c) The nature of the request , justification, and reason for removing the tree; and (d) Whether practical alternatives have been vetted to preserve the tree . (2) Removal of Category I or II historic trees or pine trees greater than 24 inches DBH classified as ‘good’ or ‘fair’ shall be decided by the Board of Zoning Appeals, • BOZA requirements • 156.1296 REVIEW CRITERIA . • (A) The Board may grant a variance in an individual case of unnecessary hardship, if the Board makes and explains, in writing, all of the following findings: • (1) There are extraordinary and exceptional conditions pertaining to the particular pieceof property; • (2) These conditions do not generally apply to other property in the vicinity; • (3) Because of these conditions, the application of the code to the particular pieceof property would effectively prohibit or unreasonably restrict the utilization of the property; and • (4) The authorization of a variance will not be of substantial detriment to adjacent property or to the public good, and the character of the district will not be harmed by the granting of the variance. • (B) The Board shall not grant a variance, the effect of which would be to: • (1) Allow the establishment of a use not otherwise permitted in a zoning district; • (2) Extend physically a nonconforming use of land; or • (3) Change the zoning district boundaries shown on the Zoning Map. • (C) The fact that property may be utilized more profitably if a variance is granted shall not be considered grounds for a variance Increasing Protection Levels on Trees less than 24 inches Tree Task Force June 25, 2026 Page 11 of 23 force was whether to lower the threshold for trees requiring Board of Zoning Appeals approval from twenty-four inches to sixteen inches in diameter at breast height, specifically for class one and class two trees in good or fair condition. Chair McKee provided context, noting that in 2025 data, only twelve of three hundred ninety-one trees that came through the planning process were in class one or class two — that is, in good or fair condition — at the twenty-four-inch-and-above threshold. He noted that this is a small but significant subset: these are the best trees, the ones with full canopy and healthy structure. He observed that under the current system, when staff receives a request to remove one of these trees, staff effectively approves the removal as long as mitigation is offered, because the ordinance language does not provide sufficient authority to deny the application. If staff does attempt to deny, the applicant simply appeals to the Board of Zoning Appeals, and the Board is constrained by state statute to apply a hardship standard that has historically been interpreted strictly by the current board composition. Chair McKee presented the binary choice facing the task force: leave the threshold at twenty-four inches, with the current framework in which staff processes removals and approval is effectively automatic with mitigation; or lower the threshold to sixteen inches, which would direct more trees into a public body review process but would subject those decisions to the same strict hardship standard applied by the current Board of Zoning Appeals. He noted that in other municipalities he had reviewed, trees of significance are typically reviewed by a dedicated tree board rather than a Board of Zoning Appeals, because a tree board is an advisory rather than quasi-judicial body and can apply different, more flexible criteria. Ms. Harris expressed concern about the rigidity of the hardship standard at the Board of Zoning Appeals, asking whether the language was ambiguous enough to allow for flexible interpretation and whether there were provisions for reasonable land use. She gave the example of a homeowner on a quarter-acre lot with a small house who wants to add a room for a baby and is told they cannot remove any of the twelve sixteen-inch trees in their backyard. She expressed the view that there has to be a pathway through the system that makes sense for property owners without simply opening the door to unconstrained removal. Assistant Town Administrator Farrell confirmed that the hardship standard is set by state statute and that while it can theoretically be interpreted flexibly, the current composition of the Board of Zoning Tree Task Force June 25, 2026 Page 12 of 23 Appeals has been significantly more strict than previous boards. She acknowledged that prior boards had approved removals that the current board would likely deny, but that the town does not control how the board weighs the statutory criteria. She also noted that the town has ended up in court and mediation on a number of tree-related appeals. Director Reed observed that what might ultimately protect trees in the sixteen-to-twenty-four-inch range is not necessarily lowering the threshold for Board of Zoning Appeals review, but rather the cumulative effect of the other recommendations being made — particularly the minimum tree density requirement, which creates a financial incentive for property owners to preserve trees on their lots rather than remove them and be required to plant to meet the minimum. She also noted that the proposed flexibility in the tree protection zone encroachment language may reduce the number of cases where property owners feel they have no choice but to remove a tree. Assistant Town Administrator Farrell echoed this point, adding that the previous doubling of the tree protection zone had caused some property owners to simply remove trees because the zone made construction impossible to work around. The new flexibility being proposed for the tree protection zone might, in her view, reduce the frequency of removal requests in that size range. Mr. Quick raised the concern that if the canopy survey comes back showing Mount Pleasant already has forty-six percent canopy coverage, there might be a temptation for Council to conclude that tree policy does not need to be strengthened. He argued that regardless of the percentage, the town should be ensuring the future generation of the canopy by getting trees in the ground now, particularly in anticipation of storms and continued development pressure. Ms. Mansour stated clearly that she is in favor of moving the threshold to sixteen inches. Ms. Harris expressed support as well, though with the caveat that the group should think carefully about how to provide a workable pathway through the approval process, particularly for property owners who are dramatically over the density minimum. Several commissioners observed that most municipalities they had studied during their research set the threshold at sixteen inches rather than twenty-four. Mr. Oswald expressed skepticism, noting that he was not convinced that large numbers of sixteen-to-twenty-four-inch trees were being lost under the current regime, and warning that lowering the threshold could Tree Task Force June 25, 2026 Page 13 of 23 significantly increase the workload on staff and could increase the likelihood of litigation. Senior Planner Lubert acknowledged that if the threshold were lowered, it would be very difficult to enforce violations in the sixteen-to-twenty- four-inch range in practice, because confirming the identity and class of a tree after the fact — if removed without a permit — requires physical evidence. He noted that enforcement would remain reactive rather than proactive regardless. Dr. Stewart called attention to the time and urged the group to move toward a decision if they wished to reach the report review portion of the agenda. Chair McKee proposed that the group take a vote on whether to include in the report a recommendation to send sixteen-inch class one and class two trees to the Board of Zoning Appeals for approval. Those opposed to the recommendation — Mr. Oswald and Mr. Grice indicated their opposition. The remaining members who voted were in favor, with Ms. Harris expressing support while noting the need for a workable exception pathway. The group agreed that the recommendation would be included in the report, while acknowledging that it would ultimately be Town Council that makes the final policy decision through the public process, and that Council might choose a different threshold entirely, might choose to establish a tree board, or might table the issue. Chair McKee briefly reviewed several additional items on which the task force had previously reached agreement. These included: supporting the staff recommendation to allow photographic evidence in mitigation decisions, which would reduce the need for site visits; clarifying the ordinance language for construction violations; and updating the language related to capital projects, which had been left in a holding pattern. 6. Review And Discussion Of Draft Final Report And Recommendations Chair McKee transitioned the meeting to a review of the printed draft final report. He proposed an organizational framework for the document, noting that the executive summary, goal and purpose, and assessment of existing programs sections appeared to be in reasonable shape, but that several highlighted sections required group decisions before the document could go to a final draft. Tree Task Force June 25, 2026 Page 14 of 23 Draft Report Recommendations • Establish a long-term canopy goal of 40% within 20 years. • Develop a 20 year Tree Planting Plan that identifies specific planting areas , their priority , and the type and costs of planting that area . This would include all land uses , not just Town owned land . • Develop a Tree Scorecard /Dashboard /Urban Forest Tracking System to continuously assess tree losses and gains for all the tree programs and tree removal permitting processes (residential , commercial , and capital improvements ). • To achieve canopy objectives , establish a dedicated leadership role within the Town’s organizational structure to oversee tree-related programs and outcomes . • To achieve canopy objectives , re-imagine existing programs to increase tree planting volumes , engage the community at every opportunity , and seek external sponsors and funding . • Ensure sufficient budget to support the new Tree Leader position and tree planting and canopy-related programs to achieve the canopy objective . Draft Report Recommendations • Explore grants , sponsorships , and public private partnership opportunities to leverage Town funding to focus on education and planting programs to encourage private tree planting . • Set aside a portion of the funds for tree-related financial support programs to ensure tree benefits are available to all . • Provide detailed encroachment options for the Tree Protection Zones to enable more flexible site use for development without tree removal • Reduce minimum tree size for mitigation replacement from 2.5” to 1.5” for residential non construction tree removal permits for easier planting by residents themselves and better long term survivability of the replacement tree. • Implement 160”/acre AND 20 trees /acre as the minimum tree cover for Residential lots seeking construction permits with tree removals . • Simplify mitigation for tree removal permits for Existing Residential Non Construction homeowners to one for one replacement , eliminating the complicated inches and mitigation percent by tree category and health rating . For this one category of Land Use , the mitigation is simply “Remove a Tree- Replace the Tree . Tree Task Force June 25, 2026 Page 15 of 23 Chair McKee asked the group whether the list of what is working had been fairly captured. The list included items such as the forest management plan, organized processes, engaged and positive staff, stronger tree protections in the new ordinance, the GIS team's data capabilities, and town funding. No members identified items that were missing or inaccurate. Chair McKee turned to the list of what is not working, noting that this is the section observers will scrutinize most closely. The current list included: no established canopy goal; lack of data about outcomes and net tracking across processes; fragmented responsibility across multiple departments; underutilized tree programs; a budget that is insufficient to support the stated goal; mitigation planting rarely being chosen by property owners; an overly resource-intensive permitting process for nonconstruction cases; and trees ultimately not being replaced. Chair McKee noted that items five and seven on the list were somewhat duplicative and might warrant consolidation. Ms. Kennedy proposed adding a reference to enforcement challenges — specifically, the lack of proactive enforcement of the ordinance during construction, including situations where contractors enter tree protection zones without proper protection in place, damage roots, and face no meaningful consequences. She described a personal experience in which a neighbor had dug a plumbing trench inside her protected trees' protection zone without having tree protection barriers installed, Draft Report Recommendations • Make the Category III tree Declining Health not zero so that a replacement tree is planted or mitigated when a tree is removed for Category 1 through 3 in Good , Fair and Declining conditions . • Support the process simplification of staff accepting photographic evidence from owners of type , condition or tree being removed and for proof of replacement . • Reclassify Laurel Oaks as Category III trees . • One of the responsibilities of the Tree Leader would be to coordinate with the Public Services department to create the proactive public tree maintenance plan as a complement to the overall Planting Plan . • Support staff input for wording changes to the ordinance to clarify pruning and maintenance requirements , capital project requirements like fiber and other utilities , and language to support enforcement and penalties . • Permitting Processes ? • Education , Outreach, Partnerships? Tree Task Force June 25, 2026 Page 16 of 23 damaging fifty percent of the root systems of six trees, with no effective remedy available to her. Senior Planner Lubert acknowledged the difficulty of enforcement, noting that while staff can issue stop work orders and write tickets, defining the extent of damage caused to a tree's root system is extremely challenging from an evidentiary standpoint. He noted one recent case in Old Mount Pleasant where a property owner was taken to court and required to implement remedial procedures. He also acknowledged that with only two code inspectors who are primarily reviewing plans and conducting scheduled inspections, proactive surveillance of active construction sites is not feasible. Assistant Town Administrator Farrell pointed out that the earlier work summary slide already included a recommendation to clarify ordinance language and fines for pruning and construction violations within tree protection zones, and that this finding in the assessment section should be aligned with that recommendation later in the document. Dr. Stewart suggested that, given general agreement, the group allow Chair McKee and staff to draft appropriate language on the enforcement point for inclusion in the final document, to be reviewed at the next meeting. The group agreed. Chair McKee presented the recommendation for a long-term canopy goal. He noted that the Community Forest Master Plan had established that a two percent increase in canopy coverage would require approximately twenty thousand trees. He noted, however, that since the 2019 data on which that plan was based, the town had experienced significant canopy loss through major capital projects — he estimated that two projects alone may have resulted in the loss of approximately five thousand trees — and proposed that the planting target be set higher, in the range of thirty thousand trees, or approximately one thousand five hundred trees per year over a twenty-year period. Mr. Quick raised a concern about relying on a specific percentage target such as forty percent, noting that the ongoing canopy survey might return results showing that the town is already at or above forty percent canopy coverage when areas such as Laurel Hill and the marshlands are included in the calculation. He expressed concern that if the town is shown to already be at forty-six percent, some might argue there is no tree problem and no need for increased planting. He suggested that the number of trees planted annually might be a more durable and politically defensible metric than a percentage target. Tree Task Force June 25, 2026 Page 17 of 23 Assistant Town Administrator Farrell indicated that the canopy survey data coming in was looking stronger than expected — that the town might not be as far behind as previously feared — but that many variables affect what is counted and that the numbers vary significantly depending on methodology and what land is included. Chair McKee summarized the discussion by proposing to take the specific percentage target out of the recommendation language and instead frame the goal as a net annual planting target of approximately one thousand five hundred trees per year over twenty years, with supporting background data explaining how that number relates to historical canopy data. He noted that the report would include reference to the 2019 data, that the marsh would be excluded from the baseline to allow for consistent comparison, and that the background would acknowledge the gap between different methodologies. Mr. Oswald raised the philosophical question of whether there is a theoretical maximum canopy percentage the town could realistically achieve given the amount of developed and developing land. Others noted that this is a natural limiting factor that would be addressed in due course, and that reaching such a constraint would be a wonderful problem to have. The group confirmed consensus on setting the net annual planting goal at one thousand five hundred trees per year, framed as a twenty-year target of approximately thirty thousand trees, with the specific percentage language to be softened or removed in favor of a relative increase goal from the 2019 baseline. Chair McKee described the recommendation to develop a tree dashboard — a public-facing tracking tool that would measure the net gain or loss of trees across all processes, with a target of showing a net gain of approximately one thousand five hundred trees annually. Ms. Harris asked whether the dashboard would be visible on the town's website so that residents could monitor progress. Chair McKee confirmed that was the intent. Ms. Kennedy proposed that the dashboard also track the type or category of trees being removed and replaced — similar to the breakdown used in the Community Forest Master Plan — rather than simply tracking total numbers. Mr. Quick expressed support for the idea but noted that it should only be pursued if it is operationally feasible given staff capacity. Director Reed indicated that the new tree leadership position being recommended would be instrumental in developing and maintaining such a system. Tree Task Force June 25, 2026 Page 18 of 23 The group agreed to include the category-level tracking as a suggestion in the dashboard recommendation, subject to feasibility. Chair McKee asked the group about the timing of dashboard reporting. He noted that the draft had originally proposed quarterly reporting to the Flood Resilience Committee but that quarterly might be too burdensome for the level of data assembly involved, and proposed semi-annual reporting to Flood Resilience and annual reporting to Town Council, with a canopy assessment update every five years. The group agreed to semi-annual reporting as the recommendation. Chair McKee introduced the recommendation for a new dedicated leadership position within the executive branch to coordinate the town's tree programs. Mr. Quick asked for clarification on whether this meant a dedicated staff member — a new position — or simply a leadership role assigned to an existing person. Chair McKee confirmed it meant a new, dedicated position, and agreed to update the language to make that explicit. The group reviewed the list of responsibilities described for the new position. Director Weis suggested adding tree maintenance to the list of responsibilities, noting that planting trees is only valuable if they are properly cared for afterward. Director Reed proposed that the first bullet point be amended to describe the position as responsible for designing the tree planting and maintenance plan, which would encompass both activities in one phrase. The group agreed to this language change. Chair McKee addressed a question that had arisen during drafting about whether this new tree leader would have decision-making authority in the zoning process — that is, whether they would take over the role of the zoning administrator in approving or denying tree permits. He was explicit that the task force was not recommending that. Director Reed clarified that the zoning administrator already designates certified arborists as decision-makers on tree permit applications, so experts are already embedded in that process. The new position would be focused on program coordination, canopy planning, inter-departmental communication, and overseeing planting and maintenance — not on replacing the existing permitting authority. Ms. Kennedy asked why, if someone with deep tree expertise was being hired, they could not also make tree-related permitting decisions. Director Reed and Assistant Town Administrator Farrell clarified that the scope of work for the new position — coordinating all of the programs, planting, maintenance, and reporting — would be a full-time responsibility in itself and that adding a permitting decision-making role Tree Task Force June 25, 2026 Page 19 of 23 would effectively double the position's workload in ways that would be unmanageable. Chair McKee described the existing structure of this section, which lists program ideas drawn from examples seen in other municipalities, organized around three themes: planning proactively, celebrating success and fundraising through events, and engaging the community at the neighborhood level. He noted that the list of references to other municipalities' programs had been included in the body of the report to support the suggestions but asked the group whether these examples should be moved to an appendix to keep the body of the report more focused for its primary audience — Town Council. Dr. Stewart observed that material in an appendix is typically reference material for those who wish to go deeper, while the body of the report is where the key conclusions and recommendations should live. She noted, without making an explicit recommendation, that the audience is Town Council, and that councillors tend to respond better to focused, concise documents. Mr. Quick expressed agreement with the implicit suggestion, noting that people do not like to read very long documents, and stated his preference for moving the detailed program references to an appendix while keeping one example per recommendation theme in the body. Ms. Mansour agreed, suggesting that pages fifteen and sixteen of the current draft could essentially become an appendix. The group reached consensus that the program references would be moved to the appendix, with the body retaining the recommendations and one illustrative example per theme. Chair McKee noted that the task force had softened the funding language at the previous meeting, moving away from very specific dollar amounts to a more general recommendation for sufficient funding. He noted that the report now lists three example areas for implementation on page eighteen and leaves it to Council to determine the mechanism. He asked whether the group was comfortable with this approach. The group confirmed comfort with the approach, and no changes were requested. Chair McKee raised the question of whether the equitable access recommendation should be embedded within the funding section or elevated to its own standalone section. Ms. Mansour expressed the view that it should remain its own section, emphasizing that it is a policy statement, not merely a funding note. The group agreed. Tree Task Force June 25, 2026 Page 20 of 23 Chair McKee walked through the ordinance recommendations section, noting that the discussion in the first portion of the meeting had added clarity on several items that would now be incorporated. He reviewed the tree protection zone recommendation, confirming that it would add flexibility by providing detailed language, and described the contents of the arborist report list as suggested specifics. Ms. Harris noted that the arborist report should, at a minimum, document species, size, health, percentage of root encroachment, canopy reduction, and distance from the tree. She offered to review the specific language in that section and provide suggested text for the next draft if anything needed to be adjusted. On the reduction of the minimum replacement tree size to one and one half inches, Chair McKee proposed — and the group confirmed — that this reduction in minimum size should apply only to the single family, nonconstruction scenario, not to commercial properties or to construction-related mitigation. He reasoned that the intent of reducing the size was to make it easy and affordable for an individual homeowner removing a tree under the simple nonconstruction process, not to reduce requirements for contractors and developers who have the resources to plant larger trees. On the minimum tree canopy cover, Chair McKee confirmed that the density requirement applies to single family residential construction permits, using the existing class definitions and excluding invasive species, consistent with the discussion earlier in the meeting. On simplifying mitigation for single family nonconstruction, Chair McKee confirmed that the recommendation eliminates the mitigation table for this scenario and replaces it with a one-to-one replacement. Ms. Kennedy raised the concern that this could create a loophole where a homeowner removes a tree under the simple nonconstruction process and then, six months later, applies for a construction permit — thereby avoiding the stricter mitigation that would have applied had they gone through the construction process initially. Director Reed noted that in practice, the phone intake process — where staff asks whether a removal is associated with planned construction — catches most of these cases upfront, because most homeowners do not know the difference between the two processes and accurately describe their intentions when they call. She also acknowledged that there is no completely foolproof way to track every mitigation tree planted under any scenario, and that the density requirement for construction provides a backstop in any case: if someone removes a tree under the Tree Task Force June 25, 2026 Page 21 of 23 nonconstruction process and then subsequently applies for a construction permit, they will still be required to meet the minimum tree density at the time of the construction permit, regardless of when the tree was removed. Ms. Harris observed that this backstop effectively addresses the loophole concern — even if someone removes a tree six months before starting construction, the construction permit trigger would require them to plant to meet the density minimum. The group accepted this as adequate protection. Chair McKee raised a specific issue with the mitigation table as proposed: currently, the mitigation percentage for class three — declining condition — trees is zero, meaning no mitigation is required for their removal. He proposed that this number should be nonzero, at least as applied to commercial and residential construction scenarios, so that there is some minimum mitigation obligation even for a declining tree. He suggested ten percent as a reasonable nonzero figure. Mr. Quick and others expressed agreement that something above zero was appropriate, and the group confirmed that ten percent was a reasonable and defensible starting point for class three tree mitigation, to be applied in the commercial and construction contexts. Ms. Mansour and others agreed. Chair McKee noted that the maintenance strategies section describes maintenance as a core function of the new tree leader position and the coordination role with Public Services. He suggested framing this not as a standalone recommendation but as a recognition that maintenance is expected to be part of the new position's core responsibilities, with coordination to be worked out with Public Services. Ms. Mansour raised the idea of creating a maintenance brochure for the public that would provide guidance on proper tree care. Chair McKee suggested that this idea would be better placed in the education, outreach, and partnerships section, as a recommended opportunity for improvement. The group agreed to move it there. Senior Planner Lubert noted that the town does currently have some informational brochures on tree care that are provided to residents. Ms. Mansour indicated that she had not been aware they were available and suggested that the recommendation include hosting these brochures prominently on the town's website for easier public access. Mr. Quick agreed and asked that a copy of the current brochure be brought to the Tree Task Force June 25, 2026 Page 22 of 23 next meeting so the group could assess whether it needed updating. Senior Planner Lubert agreed to do so. Ms. Harris raised a new proposal near the end of the meeting: she suggested that tree service companies, rather than individual homeowners, should be the party responsible for applying for and submitting tree removal permits — similar to the way licensed contractors apply for building permits. She noted that in her own experience, tree service companies that regularly work in a jurisdiction adapt quickly to administrative requirements and that having them handle permitting would eliminate a point of contact, reduce errors, simplify tracking, and encourage more professional reporting. She acknowledged that there would need to be an exception for homeowners removing trees themselves. Ms. Kennedy expressed immediate enthusiasm for the idea, describing it as a significant simplification. Several other commissioners expressed support. Ms. Mansour noted that some tree service companies currently charge homeowners additional fees to submit permit applications on their behalf — her own company had charged an additional one hundred dollars — but suggested that if this became a standard requirement as part of doing business, it would simply become part of their overhead rather than a special charge. Director Reed noted that the concept was appealing but that it had some practical challenges. She observed that many homeowners call the town before selecting a tree service, without yet having a contractor lined up, and that staff would need to direct them to select a contractor first. She also acknowledged that many homeowners currently pull their own permits. Mr. Quick raised the question of liability — specifically, if the tree service pulls the permit and something goes wrong, whether the homeowner would be insulated from responsibility. Ms. Harris clarified that the homeowner's information would still be on the application, that the homeowner would still receive all correspondence, and that both the homeowner and the contractor are currently liable for work performed. Current practice of both parties remaining responsible would continue. An unidentified participant suggested that rather than mandating tree service permitting, there might be ways to incentivize it or to make it a standard expectation communicated to contractors through business licensing, since it would need to be addressed carefully to avoid unintended consequences. Tree Task Force June 25, 2026 Page 23 of 23 Chair McKee indicated that he would find a place to insert this concept into the report recommendations and asked for the group's agreement to include it. The group was generally supportive, and several participants observed that this idea, if implemented, could significantly reduce staff workload and improve compliance. Chair McKee agreed to incorporate it and requested that the group reflect on the idea before the next meeting. 7. Discuss Next Agenda Chair McKee described the agenda for the next meeting as a full review of the final draft report, with the objective of making any last-minute changes and voting to approve the document. He emphasized that members need to read the draft before the meeting — not on the night before — and send comments to him as early as possible so that changes can be incorporated into the draft prior to the meeting, reducing the amount of live editing required during the session. He described this as crunch time for the task force. 8. Adjourn Chair McKee asked whether any member had additional items to raise before adjournment. No additional items were raised and the meeting was adjourned at 10:07 a.m. Respectfully submitted Christine Barrett Clerk of Council June 25, 2026

Source: Town of Mount Pleasant website. First collected Oct 23, 2026.