HOA Mocked My Wall — Then the Flood Turned It Into Their Biggest Regret 🚨

Hinzugefügt: 2026-05-10

[00:00:00]The night the stormwater system at Clearwater Ridge HOA failed during the worst rainfall event Central Tennessee had recorded in 44 years, sending 18 inches of water across the development's common area and into 11 of the Eastern Cluster homes, while my property sat dry behind the retaining wall the board had spent 14 months trying to force me to demolish.

[00:00:24]I was in my kitchen watching the rain gauge on my back fence read 7.2 inches in 6 hours and monitoring my drainage system's performance through the sensor array I had installed 2 years earlier.

[00:00:38]And I want to tell you that what I felt was not the satisfaction that this kind of story is supposed to produce, but the specific complicated grief of someone who had warned people accurately and completely and had not been believed and was now watching the consequences of that disbelief arrive in the form of 18 inches of water in 11 families living rooms.

[00:01:01]My name is Conrad Aldridge. I am 56 years old, a licensed civil engineer specializing in hydrology, stormwater management and drainage infrastructure with 29 years of experience in residential and municipal water systems and I have lived on the Eastern boundary of the Clearwater Ridge HOA development in Central Tennessee for 8 years.

[00:01:25]My property sat at the low point of the development's Eastern drainage watershed, which was a fact I had understood before I bought the house and which had been the primary engineering consideration in every site improvement decision I had made in the 8 years since.

[00:01:44]The retaining wall was the central site improvement and I want to describe it with the precision it deserves because the precision is the story.

[00:01:53]When I bought the property the Eastern edge of my rear lot terminated at grade break where the land dropped approximately 4 feet over 12 horizontal feet toward a drainage swale that carried storm water from the development's eastern cluster toward the regional detention basin 400 m to the south.

[00:02:11]The swale was HOA infrastructure, part of the original development's approved storm water management plan, and it ran along the rear boundary of the eastern lots, including mine.

[00:02:22]My lot was at the lowest elevation point in the eastern cluster, which meant that during significant rainfall events, the storm water from six upstream lots, plus the development's common area, drained through my property's swale segment before reaching the regional detention basin.

[00:02:40]I had recognized immediately that this configuration created a risk condition that the original development had not adequately addressed.

[00:02:49]The swale's design capacity was adequate for the rainfall events that the development's engineers had used as their design basis when the development was built 18 years ago.

[00:03:01]The design basis, I had determined by reviewing the original storm water management plan that was on file with the county, had been the 10-year storm event, meaning a rainfall of the intensity and duration that statistically occurs once every 10 years on average.

[00:03:19]The problem was twofold. First, the regional storm water infrastructure had been built on a 10-year design basis, but the development had grown over 18 years, and the upstream impervious surface area had increased, meaning more water was entering the swale per unit of rainfall than the original design had assumed.

[00:03:40]Second, the climate data for central Tennessee showed a statistically significant increase in the frequency of high-intensity rainfall events in the preceding two decades that made the original 10-year design basis increasingly conservative.

[00:03:57]I had documented both of these problems in a written assessment I prepared in my second year on the property and had submitted to the HOA board in year three when I formally proposed a swale capacity improvement project.

[00:04:12]The board at that time was led by a president named Howard Garrison who had been in the position for four years and who had the practical competence of someone who had been managing a community's infrastructure for long enough to understand that infrastructure required maintenance and that ignoring professional recommendations had consequences.

[00:04:34]Howard had read my assessment, asked three specific technical questions at a board meeting, and authorized an engineering review by the HOA's retained civil engineer, a man named Dale Morris, who had designed several of the development's common area improvements over the years.

[00:04:53]Dale Morris had reviewed my assessment and submitted a report to the board that substantially agreed with my analysis while noting that the project scope I had proposed was larger than what he believed was necessary. Dale recommended a partial capacity improvement focused on the swale's downstream segment, which he estimated at a lower cost than my full proposal.

