Add a storm observation
Keep this practical. Do not enter addresses, parcel numbers or sensitive personal information.
Nothing is uploaded by this tool.
Your local storm history
What repeated observations can reveal
Pooling only in large stormsCapacity, inlet area or temporary storage may deserve a different check than a drain that fails in every rain.
Pooling after several wet daysSoil saturation, groundwater or slow infiltration can matter even if the same location drains quickly after a dry period.
No outlet flow when the yard backs upTrace the downstream route and accessible cleanouts before assuming the inlet itself is too small.
Strong outlet flow but puddle remainsThe collection point may miss the true low spot or broad surface flow may bypass it.
Water repeatedly reaches the buildingTreat that as a higher-consequence condition; check roof discharge and near-building grade promptly.
Use the log before and after a change
If you extend a downspout, clean an outlet or regrade a small area, keep the next few storm observations under similar fields. The goal is not a scientific experiment; it is a consistent record that reduces reliance on memory.
For a system that already exists, pair this log with the troubleshooting guide. For a new project, carry the repeated observations into the property planner and field checklist.
Privacy and retention
Entries are stored in browser local storage under wrivel-storm-log. They remain on this browser until you clear the log or clear site data. Copy summary copies plain text to your clipboard; Wrivel does not create an account or server-side storm-history record for this tool.
Planning scope: a storm log helps document repeatable behavior. It does not establish a design storm, diagnose groundwater, prove legal discharge rights or replace professional evaluation for building water, sewer backup, erosion, slope instability or other high-consequence conditions.