Splash pad Q&A: editorial

We try to confirm every listing against a primary source before publishing or substantially updating it. That usually means a city, county, school, park district, HOA, or operator page, plus supporting signals like maps, photos, or current seasonal notices when available.

SplashPadHub is edited by humans, not open wiki contributors. The site is maintained by an editorial workflow that reviews source material, updates structured records, and publishes revisions deliberately. We may use tools in research or drafting, but publication decisions and factual responsibility stay human-owned.

Usually because we have not verified them yet, not because we think they are unimportant. Missing pads tend to be very new, very local, poorly documented, private, temporarily closed, or inconsistently described online in ways that make confident publication harder.

Send the most verifiable version of the lead, not just the name. A good suggestion includes the pad name, city, state, exact location if known, and a source URL or photo that shows the feature really exists and is open to the public.

Primarily public records and operator-controlled sources. That includes city and county parks pages, school and campus sites, park district PDFs, rec-center schedules, official maps, meeting packets, local news, and carefully reviewed user-submitted corrections or leads.

There is no single universal refresh day. Listings are updated when we confirm a meaningful change, when seasonal operations shift, or during scheduled editorial passes. Higher-risk fields like hours, fees, and temporary closures get more attention than static facts like a park's general location.

We prefer current operator signals over assumptions from weather or latitude. Seasonal status is verified through posted schedules, city notices, rec-center pages, social updates, and direct operator language when available. If the status is unclear, we would rather label it typical than claim certainty.

We avoid turning identifiable children into the core of the directory. The preference is wide, contextual imagery or operator-provided material that does not expose random kids for editorial convenience. We are stricter about minors because location, clothing, and water-play settings raise obvious privacy concerns.

We review complaints as editorial claims, not as automatic takedown commands. Specific, sourced corrections move fastest. Vague objections like 'this feels wrong' slow things down because we still need evidence before changing a public listing that people may already rely on.

They are built from the directory's structured data, public records, and manually written analysis. We do not call something 'research' merely because a model summarized a spreadsheet. Report claims are chosen, framed, and edited by humans with visible sourcing logic.

Because those fields change often and many operators publish them badly. If we cannot confirm current hours or fees from a credible source, we would rather mark the field unverified than pretend last summer's screenshot or a random review still reflects reality.

No. Operators cannot buy their way into better rankings, category spots, or editorial language. That line matters because a directory about family recreation becomes less useful the moment readers have to wonder whether a highlighted pad is there because it paid for visibility.

Access rules decide most of it. If a splash pad is clearly public or bookable by the general public, it is a stronger candidate. If it is only for residents, hotel guests, or members, inclusion depends on whether the directory surface is explicitly documenting restricted-access options.

A verified listing is one where the core claim has been confirmed with sufficiently reliable evidence. At minimum, that means confidence the pad exists at the stated place and is described in the right category. Verification is stronger than rumor, weaker than omniscience.

Yes, in the practical sense that operators can send corrections, details, or missing context directly. Claiming does not mean taking over the page as branded self-service marketing. Editorial control stays with the site even when the operator is helping improve accuracy.

Carefully, and usually field by field. Accessibility claims come from operator descriptions, imagery, maps, documented amenities, and sometimes direct correction from people who know the site. If we cannot support a claim like wheelchair-friendly entry or adult changing space, we avoid guessing.

Duplicates get merged, redirected, or removed once we confirm the identity conflict. They usually happen because a pad has multiple names, sits inside a larger park with its own label, or was documented from two different source trails that did not initially look identical.

Only to the extent needed to review, respond to, and document the submission. A useful directory needs some audit trail for corrections, but it does not need to hoard personal detail. The principle is operational necessity, not collecting data just because forms make it easy.

Tools may assist parts of the workflow, but factual publication is not delegated blindly to a model. Any AI-assisted drafting should still be checked, edited, and owned by a human. If a directory stops doing that, it becomes a faster way to spread polished mistakes.

Generally yes, subject to the site's stated licensing and attribution terms. The practical expectation is simple: cite clearly, link back when appropriate, and do not remove caveats that mattered in the original context. Reuse is most valuable when the uncertainty travels with the numbers.