May is when Western PA yards show you where water actually goes after a few heavy rains, not where you hoped it would go on paper. This guide is a handoff sequence for homeowners who want clear language before they talk with contractors, neighbors, or municipal programs about grading, downspouts, and the low spots that always win the puddle contest.
Use it next to May first heavy rains and backyard drainage for photo habits, and outdoor drainage maintenance when you need vocabulary that matches how crews describe sheet flow and outlet clogging. If you are also preparing to host, thread host week notes from May host week grill and deck safety so grading work does not fight the path guests will use with food.
Name the real low spots with daylight and simple measures
Walk the property the morning after rain when grass still shows tracks. Mark repeat puddles with stakes or chalk that survives one photo set. Measure approximate length and width in feet so your notes read like a field log, not a vague “always wet back there” line that forces guesses on the phone.
Note how long a stripe stays soft forty eight hours after a modest rain. Clay in Allegheny County and flatter lots in Allison Park behave differently, yet repeat footprints in the same outline tell the same story: water is not leaving on the path you think is active.
Trace every downspout to its exit truth
Follow each leader to daylight, dry well, or storm tie in if you know where it goes. Note splash blocks that migrated, elbows that leak at joints, and leaders that dump toward foundations, walks, or the neighbor fence. Photograph problem joints from two angles so winter damage and summer growth are both visible in the same file name pattern you keep all year.
When a leader concentrates roof volume in one corner, a technically correct swale can still fail. Write roof water paths in their own short paragraph before you describe yard slope. That split saves time when you send the packet through contact.
Roof volume and yard slope are different stories
Roof runoff can overwhelm a lawn crown if leaders aim at the same ten feet every storm. Yard slope behavior belongs in a second paragraph: where sheet flow starts, where it crosses walks, and where it stops. When those stories live separately, contractors spend less time untangling mixed symptoms and more time proposing fixes that match both loads.
Compare your field log with April clay soil lawn recovery when thin turf follows the wet line. Turf culture from best practices for lawn care in Pittsburgh helps after water paths are honest, not before.
Hardscape edges that act like dams
Inspect patios and walkways for edges that block sheet flow toward the outlet you think is active. Note joints that washed out and lips that trip guests because those often sit in the same stripe as recurring puddles. If outdoor living traffic increased since last year, say so. Wear patterns change where water can infiltrate versus where it will sheet across stone.
Cross check April hardscape notes from late April patio and walkway stability so you are not describing a drainage bowl that is partly a settled tread problem. May outdoor living prep from May outdoor living prep checklist helps you sequence furniture moves after grade conversations, not before.
Plant beds, mulch depth, and irrigation overlap
Deep mulch against siding or sill lines can bridge moisture where you do not want it. List beds that stay saturated while uphill lawn looks fine. If sprinklers run before rain events, capture your controller schedule in the same packet so grading proposals account for artificial water, not only storms.
Spring irrigation start up and irrigation booking help when heads need technician level adjustments. Low heads sitting in puddles can keep clay surface wet while the controller still thinks the zone is fine. Fix programming and aim in the same season you fix grade when both symptoms appear together.
Build a handoff packet partners can reuse
Combine photos, the two short roof and yard narratives, and a simple sketch with north marked. Add event dates that matter for access, such as host weekends or fence projects, so proposed work lands in realistic windows. Include lighting notes if walks stay dark after grading changes, using April outdoor lighting safety check habits for beam aim after soil or stone moves.
When you want Eichenlaub to align drainage conversation with broader landscape management or hardscape repair scope, send that packet through contact with the top three questions this walk surfaced. Good packets beat perfect sketches drawn from memory in August.
Neighbor lines, easements, and shared runoff
When sheet flow crosses a property line, mark the direction on your sketch with a light arrow. Photos from both sides of a fence after the same storm prevent summer arguments when everyone’s mulch floats the same afternoon. You are not assigning blame. You are documenting physics so any proposed swale or outlet respects real paths.
If municipal programs or HOA rules apply in your municipality, note them in the packet header so contractors do not propose work that cannot be permitted on your street. That small line saves weeks in East Region townships and older Bradford Woods lots where drainage history is long and layered.
What honest expectations sound like in May
Not every wet corner needs a major build. Sometimes aim, mulch depth, and a reset splash block solve the repeat stripe. Sometimes stone, swale, and outlet work belong in scope. Either way, May storms give you evidence summer will repeat. Read planning before the spring rush if you want design level changes in the same year as drainage fixes.
Browse articles when you want more context, and keep photographing after each heavy rain so you know what changed. Pittsburgh clay rewards patience, clear language, and notes that respect both roof volume and yard slope as separate stories.
File your packet where you will find it in September, when leaf load changes flow again. The same photos that convinced you to fix a leader in May will still explain why a stripe returned after the first October storm.