The rain stopped two hours ago and the property looks fine. The parking lot is dry. The grass is wet but not flooded. Nobody called to report anything. That is usually the moment a board stops thinking about drainage until the next storm, and it is exactly the wrong moment to stop.
A drainage system that "passed" a storm, in the sense that nothing overflowed onto a walkway or backed into a unit, can still be quietly failing. A pipe that is fifty percent blocked still moves water. A swale that has lost half its pitch still drains, just slower, and slower is invisible until the next storm is bigger than this one. The failures that matter most in Florida drainage are the gradual ones, and the only way to catch them is to look at the system while the evidence is still on the ground, not after it has washed away or dried up.
This is a guide to that look: the walk a board or a community association manager should take the same day a storm passes, what to check, in what order, and how to write it down so a pattern across a season becomes visible instead of forgotten. It is not about getting ready before a storm. That work, covered in Hurricane Drainage Check for Central Florida Communities and the August storm prep checklist, happens on a different calendar with a different goal. This article picks up after the rain has already fallen. The job now is assessment and documentation, not preparation.
Drainage systems leave evidence, and that evidence has a shelf life. Standing water that should have cleared tells you something different at the one-hour mark than it does the next morning, because by the next morning it may have soaked in or evaporated and the record is gone. Silt lines on a curb or a fence rail fade as they dry and get disturbed by foot traffic and irrigation. Scour marks at a pipe outfall get walked over, mowed over, or refilled by the next light rain before anyone photographs them.
The walk works best somewhere between one and three hours after the rain has fully stopped. Too early and the system is still actively draining, so normal function and a slow system look the same. Too late and the ground-level evidence of where the water actually went starts to disappear. If the property has multiple areas that drain at different rates, plan to hit the low points and pipe outfalls last, since those hold water longest and give you the most time.
This is also not a job for a single person walking fast. It works better as a slow, deliberate route, on foot, with a phone camera and something to write on. Driving the property is not the same inspection. Standing water two inches deep in a swale reads as "a little wet" from a car window and reads as a real problem from ground level.
The most useful way to structure the walk is to follow water downhill, the same path the storm followed, rather than walking the property in some other order like building by building. Water moves from roof to ground, from ground to swale, from swale to inlet, from inlet to pipe, and from pipe to an outfall or retention area. Checking the system in that sequence tells you not just where a problem is, but what fed it, which matters when you are deciding what to fix.
Start where water first hits the ground. At every downspout discharge point, look at where the water actually landed versus where it was designed to land. A downspout that used to discharge onto a splash block and now shows a fresh channel cut into the mulch or turf next to it has moved, or the splash block has moved, or something downstream of it is backed up and pushing water somewhere new. Note any erosion groove running away from a discharge point. That groove is a map of where extra water is going that the original design did not plan for.
Swales are the shallow channels that carry water from buildings and paved areas toward inlets or a retention area. Walk the length of every swale on the property, not just the ones near a building entrance. Look for standing water sitting in the middle of a run rather than moving toward its low end, which is the clearest sign the swale has lost pitch somewhere along its length. Look also for a fresh flattened or matted strip of grass showing where water actually flowed, which is often not exactly where the swale was designed to carry it.
At every catch basin and grate, check what is sitting on top of it and what is sitting in the throat below the grate. A storm moves debris, and a grate that was clear before the storm can be half covered in leaves, mulch, and loose landscape material after it. Debris on the grate is easy to see and easy to clear. Debris packed into the inlet below the grate is the more serious version of the same problem, and it is invisible unless someone lifts the grate and looks. If water was still standing over an inlet at the time of the walk, that is worth noting even if the inlet looks clear on top, since it may mean the blockage is further down the pipe.
Where a drainage pipe discharges, either into a pond, a ditch, or a lower section of the property, look at the ground immediately around the pipe end. Scour, meaning soil washed away in a fan pattern below the outfall, tells you the pipe was moving water under enough force to erode the ground it discharges onto. A small amount of scour after a heavy storm is normal. A pipe end that is undercut, with soil missing from beneath or around the pipe itself so the pipe appears to be hanging or exposed, is a structural concern, not a landscaping one, and it tends to get worse with every storm after it starts.
Finish at whatever collects the property's water last, whether that is a retention pond, a low corner of common ground, or a connection to a larger municipal system. Note the water level relative to any visible high-water marks from past events, whether the area is still actively receiving flow from pipes or swales feeding into it, and whether any area near it that should be dry is staying saturated well after the rest of the property has drained.
For a quick reference to carry on the walk itself, the same five stages reduce to a checklist:
A few terms come up repeatedly on this walk and are worth having a shared, plain-English definition for, since a board reading a manager's notes should not have to guess what they mean.
| Term | Plain-English meaning |
|---|---|
| Pitch | The slope of a swale or pipe that lets water move by gravity toward its outlet. Lost pitch means the slope has flattened somewhere along the run |
| Silt line | The faint deposit line water leaves behind on a curb, wall, or fence showing how high it rose during an event |
| Scour | Soil erosion caused by moving water, typically seen as a fan-shaped washed area below a pipe outfall |
| Undercutting | Soil eroded from beneath or around a structure, such as a pipe end, to the point the structure is no longer fully supported |
| Outfall | The point where a drainage pipe discharges its water, whether into a pond, a ditch, or another collection point |
| Retention area | A pond or low area designed to hold stormwater temporarily before it soaks in or is released gradually |
Walking the route produces observations. Turning those observations into a decision is the harder part, and it is where most boards either overreact to something cosmetic or underreact to something structural. The table below is built to sit next to your notes and translate what you saw into what it likely means.
| What you observe | What it usually means | What to do |
|---|---|---|
| Standing water in the middle of a swale, gone at both ends | The swale has lost pitch at that point, often from settling or repeated mowing pushing soil sideways over time | Mark the location and re-check after the next rain. If it repeats, this is a regrading job, not a one-time fix |
| Fresh silt line well above the normal grass line on a curb, wall, or fence | Water rose higher at that spot than it has recently, which may be a one-time storm intensity issue or a sign capacity is shrinking nearby | Photograph and measure the height against a fixed reference point. Compare to the silt line after the next storm |
| Debris packed into an inlet throat below the grate | The inlet's flow capacity was reduced during the storm, which likely slowed drainage across everything feeding that inlet | Clear the inlet and confirm it flows freely. If this repeats after every storm, look upstream for the debris source |
| Scour or a washed fan pattern at a pipe outfall | The pipe was discharging under enough force to move soil, which is expected during a heavy event to some degree | Note it. Only escalate if the scour is progressively larger after each storm or if it is undercutting the pipe itself |
| Soil visibly missing from beneath or around a pipe end | Ongoing erosion has outpaced the ground's ability to hold the pipe in place, a structural condition rather than a cosmetic one | Treat as a repair item, not a monitoring item. This tends to worsen with each additional storm |
| Ground that stays soft and spongy days after everything else has dried | Water is draining into that spot faster than it is leaving it, which can mean a blocked subsurface connection or a low spot with nowhere to go | Flag for a closer look at what feeds that area and where its outlet actually is |
| Downspout discharge landing somewhere new, with a fresh erosion channel | Something downstream of that downspout shifted, backed up, or the discharge point itself moved | Trace the water's new path and check what changed at the original discharge point |
A single walk after a single storm tells you what happened in that storm. It does not tell you whether a problem is a one-time event or a repeating pattern, and that distinction matters enormously for how a board should spend its attention and its budget. A swale that held water once during an unusually intense storm may be fine. A swale that holds water after every storm regardless of intensity has a real grade problem.
The only way to tell the difference is to compare notes across storms, at the same locations, over a season. That requires writing the walk down in a consistent format each time, which is where most boards fall short. The walk happens, someone mentions the parking lot looked fine, and no record survives to compare against the next storm.
The log does not need to be complicated. It needs to be consistent enough that the same location can be compared storm to storm. A simple table, kept in a shared document and filled in the same day as every walk, does the job.
| Date | Storm intensity (light, moderate, heavy) | Location | Observation | First time or repeat | Action taken |
|---|---|---|---|---|---|
| e.g. Inlet near the mailbox kiosk | e.g. Standing water, grate clear on top | ||||
| e.g. Swale along the east fence line | e.g. Water pooled at midpoint, drained by next day | ||||
| e.g. Outfall behind the retention pond | e.g. Fresh scour, no undercutting visible |
Once the same inlet or swale shows up as a repeat entry two or three storms in a row, the board has something a single walk never provides: proof that the issue is systemic rather than a one-off, which is the exact evidence needed to justify a repair line in the next budget cycle rather than another season of monitoring. If your board is heading into budget season without a line for this kind of recurring repair, that gap is common enough to have its own guide in The Recurring Lines That Get Left Out.
The same dated record is also useful well beyond the next budget cycle. A drainage component that keeps showing up in the log as a repeat problem is telling you something about where that component sits on its own condition timeline, which is exactly the kind of observation that should feed into longer-range planning rather than getting lost after the repair is made. For how to connect that kind of ground-level evidence to a property's broader component planning, see Reserves as a Maintenance Plan.
Not every observation from the walk needs a phone call the same week. Some genuinely just need to go in the log and get rechecked next time. The table below is a rough guide for sorting one from the other, built around how likely the issue is to get worse on its own between now and the next storm.
| Situation | Reasonable response |
|---|---|
| Debris on or in a grate, no standing water once cleared | Clear it as routine maintenance. No further action unless it recurs quickly |
| Standing water in a swale that clears within a day | Log it. Watch for a repeat at the same location next storm before acting |
| Standing water that has not cleared after two or three dry days | Worth a call. Slow-draining ground at this point is not a debris issue, it is a grade or subsurface issue |
| Scour at an outfall, pipe itself still fully supported by soil | Log it and photograph for comparison. Monitor across the next few storms |
| Any pipe end visibly undercut or hanging free of surrounding soil | Call promptly. This does not repair itself and tends to accelerate |
| A silt line noticeably higher than any previous mark at the same spot | Log and photograph. One high-water event is not proof of a capacity problem by itself, but it is worth watching closely |
| The same inlet or swale appearing in the log as a repeat for the second or third storm | Time to get someone to actually look at the grading or piping, not just monitor it again |
Ground-level drainage is only part of the picture, and a walk that stays entirely at ground level can miss a problem that is actually starting at the roofline. Wind load during a storm can pull a gutter run out of pitch without leaving any obvious sign from below, and the first symptom a board usually notices is water damage at a fascia board or a stained wall well after the storm that actually caused it. If your ground-level walk turns up water landing somewhere near a downspout that looks like it should not be getting that much flow, it is worth checking the gutter run feeding it before assuming the problem is at ground level at all. That inspection, and the specific tell that separates a healthy run from a failing one, is covered in What a Storm Does to a Gutter Run.
A single storm log entry is a data point. A season of them, covering several storms of varying intensity, is a maintenance case. By late storm season, most Central Florida properties have a clear pattern in their log: a handful of locations that show up once and never again, and a smaller set that show up every time. That second group is the one worth budgeting for, and having the log to point to turns a vague sense that "the back corner always floods" into a documented, dated pattern a board can act on with confidence instead of guessing at.
This same discipline of separating a one-time event from a genuine, worsening condition applies to more than drainage. It is the same logic that should drive decisions about aging fencing, cracking concrete, and other property elements that fail gradually rather than all at once. Keeping any kind of dated record, not just for drainage, is what turns "we think this has been getting worse" into a decision a board can defend at a meeting.
Generally between one and three hours after rain has fully stopped. Earlier and the system is still actively draining, so a slow system and a healthy one look similar. Much later and physical evidence like standing water and silt lines starts to fade or get disturbed.
Smaller storms are actually useful, since a system with real capacity should handle them with no standing water at all. If a swale or inlet shows a problem after a light rain, that is a stronger signal than the same observation after an unusually heavy storm.
Some soil movement at an outfall after a heavy storm is expected. It becomes a concern when the scour is getting visibly larger after each successive storm, or when soil is missing from beneath or around the pipe itself rather than just downstream of it.
Not necessarily. Debris on top of a grate is easy to spot and easy to clear. Debris packed into the inlet throat below the grate is invisible unless someone lifts the grate and checks, and it can still be slowing drainage even when the surface looks clean.
There is no fixed number, but once the same location shows up in the log for a second or third storm in a row, that is generally enough evidence that the issue is systemic rather than a one-off, and it is reasonable to stop monitoring and get it evaluated.
Either can, as long as whoever does it uses the same route and the same log format each time so the results are comparable. Consistency in how it is recorded matters more than who specifically holds the clipboard.
If your board wants a second set of eyes on what a recent storm left behind, Element Service Solutions offers a complimentary on-site inspection to walk the drainage system, document what is normal wear against what needs attention, and help you build the kind of dated record a board can act on with confidence.