[00:05:14]Howard had presented both options to the board and the board had approved Dale's modified scope.

[00:05:20]The work had been done in year four and had improved the swale's downstream capacity but had not addressed the upstream segment adjacent to my rear lot.

[00:05:30]I had noted my disagreement with the partial scope in writing to Howard. He had acknowledged my concern, explained the budget constraint, and said the upstream segment would be addressed in a future budget cycle.

[00:05:44]Howard had retired from the board in year five and had moved to be near his daughter in North Carolina.

[00:05:51]The board that came after Howard had different priorities. The new president was a woman named Beverly Ashford, who was 60, recently retired from a career in event management, and who had run on a platform of community aesthetics and property values.

[00:06:05]Beverly had energy and organizational skill and a genuine commitment to the community's appearance and a limited interest in what she described at her first board meeting as the technical minutia of storm water infrastructure.

[00:06:19]In year six, Beverly's board had commissioned a landscape redesign of the common area.

[00:06:25]The redesign included a pathway improvement project that rerouted a section of the eastern common area pathway across the upper portion of the drainage swale's upstream segment, installing a decorative bridge structure over the swale that was aesthetically appropriate and hydraulically problematic because the bridge abutments reduced the effective cross-sectional area of the swale at its most critical upstream location by approximately 30%.

[00:06:53]I had attended the board meeting where the landscape design was presented and had raised the hydraulic concern specifically and with technical detail.

[00:07:01]Beverly had thanked me for the input and had noted that the project's landscape architect had confirmed the design was appropriate. The landscape architect's confirmation, as I learned by reviewing the project documents through a public records request, had been based on a site observation rather than a hydraulic analysis and had not included any assessment of the swale's capacity under storm conditions.

[00:07:28]I had sent a written technical objection to Beverly, to the board, and to Dale Morris after the meeting.

[00:07:35]Dale Morris had reviewed the bridge design and confirmed my hydraulic concern in a memo to the board.

[00:07:41]The board had voted four to 2 to proceed with the design anyway, with Beverly arguing that the bridge was a minor feature whose aesthetic value justified the limited hydraulic compromise.

[00:07:53]In year seven, I had built my retaining wall.

[00:07:57]The wall served two purposes that I want to be precise about because both purposes were legitimate, and the combination of the two is what the board had found objectionable.

[00:08:09]The first purpose was erosion control on my rear lot. The grade break at the rear of my property had been eroding progressively over eight years, with each significant rainfall event removing soil from the break face and depositing it in the swale.

[00:08:24]The erosion was visible, documented in photographs I had taken annually, and was contributing to the swale's capacity reduction by adding sediment load.

[00:08:34]A retaining wall at the grade break was the standard civil engineering solution to this specific erosion condition.

[00:08:42]The second purpose was what the board had found objectionable, which was that the wall incorporated a controlled flow structure at its base that allowed me to manage the rate at which storm water from my rear lot entered the swale during significant rainfall events.

[00:08:59]The controlled flow structure was a gated outlet in the wall's base, designed to release water at a controlled rate that would not exceed the swale's current reduced cap capacity. With excess water stored temporarily in a small detention area I had graded into the rear lot above the wall.

[00:09:19]The controlled flow structure meant that during significant rainfall events, my property would temporarily detain storm water above the wall and release it at a controlled rate rather than contributing instantaneous peak flow to the already stressed swale system.

[00:09:34]From a watershed engineering perspective, this was a best management practice, a private property improvement that reduced the peak load on downstream infrastructure at my own expense.

[00:09:46]From Beverly's perspective, it was an unauthorized modification to the swale drainage pattern that required HOA approval under the community's stormwater management policy.

[00:09:58]She was technically correct that the modification affected the drainage pattern. She was technically incorrect that this was a problem.

[00:10:05]Dale Morris, when I asked him to review my wall design before construction, had told me it was a hydraulically sound improvement that would reduce the risk of swale overflow during significant events. He had offered to provide a letter to the board supporting the design.

