What we got wrong this season: a candid editor's note

Why this post exists

When we audited 866 splash pads between November 2025 and July 2026, we publicly committed to telling the truth about what we did not know. Saying that and doing it are two different things, and the test is not the audit announcement. The test is the post that comes after a season, where we are honest about what we got wrong.

This is that post.

We got things wrong this season. Some of them were small. A few were significant. All of them are correctable, and we are running corrections. This editor's note covers the ones we know about, with what we are doing differently in 2027.

If you only read one of our posts, this is the one we would pick. The audit data is useful. The honesty about its limits is what makes the data trustworthy.

Mistake 1: we propagated unverified accessibility claims for too long

This is the biggest one.

When we launched, our accessibility flags came primarily from official city pages. If a city said a pad was "ADA accessible," we trusted it. We added a verification layer in early 2026, but for the first six months of the year, hundreds of pads in our directory carried accessibility flags we had not independently confirmed.

The audit eventually revealed that 32 percent of "accessible" pads have serious access friction (gravel paths, steep ramps, missing curb cuts to the deck, transfer challenges) and 5 percent are functionally inaccessible despite the official claim. That means a meaningful fraction of families in our user base were getting bad information for the first half of 2026.

What we are doing differently:

• We have downgraded all unverified accessibility flags to "claimed (unverified)" until we can confirm them
• We added the three-tier system (ADA-baseline, verified-accessible, accessible-first) across the directory
• We prioritized accessibility verification for pads in our top 20 percent by visit volume, completed by August 2026
• We will not call a pad accessible-first without a confirmed wheelchair-user visit or trusted-source attestation

What we apologize for: the families who drove to "accessible" pads on our recommendation in early 2026 and found inaccessible reality on arrival. We owe you better, and we are building it.

Mistake 2: we underestimated how often pads close mid-season

We knew pads close. We did not appreciate how often, or how many of those closures happen mid-season for reasons that are visible in maintenance logs but invisible to families.

In our 2025 launch year, we treated opening and closing dates as the primary status fields. In reality, summer 2026 saw a significant number of multi-day or multi-week closures during peak season at popular pads, driven by mechanical failures, water-quality incidents, and storm damage.

Our closure data lagged reality by an average of 3 to 5 days for the most-visited pads. That is too long. Families plan around our information, and a pad listed as open is presumed open.

What we are doing differently:

• Quarterly automated calls to parks departments for the top 20 percent of pads by visit volume
• A community-submission flow for closure reports, with verification workflow
• A "recent status check" timestamp on every pad page so users know how fresh the information is
• A short-fuse alert system for pads that have closed within the last 72 hours

This will not be perfect. But it will close the gap from days to hours for the pads where it matters most.

Mistake 3: we overrated three pads we should not have

This is the one most directories will never write. We had three pads in our top-rated list that did not deserve to be there. Two had quietly degraded since their initial inclusion (worn surfacing, reduced shade, missing features), and one we had simply rated too generously based on a single high-quality summer visit before maintenance issues developed.

We are not going to name them publicly. They have been quietly downgraded with corrected information, and we have reached out directly to each parks department.

What we are doing differently:

• Top-rated pads are now re-verified annually, not once and forever
• A second-source confirmation requirement for any pad to enter the top-rated tier
• A degradation-watch flag triggered by user reports or audit signals
• An explicit tiering policy posted publicly

A directory that never demotes a pad is not really evaluating pads. It is just listing them.

Mistake 4: we ignored a mid-sized city for nine months

We had a coverage gap. A city of about 180,000 people in the Midwest with five active splash pads barely showed up in our directory until July 2026. The reason was unglamorous: our seed data missed it, no community submissions surfaced it, and we did not run a systematic check for coverage gaps.

By the time we noticed, families in that city had spent most of a season without a useful directory entry for their region.

What we are doing differently:

• Quarterly coverage audits against US Census data for cities of 100,000+
• A community-submission pathway specifically for missing cities, with priority review
• A "we know we are missing" page where users can report gaps
• An explicit goal of every US city of 50,000+ having at least one verified pad listed by end of 2027

Coverage gaps will exist. The mistake was not having a system to find them.

Mistake 5: we let our seasonal content lag the season

We published our Memorial Day opening guide on May 18. That is too late. Most families had already done their planning by then. Our Labor Day closing guide hit September 1, also late. Useful content published after the decision window has been made is content that should have been published earlier.

What we are doing differently:

• Seasonal content is now scheduled six weeks ahead of the relevant decision window
• The 2027 Memorial Day guide will publish in early April 2027
• The 2027 Labor Day guide will publish in mid-July 2027
• Birthday-booking content publishes in February, ahead of the March reservation rush

Editorial discipline is unglamorous, but families plan ahead and we have to publish ahead of them.

Mistake 6: we underweighted shade in our scoring

Our initial scoring model treated shade as one of many factors. The audit and ongoing user feedback made it clear that shade is one of two or three factors that families weight most heavily, especially in heat-state regions. Treating it as average-weighted understated its real importance.

What we are doing differently:

• Shade is now a primary weighted factor, not a secondary one
• We added explicit shade-source breakdowns (trees, sails, pavilion, none) to every listing
• A "no shade" warning is now prominent on listings where shade is absent
• Heat-state pads with substantial shade get an additional badge

This was a quiet error, but it affected ranking in a way that matters more than we initially modeled.

What we got right (briefly)

This is not a self-flagellation post. We got most of what we set out to do done. The audit ran. The corrections are running. The accessibility framework, however imperfect at launch, is now real. Coverage is better than it was six months ago. The tone of our content is honest and useful, with a few exceptions (the seasonal lag mistake above).

But naming what we got right is not the point of this post. The point is naming what we got wrong, because that is the test of whether to trust the rest.

What you should do with this post

Three things.

If you used our directory in early 2026 and felt that something was off, you were probably right. Use the corrected information now and forgive us the lag.

If you are deciding whether to trust us going forward, this post is the test. We will run a similar editor's note in October 2027. If we have gotten visibly better, the case for trust grows. If we have not, push back and tell us.

And if you spot something we missed in this list, email us. We are still finding mistakes. We will keep finding them. The corrections happen because users tell us.

That is the contract. Thanks for reading.