Common questions about the campaign

The team did serious engineering. Nothing in the campaign says they're wrong, lazy, or cutting trees for fun. Tree removal is expensive — they wouldn't do it absent a design that asked them to.

The question is what the design asked them to do. The FEIS Alternatives Chapter makes the answer clear: it lists 7 criteria for evaluating designs, and tree retention isn't one. Only 1 of 7 reaches has a tree-count comparison across alternatives. Tree retention was never a primary design objective.

That's why "the engineers planned 500" and "500 isn't necessary" can both be true. 500 is what the current brief produces. A brief that starts from tree retention produces a different number.

Other coastal-resilience and levee projects show what happens when the brief is revisited. Miami's $4.6B Biscayne Bay seawall — scrapped and redesigned around nature-based alternatives. San Antonio — 105 removals dropped to fewer than 50. Coeur d'Alene — 1,000 mature pines ordered cut, only the dead ones were. Different agencies and contexts, but the pattern is consistent: when the design brief changed, the tree count changed.

The ask isn't "overrule the engineers." It's "give them a brief that takes saving the trees seriously."

It's not binary. "Necessary for the wall" depends on which wall. There are many possible designs that meet the resilience objective; BPCA built one, and in that design 500 trees fall. They have not designed a version where retention is a starting input — the FEIS Alternatives Chapter is the record.

That's the campaign's only claim. Not that the engineering is wrong. Not that the wall isn't needed. That a 40% mature-canopy loss should not stand on a design process that never asked "what if we tried to save them?"

Until that alternative exists on paper, "the trees must go" is a statement about this design, not about resilience.

No personal expertise, and none claimed. The campaign rests on public documents: BPCA's Final Environmental Impact Statement (May 2025), the post-FEIS Technical Memorandum (Dec 2025), BPCA's own reply to community inquiries, and the Battery Alliance lawsuit (Nov 2025). Each claim links back to a primary source on the main page.

And the point isn't that residents have to out-engineer BPCA. It's that authorities don't get the last word on a 40% canopy loss without an alternatives analysis that tries to save trees. Miami, Sacramento, San Antonio, Coeur d'Alene, Virginia — every one of those started with an authority saying "this is necessary." The design changed because people kept asking. Believing BPCA's framing without question is how the 500-tree number stands; pushing back is how it moves.

A 40-year-old tree intercepts 1,000+ gallons of stormwater a year, cools blocks, and captures carbon. Replacements won't match that for 20–30 years. About a third of the new trees will be 4–8" caliper; the rest are 3" caliper or smaller multi-trunk species. A project sold as resilience is cutting the trees that absorb the most stormwater.

The visible cutting in south Battery Park is the leading edge, not the bulk. The biggest losses by count haven't begun:

• Reach 1 (Route 9A / West St / Tribeca) — 119 trees.
• South Esplanade — 139 trees, ~80% of the area.
• Brookfield Place / North Cove — 121 trees.

Other coastal-resilience and parks projects all started where this one is — agencies saying the cuts were needed, residents being told they were too late. Miami, San Antonio, Coeur d'Alene, Virginia — the numbers changed when people kept pushing past the first reply.

"Are they listening?" is the wrong test. Movement isn't a function of listening — it's a function of political cost. BPCA's board is appointed by the Governor; it operates in the Mayor's city; its funding and oversight run through Albany. When the cost of holding a number gets high enough — voters above the agency asking the same question, press coverage on the record, lawsuits in the pipeline — the number moves. That's how Sacramento, San Antonio, and Coeur d'Alene moved. Not because the agency suddenly cared.

The email is one piece, not the answer. What raises the cost is sustained, multi-channel pressure — press, neighbor-to-neighbor organizing, flyers, @treesbpc, CB1, the pending Battery Alliance lawsuit, and the email's cc list of 30+ officials with authority over BPCA but outside its SEQRA response loop. None alone. Together is how the political math changes.

Success here doesn't mean "stop the wall." It means BPCA finally does the analysis they haven't: a retention-first alternative for each reach, per-tree justification, independent review. Reach 1 alone jumped from 65 trees to 119 between the FEIS (May 2025) and the updated impact map (May 2026). If pressure pulls that back even halfway, that's 25+ mature trees that stay. Any number we move is the win.

Replacement isn't a concession being asked for — it's the existing plan. The 525-sapling number sits in every BPCA communication, including the May 2026 reply. Pushing for replacement is pushing on an open door.

The mature trees are what residents lose. A 40-year tree intercepts 1,000+ gallons of stormwater a year. Saplings won't match that on shade, stormwater, or carbon for 20–30 years. That's the cost being absorbed.

The trees that can still be saved are the ones still standing in Reaches 1–6. That's what every email this month is about.

Reasonable people can disagree about whether to push back. But "fair trade-off" assumes there's a trade-off on the table. Right now there isn't one — no alternative was ever designed around saving the trees, so the only plan to weigh 500 against is the one that cuts 500.

Miami, Sacramento, San Antonio, and Coeur d'Alene all started where we are: residents were told the cuts were necessary. Once a retention-first alternative was put on paper, the trade-off looked very different. The ask isn't "save every tree" — it's "put a real choice on the table." That hasn't happened here.