_07302026-2232
Town of Mount Pleasant · Charleston County · meeting of Jul 30, 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, July 30, 2026
8:00 a.m.
Municipal Complex, Committee Meeting Room
100 Ann Edwards Lane, Mount Pleasant, SC 29464
M
INUTES
C
lick here to listen to the recording.
Click here to view the draft report.
Click here to view the amended final report.
1. Call to Order
M
r. Bob O'Neill noted that James McKee, the chair, was absent due to a
family emergency. He indicated that the group did not technically have a
vice chair and offered to facilitate the meeting himself or to defer to
another member. Michelle Mansour agreed to facilitate, citing her
experience with planning commission meetings. Ms. Mansour called the
meeting to order on July 30, 2026 at 8:00 AM. Shanna Harris, David
Quick, Michelle Mansour, George Grice, Diedre Kennedy and Edward
Oswald were all present. James McKee was absent.
2.
A
pproval of Agenda
Ms. Mansour called for any changes to the agenda, and none were
raised.
Motion to approve the agenda was made by Mr. Quick and
seconded by Ms. Harris. The motion carried unanimously.
3.
A
pproval of Minutes from June 25 Meeting
Ms. Mansour called for any changes to the minutes from the June 25
meeting. No changes were proposed.
Motion to approve the minutes from the June 25 meeting was made
by Mr. Quick and seconded by Ms. Kennedy. The motion carried
unanimously.
4. Public Comment
Two members of the public addressed the Task Force.
DRAFT
Tree Task Force
July 30, 2026
Page 2 of 9
Lisa Schnipke opened by thanking Town Council for creating the Task
Force, the Town for supporting it, and all committee members and staff
for their contributions. She expressed agreement with many of the draft
plan's objectives, including the establishment of dedicated leadership
within the Town's organizational structure to oversee tree-related
programs, the prioritization of tree mitigation funds for tree planting, and
the reduction of minimum planting caliper size from 2.5 inches to 1.5
inches for residential plantings. She emphasized that community
engagement was essential, and that residents needed to understand
that the appropriate way to advocate for trees was through formal
processes such as ordinances and public meetings — not simply
through informal community discussion. She encouraged the Town to
pursue a robust media and education campaign, noting that trees
provide community-wide benefits through wildlife habitat, storm
protection, and canopy restoration, not merely individual benefit. She
commended Town staff for their one-on-one outreach at community
events.
Town Council Member Mike Tinkey echoed the prior comments and
stressed that the Task Force was at a critical tipping point in determining
whether the Town would take an intentional approach to its tree planting
program. He cited the Tinkey Timberlands forest management plan as
an example of the kind of detailed, long-range planning — plot by plot,
area by area, over a 20-year horizon — that the Town should strive to
emulate. He suggested that the program needed a simple,
communicable goal that the public could visualize, such as planting a
specific number of net new trees per year. He also referenced a planting
program conducted by George Grice's firm at Laurel Hill County Park as
a model of the level of detail and habitat-specific planning that he
believed was necessary. He stressed the importance of hiring the right
experienced staff person and noted that the management plan must
include a maintenance component and a dedicated budget. He thanked
Christiane Farrell specifically for her leadership and years of experience
brought to this work.
5. Review and Approval of Final Report and Recommendations
Ms. Mansour opened the item by thanking Deidre Kennedy, James
McKee, and David Quick for their work in compiling the report. Mr.
O'Neill suggested the group focus on any outstanding questions or
comments rather than reviewing the report page by page, given that all
members had reviewed it in advance.
DRAFT
Tree Task Force
July 30, 2026
Page 3 of 9
Arborist or Tree Company Submission Requirement
Ms. Kennedy raised a previously parked item from the last meeting,
originating from a suggestion by Ms. Harris, regarding whether arborists
— rather than homeowners — should be required to submit tree removal
permit applications. The relevant language in the draft report, found on
pages 30 and 31, used the word encourage rather than require.
Ms. Kennedy explained that the intent was to have the first step of the
permitting process directed toward a tree company, noting that staff
could be involved in facilitating that. She also noted that there would
always be exceptions and that flexibility would be needed. Mr. O'Neill
asked whether the intent was to make arborist submission mandatory.
Senior Planner Chris Lubert provided perspective from a staff
standpoint. He noted that when homeowners submit applications
directly, the process is often complicated because homeowners are
unclear about what information staff needs — such as proper
measurements and tree identification. In contrast, when an arborist or
professional tree service submits the application, the information tends
to be accurate, complete, and efficiently processed, because the
company is motivated to get the permit approved so they can complete
the job. He acknowledged, however, that some homeowners prefer to
shop for contractors only after they know the permit will be granted.
Mr. Grice asked whether requiring an arborist would significantly
increase costs for homeowners. Ms. Kennedy and Ms. Harris noted that,
in their experience, most tree companies do not charge an additional fee
simply to complete the permit application — the standard Town fee of
fifty-five dollars applies. Ms. Mansour noted that the company she had
worked with charged a one-hundred-dollar fee to fill out the permit
application, which she declined to pay, indicating that market
competition would naturally discourage companies from charging for this
service.
Mr. Quick suggested that requiring an ISA-certified arborist to submit the
application could help raise the standard of tree removal companies
operating in the Town. Ms. Kennedy and others found this appealing
from a quality standpoint. Ms. Harris, however, noted that ISA
certification is not a current legal requirement to perform tree removals,
and that imposing such a requirement would either exclude many
legitimate tree service businesses or require them to incur the cost of
hiring a certified arborist — a burden that could ultimately be passed on
to homeowners. She expressed that she supported requiring a certified
DRAFT
Tree Task Force
July 30, 2026
Page 4 of 9
arborist to author any health assessment report for trees 24 inches and
above, but not for the act of submitting a general removal permit.
Mr. Oswald expressed concern about making arborist submission
mandatory, noting that the Town itself employs arborists and that the
Town's staff could review applications and inspect trees as needed. He
also emphasized equity concerns, noting that not all Mount Pleasant
residents could absorb the additional cost that a mandatory arborist
requirement might impose. He suggested that the Town's proposed
expansion of arborist staff was a better mechanism for quality control.
Mr. Grice suggested a possible middle ground in which an arborist would
need to sign off on the application but a separate tree company could
perform the removal work. Ms. Harris noted this would likely introduce an
additional fee and could complicate what are sometimes straightforward
or hazardous situations requiring prompt action.
Mr. O'Neill proposed leaving the language as currently written — using
encourage — and directing staff to develop application language that
would explain to homeowners the practical benefit of using a
professional tree service or arborist, specifically that permit turnaround
would be faster. He noted that this would create a de facto norm without
imposing a legal mandate. Mr. Grice supported adding language that
would strongly or highly encourage the use of a professional. Ms. Harris
supported this direction, drawing a parallel to owner-builder provisions in
the building code, where language advises homeowners that a
contractor unwilling to pull their own permit is a red flag.
The group reached consensus to leave the language as encourage and
to note in the minutes that staff should develop application language that
clearly communicates the benefits to homeowners of using a
professional tree service or arborist for permit submissions.
Task Force Continuity
Mr. Quick raised the question of whether the report included any
language contemplating that some form of the Task Force should remain
active to help shepherd implementation of the recommendations. Ms.
Farrell noted that the cover letter to the report included a specific request
for a workshop to reconvene the group. She explained that if Town
Council directed staff to proceed with ordinance drafting, staff would
bring a redlined version of the existing ordinance back to the Task Force
for review before sending it through the public hearing process with the
Planning Commission.
DRAFT
Tree Task Force
July 30, 2026
Page 5 of 9
Mr. Quick asked whether the group would formally disband upon
presentation of the report. Farrell noted that the enabling resolution
authorized the Task Force for one year, which had effectively elapsed,
but that Council had authority to extend the group as needed.
Ms. Kennedy asked whether the group needed to take any formal action
regarding the proposed workshop. Farrell indicated the request was
already documented in the report and that it would be part of Chair
McKee’s presentation to Council.
EDS Data
Ms. Kennedy raised a concern, previously discussed with Chair McKee,
about the absence of EDS (Engineering and Development Services)
data on tree removal numbers. She asked whether the report should
note that all recommendations were based on planning data rather than
EDS data. Ms. Farrell confirmed that the report's recommendations
already addressed the need for improved tracking going forward, and
that the absence of historical EDS data was acknowledged implicitly as
something the Town needed to remedy. The group was satisfied that the
report addressed this prospectively rather than retroactively.
Category 4 Tree Replacement Language — Pages 29–30
Ms. Harris raised a concern about language on page 29 stating that
exclusions should be eliminated and that one-for-one replacement
should be required for all trees in all conditions. She questioned whether
this was the Task Force's actual intent, particularly for category 4 trees,
which include invasive species and trees not typically requiring a permit
for removal.
Ms. Kennedy clarified that the original intent was to encourage
replacement even for dead, dying, diseased, or invasive trees, including
category 4, because replacing canopy was important regardless of the
species removed. Ms. Harris pointed out a procedural difficulty: if a tree
does not require a permit to remove, there is no mechanism to require
replacement, and attempting to enforce replacement on unpermitted
removals would be difficult and potentially counterproductive.
Ms. Farrell noted that if the Town moved toward a system of required
permitting and tracking, replacement could theoretically become an
enforceable requirement, but acknowledged that the ordinance had not
yet been drafted to that level of detail.
Mr. Grice suggested that the language could be changed to encourage
landowners to replace category 4 trees rather than require it, which he
believed would resolve the practical and legal concerns raised. Ms.
DRAFT
Tree Task Force
July 30, 2026
Page 6 of 9
Harris agreed that a campaign-style or strongly-encouraged approach
would be more workable than an enforceable mandate for this category.
Ms. Kennedy expressed some concern about losing the ability to track
canopy numbers without a permit requirement, but ultimately
acknowledged the administrative complexity of requiring permits for
category 4 trees.
Mr. O'Neill proposed that the Task Force recommend encouraging one-
for-one replacement for category 4 trees rather than requiring it, and that
the language in the report be amended accordingly.
Ms. Mansour asked if there was a consensus to amend the report to
change the language on category 4 tree replacement from require to
encourage one-for-one replacement. Mr. Quick abstained and all
others were in agreement.
Mr. Quick explained his abstention by noting that pine species — many
of which are native — are classified in category 4, meaning that under
the current framework a property owner could remove a pine tree
without any replacement obligation. He expressed particular concern
about the ecological value of pines as wildlife habitat, having recently
observed herons and eaglets nesting in tall pines in his neighborhood.
Pine Species Classification
Mr. Quick asked whether the Task Force was still satisfied with all pine
species being classified in category 4, including longleaf pine. Ms.
Kennedy acknowledged she had previously suggested moving pines to
category 3 but had not pressed the issue. Mr. Lubert clarified that pines
24 inches in diameter at breast height and above are currently treated as
category 2 for mitigation purposes, and that buffers throughout the Town
also provide additional protection for pines regardless of category.
Mr. Quick formally suggested moving longleaf pine to category 1 and all
other pine species to category 3. He argued that longleaf pine is
ecologically significant — historically, the Mount Pleasant area was a
longleaf pine ecosystem prior to European settlement — and that
placing longleaf in the same category as invasive species sent the
wrong message about its value.
Ms. Harris expressed support for protecting pines in the 16-to-24-inch
range, noting that a majority of tree removals involve pines and that they
provide meaningful environmental value. She also raised a concern that
if pine species were moved to category 3 and a 16-inch threshold were
adopted, 16-inch pines on residential lots could become very difficult to
remove, potentially causing property owners to preemptively remove
DRAFT
Tree Task Force
July 30, 2026
Page 7 of 9
smaller trees before they reach a protected size. She acknowledged that
this was a balance to be struck.
Ms. Mansour asked Mr. Lubert whether moving pines to category 3
would affect the Board of Zoning Appeals process. Mr. Lubert confirmed
that only category 1 and 2 trees go to the BZA, so moving pines to
category 3 would mean that pine removals — regardless of size —
would remain at staff discretion rather than going to the BZA. Moving
longleaf specifically to category 1 would, by contrast, subject longleaf
removals to BZA review.
Mr. Grice noted that longleaf pines naturally grow in sandy upland soils,
which is precisely where residential development tends to occur,
contributing to the significant loss of longleaf from the landscape. He
disclosed that he personally has four large longleaf pines on his property
and abstained from the vote on that basis. Harris noted that professional
tree services submitting permit applications would be well-equipped to
correctly identify longleaf versus other pine species, reducing concerns
about misidentification.
The group agreed to recommend moving longleaf pine to category 1 and
all other pine species to category 3.
Ms. Mansour asked if there was a consensus to amend the report to
reclassify longleaf pine as category 1 and all other pine species as
category 3. Ms. Mansour, Ms. Kennedy, Mr. Oswald and Mr. Quick
were in favor. Ms. Harris and Mr. Grice abstained. The report will
be amended.
Tree Program Leadership Position
Mr. Quick raised a concern about whether the report sufficiently
conveyed the importance of establishing a dedicated tree program
leadership position — an urban forest manager or equivalent. Ms.
Kennedy expressed concern that the position as described in the report
sounded more like an outreach or programmatic role than a decision-
making one with real authority over permits and executive-level
decisions, noting that the description of reimagining programs and
conducting community outreach could be performed by an intern.
Mr. O'Neill and Ms. Farrell noted that defining the specific job description
was beyond the scope of the report, but that the position was listed as
one of the primary recommendations, second only to canopy restoration.
Ms. Farrell emphasized that members of the Task Force would need to
continue to champion this recommendation as the report moves through
the public process. Mr. Quick added that the position should ideally be
DRAFT
Tree Task Force
July 30, 2026
Page 8 of 9
filled by an experienced professional, not a recent graduate, given what
he described as high turnover in that demographic and the need for
continuity in implementing the program.
Final Vote on Amended Report
With no further questions or comments, Ms. Mansour called for a vote to
approve the report as amended.
All members voted in favor of approving the amended report.
6. Discussion Regarding Next Steps and Presentation to Flood
Resilience Committee
Ms. Farrell outlined the following schedule and process for the report
moving forward:
Staff would incorporate the three amendments approved at this meeting
— the category 4 replacement language change, the pine
reclassification, and any related language adjustments — and distribute
the revised report to all Task Force members for final review. Members
were encouraged to flag any errors or needed clarifications.
The report is scheduled to be presented to the Flood Resilience
Committee on Monday, August 31, 2026. Ms. Farrell noted that the
meeting typically takes place during the day, starting in the morning, and
that the exact time is generally not confirmed until the end of the prior
week. She strongly encouraged as many Task Force members as
possible to attend in support. She said Chair McKee is expected to
present the report on behalf of the Task Force, with staff present to
address technical questions related to ordinance specifics or budget
matters.
Following the Flood Resilience Committee, the report would be
forwarded to the full Town Council for review and consideration. If
Council directs staff to proceed, staff would draft amendments to the
existing tree ordinance using a redline format and would bring that draft
back to the Task Force for a review workshop before the ordinance
proceeds to a public hearing with the Planning Commission. Ms. Farrell
estimated that the earliest the ordinance could reach the Planning
Commission would be December, given the time required for Council
deliberation and staff drafting.
If Council also approves the recommended tree program leadership
position, staff would develop a job description and move forward with
DRAFT
Tree Task Force
July 30, 2026
Page 9 of 9
hiring, noting that a budget adjustment could be handled at midyear if
needed.
Mr. Oswald asked for clarification on whether staff would be drafting an
entirely new ordinance or amending the existing one. Ms. Farrell
confirmed that staff would redline the existing ordinance, using it as the
baseline, and that the redlined version would be presented back to the
Task Force and ultimately to the Planning Commission.
7. Adjourn
There being no further business, Ms. Mansour adjourned the meeting at
9:16 a.m.
Respectfully submitted,
Christine Barrett
Clerk of Council
July 30, 2026
DRAFT
Source: Town of Mount Pleasant website. First collected Oct 13, 2026.