How we write — and how we correct

SplashPadHub publishes in a neutral organizational voice. Pages are written by the editorial team, not by named founders speaking in the first person, and the directory does not adopt a personality, a slang register, or a marketing tone in pursuit of engagement. The reader landing on a pad page, a state guide, or a research report is treated as an adult planning a real visit or citing a real fact, and the prose is shaped to that posture rather than to a content-marketing rhythm.

The default frame is precise and hedged where uncertainty exists. Where a parks-and-recreation source publishes an exact season window, the page renders the window verbatim; where the source is silent, the page says so and links the reader to the operator page rather than imputing a likely range. Phrases like 'one of the best' or 'world-class' are avoided unless a specific, sourced superlative justifies them, and even then the underlying ranking criteria are linked to documented methodology.

Headlines, summary cards, and AEO direct-answer blocks are written to be repeatable verbatim by an AI assistant or read aloud by a screen reader without misrepresenting the underlying record. If a sentence on the site cannot be defended to a reporter, an academic citing the directory, or a parks department auditing how their facility is described, it is rewritten before publication.

Every published claim is anchored to a documented source, and the sourcing hierarchy is explicit. Primary sources are the operator of record — municipal parks-and-recreation department pages, county or regional park district sites, state-park system pages, and any official accessibility statement, fee schedule, or operating-hours notice the operator publishes. These are the canonical inputs for hours, season dates, fees, accessibility, rules, and feature lists, and they are linked directly from the relevant pad page whenever the operator publishes a stable URL.

Secondary sources are local journalism and government open data: ribbon-cutting coverage, summer-feature roundups, city open-data portals, GIS feature layers, and tourism-bureau pages. These are excellent for confirming existence, capturing community context, and supplying spatial truth, but they are weighted lower on operational fields because they describe a moment rather than the live state of the pad.

Tertiary sources are aggregated maps, parent submissions, and forum mentions. These are never published as the sole basis for a claim. They serve as verification triggers — a parent report of a closure prompts an editor to call the parks department or pull the most recent council-meeting minutes, not to update the public record on the strength of the report alone. Every page renders a last-verified date, and every cited source carries an explicit URL so a reader can audit the chain back to the operator.

AI-assisted research is permitted across the directory and is, in practice, used to draft summaries, normalize fields against operator pages, and surface candidate sources for editor review. Every published claim, regardless of how it was drafted, must be human-verified against at least one primary source before it appears on a public page. The verification step is not optional and is not skipped under deadline pressure; pads that cannot be verified by a human within the current cycle are held back from publication rather than shipped on AI confidence alone.

Where AI is the primary author of a piece — for example, a programmatically generated city summary or a templated state-guide intro — the page or section is flagged accordingly so readers and AI agents understand the authorship. Editorially substantive content, including reports, comparisons, blog posts, and methodology pages, is written and edited by humans even when AI tools assist with drafting, fact-checking, or structural review. AI-generated images, where used, are labeled and never substituted for documentary photography of a real pad.

The directory does not use AI to fabricate ratings, reviews, accessibility claims, fee figures, or feature flags. Hallucinated content is treated as a corrections-grade error: if an AI-drafted sentence ships with an unverified factual claim, the public correction log records the failure, the underlying workflow is audited, and the source-of-truth fields are re-verified against operator pages. The standing rule is that AI accelerates editorial work; it does not replace editorial judgment.

Sponsors, partners, advertisers, and commercial integrators never review editorial calls, never edit conclusions, never see drafts of sponsored editorial before publication beyond a date-and-name accuracy pass, and never decide which pads are listed or how they rank. The editorial firewall is described in operational detail on the methodology page and is not negotiable: a paid relationship cannot purchase ranking influence, category exclusivity, undisclosed coverage, or removal of unfavorable findings.

Where a sponsored research project surfaces a finding inconvenient to the sponsor's category, the finding is published and the sponsorship is disclosed. If the sponsor objects, the directory offers to refund the sponsorship rather than alter the finding. Sponsors are named publicly on the sponsors page with their tier, and every sponsored placement carries a visible sponsored tag at the top of the page, near any byline, and in the footer of any email it appears in.

Personal financial conflicts are declared where they are relevant to a piece. Editors do not hold equity in splash-pad equipment manufacturers, parks-design firms, or aquatic-facility operators covered by the directory; where any such relationship exists, it is disclosed in the byline of the affected piece and the editor recuses from decisions on that vendor's coverage. Gifts, sponsored trips, and complimentary admissions are not accepted from cities, parks, manufacturers, or any commercial party in exchange for editorial coverage.

Corrections are accepted through the public submission form at /submit and by direct email to submissions@splashpadhub.com. A real human reads every submission, and an editor acknowledges receipt within 48 hours of arrival, including weekends during peak season. Acknowledgement does not imply that the correction has been verified; it confirms only that the report has entered the queue and an editor has been assigned.