[00:10:22]Beverly had declined Dale's offer and had instead retained a different engineer, a young civil engineer from Nashville, who had reviewed my wall design without the eight years of site familiarity Dale Morris and I had, and who had produced a report concluding that the controlled flow structure's detention function could create backwater conditions in my rear lot during extreme events that might exceed the wall's design capacity.

[00:10:48]The report was not wrong technically. It was correctly identifying a scenario in which my wall's storage capacity could be exceeded during an extreme event, which would result in water overtopping the wall and flowing in an uncontrolled manner.

[00:11:05]What the report did not address was what would happen at the same location during the same extreme event in the absence of my wall, which was that the uncontrolled peak flow from my lot would contribute to swale overflow that was more dangerous than the controlled backwater scenario the engineer had identified.

[00:11:25]I had prepared a written response to the report that made this comparison explicitly. I had modeled both scenarios at the 25-year storm event and shown that my wall design produced lower downstream peak flows and lower swale overflow volumes than the no wall scenario in every modeled condition. The response was 14 pages with supporting calculations.

[00:11:48]Beverly had presented my response to the board. The board had voted four to two to require me to remove the controlled flow structure from my wall citing the retained engineers report and noting that private residents should not be modifying community drainage infrastructure even with benevolent intent.

[00:12:08]I had filed for an injunction. The injunction hearing had produced a ruling that I could maintain the wall but that the controlled flow structure required county approval as a stormwater management improvement because it affected the downstream drainage system.

[00:12:24]I had applied for and received the county approval within 6 weeks.

[00:12:28]The county stormwater management reviewer, a woman named Patricia Simmons, who I had worked with on two prior projects, had reviewed my design, agreed with my hydraulic analysis, and approved the structure with minor modifications to the outlet sizing that improved its performance.

[00:12:47]Beverly had called the county stormwater management office after the approval and had been told by Patricia Simmons that the controlled flow structure had been reviewed and approved and that the review had found it to be an appropriate private property stormwater improvement.

[00:13:03]Beverly had escalated to the county engineer who had reviewed Patricia's decision and affirmed it.

[00:13:10]She had then written me a letter on HOA letterhead stating that while the structure was apparently county approved, the board continued to find it inconsistent with community standards and would be monitoring the situation for any evidence of impact on common area drainage infrastructure.

[00:13:29]I had filed that letter in my documentation folder alongside Dale Morris's letter, the county approval, Patricia Simmons's review memo, and the 14 pages of technical response I had prepared to the Nashville engineers report.

[00:13:45]The board had been monitoring the situation for 14 months when the 44-year rainfall event arrived.

[00:13:52]I had been monitoring it more carefully.

[00:13:54]My sensor array had been tracking the swale's water level, my wall's upstream detention areas water level, the controlled flow structure's outlet rate, and the rainfall accumulation at 5-minute intervals throughout the storm event. Every data point was logged to my cloud account with timestamps.

[00:14:14]At 11:37 in the evening, the swale exceeded bank full stage for the first time. My controlled flow structure had been releasing water at its designed rate for 4 hours by that point, managing my lot's contribution to the swale system at a rate that the swale could accommodate. The bank full condition was driven by the upstream contributions from the six upstream lots and the common area, not by my lot's contribution.

[00:14:40]At 11:52, the bridge abutments that Beverly's landscape project had installed became a hydraulic control point as the rising swale stage backed water against the reduced cross-section.

[00:14:53]The backwater extended upstream, compounding the bank full condition that was already occurring from the upstream contributions.

[00:15:02]At 12:19, the swale overflowed its eastern bank at the bridge location.

[00:15:07]The overflow found the path of least resistance across the common area pathway and toward the eastern cluster homes.

[00:15:16]My wall held. My detention area was at approximately 60% capacity. My controlled flow structure was releasing water at its design rate. My rear lot was wet but contained. My house was dry.

[00:15:30]At 12:47, my phone showed alerts from the community's emergency notification system. 11 households reporting water intrusion. The development's common area was inundated. The regional detention basin, which Beverly's engineer had apparently assumed would capture the overflow, was at capacity and not accepting additional inflow.

