Saving Oaks and Stony Run: Remington's Stand Against Hopkins' AI Institute
Hopkins' DSAI build meets Remington resistance over noise, trees, parking, and runoff. Builders: control water, protect canopy, enforce conduct, communicate clearly.

Hopkins' DSAI vs. Remington: Practical Takeaways for Builders and Developers
On the edge of Johns Hopkins' Homewood campus, a major research build is colliding with a tight-knit neighborhood. Residents on Remington Avenue are pushing back over noise, worker behavior, parking, tree removal, and stormwater runoff into Stony Run.
For construction and real estate professionals, this is a case study in execution risk. The work is legal and permitted - but the court of public opinion can stall momentum, add cost, and damage reputation if not managed well.
Project snapshot
- Two new buildings at Wyman Park Drive and Remington Avenue; roughly four-year timeline.
- Estimated 11,000 jobs and $1.6B in economic impact during construction and ramp-up.
- Program scale: larger combined square footage than CFG Bank Arena; 140 new faculty and researchers; 750 doctoral students.
- No special zoning variances required; built on university-owned land; no extra tax breaks.
Community temperature check
Residents cite daily friction: construction noise, rude interactions, litter, loss of parking, planned removal of mature oaks, and runoff into Stony Run. Some see a pattern with the university and fear a slow push that eventually prices them out or buys up the block.
Local leaders describe a sense of inevitability. University officials say there is no plan to acquire homes on Remington Avenue and point to long-term citywide benefits. The trust gap remains.
Environmental compliance: don't learn this lesson on Instagram
A viral video showed stormwater from a nearby site flowing toward Stony Run. A fence went up after a city inspection. Community groups say they'll continue active oversight.
- Own rainfall events: pre-storm checks, during-storm monitoring, and post-storm corrective actions.
- Use layered BMPs: stabilized entrances, check dams, inlet protection, silt fence backed by wattles, sediment traps, and wheel-wash stations.
- Field-verify SWPPP details weekly; add third-party turbidity checks after major rain.
- Document and publish fixes within 48 hours; keep a public change log.
Trees and urban canopy: precision beats promises
The plan removes 102 trees, including 30 in the public right-of-way, with a pledge to plant 300 replacements and install at least 25-foot trees in the right-of-way. Neighbors want to save nine scarlet oaks along the planned construction entrance.
- Engage an ISA-certified arborist to map critical root zones and redesign access where feasible.
- Maximize preservation with air-spade root exposure, trunk/branch protection, and no-dig fencing at dripline+
- Front-load replanting in early phases; specify caliper, species diversity, and soil volumes; commit to a three-year establishment plan with watering and mortality guarantees.
- Publish a tree-by-tree matrix: status, mitigation, replacement location, and size.
Workforce conduct and site logistics
Complaints include littering, confrontations, and workers parking on residential blocks despite directions. These small frictions inflate into political problems.
- Mandatory code-of-conduct briefings at orientation and weekly tailgates; one-strike policy for harassment or littering.
- Signed parking plan with enforcement: permits, off-site lots, shuttle schedules, and penalties for violations.
- Housekeeping by 3 p.m. daily: sweep, bag, and remove; supervisor photo report to the owner and community portal.
- Visible QR code at site gates linking to a hotline, response SLAs, and a live issue tracker.
Communication that actually calms a neighborhood
Fourteen meetings haven't closed the gap. Residents complain of slow responses and a stale website.
- Publish a two-week cadence dashboard: schedule look-ahead, noise windows, lane closures, tree work, and BMP status.
- Set service levels: acknowledge complaints in 24 hours, resolve or update in 72 hours.
- Hold monthly walk-throughs with resident reps and environmental groups; document field notes and actions.
- Share a site logistics map with haul routes, delivery windows, and flagger posts.
Housing optics and market impacts
The research build will attract high-earning faculty, researchers, and graduate students. That pressures a block of modest rowhomes and nearby rentals.
- Voluntary commitments: no acquisition of owner-occupied homes for X years; if acquisitions occur, offer above-market plus relocation support.
- Seed a neighborhood housing fund for repairs, tax relief, and anti-displacement programs; report outcomes quarterly.
- Cap student master-leasing in target zones; support inclusionary and mixed-income units in private developments.
- Partner with CDCs for scattered-site preservation and small landlord support.
Governance and approvals
The project doesn't rely on variances or special incentives, and planning approvals are moving. The real risk is political - a perception that the university "wins" by default.
- Convert meetings into agreements: measurable commitments, timelines, and named owners.
- Use a community benefits framework tied to milestones and payment holdbacks.
AI build, AI workforce
This institute is a magnet for capital, labs, and specialized space. It will also set expectations for how contractors use AI for scheduling, estimating, QA/QC, and safety.
- Audit your tech stack: scheduling assistants, takeoff tools, progress capture, and claims analysis.
- Upskill PMs and supers on practical AI workflows to reduce RFIs, rework, and idle time.
Practical AI skills by job role can help teams prepare for the talent bar these projects set.
Action checklist for project teams
- Stormwater: verify BMPs weekly, add rain-event inspections, publish corrective logs.
- Trees: ISA plan, save-where-possible entrance redesign, and early, large-caliper replacements.
- People: code-of-conduct enforcement, litter zero-tolerance, and controlled parking with penalties.
- Transparency: live dashboard, hotline with SLAs, and monthly joint walk-throughs.
- Neighborhood: housing fund, acquisition moratorium or rules, and master-leasing caps.
- Delivery: define measurable community benefits with milestone-based enforcement.
- Capability: equip teams with AI-enabled planning, estimating, and QA/QC tools.
Bottom line
The build will likely proceed. Whether it becomes a regional success story or a cautionary tale depends on how well the team manages water, trees, traffic, and trust - every week, without fail.
Earn the social license, and the rest follows.