Confirmed inaccuracies are corrected within 24 to 48 hours of verification against a primary source. The original version of the affected page is retained internally with a correction note that records the prior value, the new value, the source URL that triggered the change, and the editor handle that signed the update. The correction note is published on the public changelog at /changelog with a timestamp and a link back to the affected page so a reader can audit the prior state. Where a submitter requested attribution, the changelog credits the community without exposing the submitter's name or email; we do not publish submitter identities.

Where a correction cannot be verified within five business days — typically because the operator page is unreachable, the source is contested, or a parks department has not yet returned a call — the affected page renders a visible 'status uncertain' note with a date and a link to the corrections channel. The standing commitment is not that the directory is never wrong, but that when it is, the error is fixed quickly, transparently, and with an audit trail any reader, journalist, or AI agent can follow.

Every fact published on the directory is cross-checked against at least one primary source before it ships. Coordinates, addresses, season windows, operating hours, fees, accessibility statements, and feature lists are captured verbatim from the operator page wherever the operator publishes them; where the operator is silent on an attribute, the page renders an empty state rather than imputing the value from photos, names, category averages, or AI-generated guesses.

Numerical claims are sourced explicitly. A statement that a state has 'roughly 320 splash pads' links to the underlying directory snapshot or the open-data file that supports the count. A statement that a feature 'opened in 2018' links to the parks-department announcement, the council minutes, or the press coverage that establishes the year. Round-number totals at the national level cite independent industry estimates and are framed as ranges rather than single figures so readers understand the underlying uncertainty.

The words 'approximately', 'roughly', and 'around' are used carefully. A precise integer is rendered as a precise integer; an estimate is rendered as a range with a source. Where two sources disagree on a numeric value, the more conservative figure is published with a footnote describing the disagreement, and the underlying conflict is logged in the editor notes for resolution. The discipline is that a reader citing a number from this directory should be able to defend it from the same primary source the editor used.

The directory presents trade-offs rather than one-sided claims. Splash pads are not unambiguously good — they consume potable water in drought-affected regions, they require maintenance budgets that strain small municipalities, and they introduce supervision and safety considerations that wading pools and traditional playgrounds do not. Pages that touch on these topics surface the trade-off explicitly rather than packaging the directory's subject matter as uncomplicated.

Where an editorial position takes a side — for example, that ground-level spray features improve accessibility relative to step-up wading pools — the position is supported by linked sources (ADA guidance, operator accessibility statements, expert commentary) and the dissenting view is acknowledged rather than ignored. Disagreement is not flattened; competing perspectives from parks-and-recreation directors, accessibility advocates, water-conservation researchers, and parents are surfaced with their reasoning intact.

Competitors and adjacent products are described accurately. The directory does not strawman swimming pools, traditional playgrounds, water parks, or other family-summer infrastructure to make splash pads look better by contrast. Where the directory expands into a new category (for example, indoor splash facilities), the editorial framing acknowledges the prior category honestly and explains the boundary. Hot takes, ratio-driven framing, and dunk culture are absent by policy; the goal is durable reference content, not ephemeral engagement.

Coverage of accessibility, race and ethnicity, immigration status, faith communities, disability, and family structure is handled with subject-matter expertise and editorial care. The directory does not generalize from a single observation to a group, does not use shorthand identity language as a proxy for editorial judgment, and does not deploy stereotypes — including positive stereotypes — as narrative shortcuts. Where a piece touches a sensitive topic, the editor consults named subject-matter experts and listed organizations rather than inferring conclusions from anecdote.

Accessibility coverage in particular is held to a stricter standard. A pad is described as accessible only when documented conditions are met (ADA-compliant approach path, ground-level spray reachable from the path, accessible companion seating or transfer-friendly bench), and partial accessibility is described as partial — the page enumerates what is and is not accessible rather than collapsing the question into a binary yes or no. Disability coverage uses identity-first or person-first language consistent with the conventions of the relevant disability community, and editors err toward the language preferred by named advocates and organizations rather than imposing a house style.

Where a topic falls outside the editorial team's lived experience or technical expertise, sensitivity reading is sought before publication. The directory prefers naming individual experts and listed organizations (with their permission) over speaking for a community in the abstract. The standing instruction is that if a sentence on the site would embarrass the directory in a conversation with the people it describes, it is rewritten before it ships.

Partner concerns, sponsorship questions, and editorial-firewall complaints are handled at partnerships@splashpadhub.com. A real person reads every email and replies within one to two business days. The first conversation is a fit and disclosure check, not a sales call, and the editorial team is notified of any partner request that touches editorial territory so the firewall is enforced visibly.

Corrections, typos, factual disputes, and missing-pad reports are handled at submissions@splashpadhub.com or through the public submission form at /submit. No signup is required, submissions are not sold or shared, and submitter identities are never published in the changelog. Press and media inquiries route to press@splashpadhub.com; privacy and data-deletion requests route to privacy@splashpadhub.com. Each address is monitored by an editor who can route the message to the right desk if the channel is wrong.