[00:15:53]I put on my rain gear and went outside to check my wall and sensors. The rain was still heavy, but the peak appeared to have passed. My wall was performing correctly. The upstream detention area was managing the continued inflow from my roof and rear lot. The controlled flow structure was releasing water at the correct rate.

[00:16:14]I walked to the common area boundary and looked at the situation. The pathway was flooded. The bridge was submerged. The water had found the low points in the eastern cluster and the homes at those low points had water in them.

[00:16:29]I went back inside and sat at my kitchen table and looked at the sensor logs on my laptop and thought about the 14-page response that had not been read carefully enough and the county approval that Beverly had contested. And the 14 months of monitoring that had not included any of the capacity analysis that would have allowed the board to understand what their infrastructure's vulnerability actually looked like.

[00:16:54]I called James Waller at 7:00 the next morning. He said, "I heard about the flooding."

[00:17:00]I said, "11 homes. My property is undamaged. My wall performed as designed throughout the event. I have sensor logs for the entire event with 5-minute data intervals."

[00:17:12]He said, "The sensor logs show your property's contribution to the swale during the event.

[00:17:19]I said my logs show that my controlled flow structure released water at the designed rate throughout the event. The swale overflow did not originate at my property. The overflow originated at the bridge section and upstream.

[00:17:34]James said the board's retained engineer report said your structure could create backwater conditions.

[00:17:41]I said it did not create backwater conditions. The upstream detention functioned correctly. The backwater that caused the overflow was caused by the bridge abutments reducing the swale's cross-section during the elevated flow event.

[00:17:57]James said you told them that.

[00:18:00]I said in 14 pages with supporting calculations in year seven.

[00:18:06]He said the flooding affected 11 homes.

[00:18:09]I said, yes.

[00:18:11]He said those homeowners are going to be looking for causes.

[00:18:16]I said the cause is a storm water system that was designed for a 10-year storm degraded by increased upstream impervious surface and further compromised by a landscape project that reduced the critical cross-section of the swale by 30%.

[00:18:32]I documented all three of these conditions in writing to the board before the event.

[00:18:38]James said send me everything. I mean everything. The year three assessment, the year six hydraulic objection, the response to the Nashville engineers report, the county approval, every communication with the board over eight years.

[00:18:53]I said I will send it this morning.

[00:18:56]I sent it within two hours. The documentation package was the most complete technical record I had assembled in 29 years of practice because I had been building it for eight years with the specific attention of someone who understood that the situation they were documenting would eventually be examined under circumstances where completeness mattered.

[00:19:18]James reviewed it over the weekend and called me Monday morning. He said, "The Nashville engineers report addressed your wall's backwater scenario, but did not model the no wall scenario for comparison."

[00:19:32]I said, "Correct."

[00:19:34]He said, "The board approved the landscape project's bridge design without a hydraulic analysis."

[00:19:40]I said, "Correct. Dale Morris's memo raising the hydraulic concern was not acted on."

[00:19:47]He said, "Dale Morris's memo is in the file."

[00:19:51]I said, "Yes, six. I was copied on it."

[00:19:54]James said, "The 11 affected homeowners are going to file claims against the HOA. The HOA's insurance carrier is going to conduct a causation investigation. What that investigation is going to find when it encounters your 8-year documentation package is going to be significant."

[00:20:14]I said, "The causation is clear and documented. The bridge abutment restriction is the primary hydraulic cause of the overflow. The board had written notice of the hydraulic concern before the project was approved."

[00:20:29]He said, "And your wall."

[00:20:31]I said, "My wall reduced my property's contribution to the swale peak flow during the event. The sensor logs are unambiguous on this point. My wall is not a cause of the flooding. It is a mitigating factor that reduced the severity of the event at my property."

[00:20:49]James said, "I want to proactively share your documentation with the HOA's insurance carrier before they begin their formal investigation. I want them to have the complete picture of what the board knew, when they knew it, and what they chose to do."

[00:21:05]I said, "Yes."

[00:21:07]He sent the documentation package to the carrier's claims department with a cover letter that James described as forensically organized in a way that left no analytical ambiguity about the sequence of events and the board's knowledge at each step.

[00:21:24]The carrier's investigation took 6 weeks. Their engineering consultant reviewed the documentation and the physical site and the event data. The consultant's report, which James obtained through the claims process, found that the primary cause of the flooding was the hydraulic restriction created by the bridge abutment installation and that the board had received and not adequately acted on written notice of this risk before the project was approved.

[00:21:51]The report further found that the private storm water improvement at my rear property had performed as designed and had not contributed to the flooding event.

[00:22:01]Beverly Ashford called me the week after the consultant's report was released.

[00:22:06]She used a voice I had not heard from her in 4 years of interaction, a quiet voice without the organizational energy that usually characterized her communications.

[00:22:17]She said, "The report confirmed your analysis."

[00:22:21]I said, "Yes."

[00:22:23]She said, "I want to understand what should have been done differently."

[00:22:27]I said, "The hydraulic analysis that Dale Morris's memo requested should have been completed before the bridge project was approved. The analysis would have identified the cross-section reduction as a risk factor. The project could have been redesigned to maintain the full swale cross-section while achieving the aesthetic objective."

[00:22:49]She said, "It could have been both."

[00:22:51]I said, "Hydraulically adequate bridge designs are common. The span and abutment configuration simply needed to be selected for hydraulic clearance rather than only for aesthetics. the cost difference would have been modest.

[00:23:06]She said, "No one did that analysis."

[00:23:09]I said, "No."

[00:23:11]She said, "Because I said we did not need it."

[00:23:14]I said, "The board voted to proceed without it, yes."

[00:23:18]She was quiet for a moment, then she said, "What needs to happen now?"

[00:23:23]I said, "The bridge needs to be replaced with a hydraulically adequate design.

[00:23:28]The swale's upstream segment adjacent to my property needs the capacity improvement that I proposed in year three and that was deferred for budget reasons. Dale Morris can design both. I will provide peer review at no charge."

[00:23:43]She said, "You will help."

[00:23:45]I said, "I will help because 11 families had water in their houses and because the creek and the storm water system that drains to it are going to keep being my neighbors for as long as I live here.

[00:23:57]My interest in the system functioning correctly is not contingent on whether I was right or wrong in the dispute about my wall."

[00:24:06]She was quiet again, then she said, "I misjudged you."

[00:24:10]I said, "You had a technical concern about my wall that was legitimately raised and properly reviewed. The county review found it was appropriate. The misjudgment was not in questioning my wall. It was in approving the bridge project without the analysis that your own engineer recommended."

[00:24:29]She said, "That distinction is important to you."

[00:24:32]I said, "Accurate attribution of causes matters in engineering and it matters in life. You were not wrong to question my wall. You were wrong to approve the bridge without adequate analysis."

[00:24:45]She said, "I appreciate that."

[00:24:48]The HOA's insurance covered the claims from the 11 affected homeowners at a total of approximately $340,000.

[00:24:56]The carrier subrogated against the landscape design firm that had produced the bridge design without hydraulic analysis and eventually settled that claim for a portion of the total.

[00:25:07]The HOA's reserve fund was depleted and required a special assessment.

[00:25:13]Beverly resigned from the board 2 months after the event. Her resignation letter, which Gerald Alderman shared with me, was three paragraphs and was honest in the specific way of someone who had understood something important and was not trying to avoid saying it.

[00:25:30]The bridge replacement was completed in the spring. Dale Morris designed a clear span structure with no abutment intrusion into the swale cross section.

[00:25:39]The hydraulic capacity through the bridge section was fully restored. The upstream swale improvement I had proposed in year three was also completed in the same project funded in part by the insurance recovery.

[00:25:53]I provided peer review of both designs as I had offered. Dale Morris and I had a productive professional collaboration on the project that benefited from the 8 years of site-specific data I had accumulated.

[00:26:07]The designs were better for that collaboration than either of us would have produced alone.

[00:26:13]My wall remained. The controlled flow structure operated correctly. The sensor array continued logging. The documentation folder continued growing.

[00:26:24]Gerald Alderman walked the completed infrastructure improvements with me on a May afternoon.

[00:26:30]He looked at the clear span bridge and then looked at my wall at the rear of my lot and said, "8 years."

[00:26:37]I said, "I wrote the first assessment in year two."

[00:26:40]He said, "And Beverly approved a bridge that reduced the swale capacity in year six."

[00:26:47]I said, "Without the hydraulic analysis that Dale Morris had recommended."

[00:26:53]He said, "If she had done the analysis."

[00:26:56]I said, "The analysis would have identified the problem. The project would have been redesigned or the bridge location would have been selected differently. The swale capacity would have been maintained. The October event would have been a high-water event rather than a flooding event."

[00:27:13]He said, "For the cost of an analysis."

[00:27:16]I said, "Dale Morris's hydraulic analysis fee would have been between $2,000 and $5,000 depending on the scope. The event cost $340,000 in claims plus the bridge replacement and swale improvement."

[00:27:32]He said, "You knew this would happen."

[00:27:35]I said, "I knew the hydraulic conditions made significant flooding a meaningful risk. I did not know when a sufficient storm event would arrive. I said one to three storm seasons in my written objection. It happened in the second storm season after the bridge installation."

[00:27:53]He said, "You were specific."

[00:27:55]I said, "I was accurate within the uncertainty that honest engineering acknowledges."

[00:28:01]He said, "The board did not read you as accurate. They read you as obstinate about your wall."

[00:28:07]I said, "Both things can be perceived simultaneously. I was defending my wall and I was accurately describing the storm water risk. The board focused on the wall dispute and did not engage with the storm water analysis."

[00:28:22]He said, "I want that to change."

[00:28:24]I said, "I have offered technical guidance to every board since I moved here. Howard Garrison used it. The subsequent boards engaged with it selectively. What changes is whether the board values technical input from a qualified resident with site-specific expertise or regards it as a stakeholder's self-interested position."

[00:28:46]He said, "How do we tell the difference?"

[00:28:48]I said, "You check the technical credentials, you verify the analysis against independent review, and you ask whether the person recommending action has any interest that is opposed to the community's interest." In this case, I have lived here for 8 years, and I want my home and my neighbors' homes to stay dry.

[00:29:07]My interest and the community's interest are aligned.

[00:29:11]He said, "I will remember that."

[00:29:14]We walked back from the creek. The stormwater system was functioning correctly for the first time in 2 years.

[00:29:20]The swale was carrying its normal spring flow without restriction. The bridge span was clean and properly proportioned. My wall was at the rear of my lot. The controlled flow structure closed at the current low flow conditions, the detention area empty and ready for the next significant event.

[00:29:38]I had built this wall for the reasons I said I built it. The documentation confirmed those reasons. The event had confirmed the analysis. The infrastructure had been improved because the event had made the improvement unavoidable.

[00:29:53]None of that was satisfying in the way the story wanted it to be satisfying.

[00:29:59]11 families had had water in their houses.

[00:30:02]That fact did not go away because I had been right, or because the documentation was complete, or because the board had ultimately agreed to the improvements I had recommended.

[00:30:14]What remained was the creek and the stormwater system and my property at the low point of the watershed and the work of making sure the system worked correctly for as long as I lived here.

[00:30:26]I went back to my workshop and updated the sensor logs with the post-improvement baseline readings.

[00:30:33]The data was good. The system was functioning within designed parameters.

[00:30:39]The work continued.

[00:30:41]It always would.

[00:30:43]Thumbnail text: He warned them for eight years with technical documentation. They built the bridge anyway. The rain made his case for him in six hours.