How two sister schools built a shared splash pad as a joint campus project in St. Paul, Minnesota
A composite case study of two paired public schools splitting capital, scheduling, and programming for a shared splash pad tied to exchange activities and summer learning.
Summary
This composite St. Paul case follows two adjacent district schools - a neighborhood elementary and a language-immersion magnet formally paired as sister schools - that jointly built a $980,000 splash pad on shared district land between their campuses. The project began as a practical response to overheated summer-school recess and evolved into a broader exchange program with joint field days, bilingual family nights, and shared stewardship by two principals, two PTAs, and one district facilities team. By splitting capital, scheduling, and programming rather than duplicating amenities on each campus, the schools created a more affordable and more social solution than either could have delivered alone.
Key metrics
Background: the schools were neighbors with parallel needs and a habit of solving them separately
Maple Grove Elementary and Riverview Language Academy in this composite St. Paul district sit on adjoining parcels divided by little more than a fence line, a service lane, and years of administrative habit. One is a neighborhood school with a large summer learning program. The other is a districtwide immersion magnet that attracts families citywide and runs exchange-themed cultural programming through the summer. Both serve many young children. Both faced rising heat on blacktop-heavy school grounds. Both had family groups asking for more joyful outdoor infrastructure that did not require the staffing and liability profile of a pool. Yet for years the district treated them as separate capital stories. Each school pursued its own playground grants, shade requests, and PTA wish lists, even when the physical realities on campus made collaboration the more rational path. The turning point came during a particularly hot summer-school season when both principals were shortening recess, moving activities indoors, and watching attendance dip during late-July heat waves. A district facilities planner asked an obvious question nobody had operationalized: why are we considering two smaller cooling interventions when the campuses already share a central service yard that could support one better amenity? Because the schools had been formally paired in district communications as sister schools for language exchange, arts showcases, and family engagement, a shared splash pad suddenly had both a logistical and a symbolic frame. It could solve heat and recess needs while also giving the sister-school relationship a daily, usable physical expression. What made the project compelling was not just the infrastructure. It was the chance to make two schools that often exchanged goodwill finally exchange space.
The joint funding model worked because it saved each school from chasing a weaker solo project
Neither campus could have built a robust splash pad alone without waiting years. The district had enough deferred-maintenance pressure that a single-school recreation request would likely have fallen below roofs, HVAC upgrades, and accessibility work. A joint model changed the math. The district committed $520,000 from capital funds by classifying the project as shared campus infrastructure that improved summer-school functionality and expanded ADA-compliant outdoor programming. The two PTAs then coordinated a unified family campaign rather than competing for separate donations, raising a combined $190,000 across both school communities. A local education foundation added $170,000 after positioning the splash pad as a summer-learning and attendance-support tool, not merely a playground add-on. The final $100,000 came from ward-level participatory budgeting and a small corporate match from a nearby employer that supports bilingual education. The political beauty of the arrangement was simple: each stakeholder could spend less while getting more. One central pad with shade, storage, and accessible routes was better than two token misting stations or hose-based improvisations. The funding model also forced early agreement on operations. District facilities would own the water system. The schools would share program scheduling through a written calendar compact. The PTAs would not receive reservation privileges in exchange for fundraising. That last point mattered. Once parent groups help pay, there is a temptation to let donor energy evolve into ownership claims. The district resisted that firmly. The amenity would belong to both campuses equally and, during designated community hours, to neighborhood families as well. In a shared-school project, governance clarity is what prevents generosity from becoming territoriality.
Design centered on shared visibility and flexible school-day use rather than on spectacle
The design team placed the pad in the former service-yard lawn between the two schools, opening clear sightlines from each campus and from the shared family entrance used during summer programs. That placement was operationally strategic. Neither school could claim the amenity physically, and supervisors from both sides could access it without crossing the other's academic core. The pad itself is modest but highly functional: about 2,700 square feet with ground sprays, interactive loops, a low mist arch, and a wide perimeter bench that doubles as class seating during exchange activities. There is no bucket and no themed sculpture. The schools wanted the site to feel energetic without turning transitions into chaos. Bilingual wayfinding, storage for towels and program bins, and adjacent shade pavilions for both wet and dry activities were more important than high-drama features. Because one campus serves more sensory-sensitive learners, the design includes a calmer edge with lower-pressure sprays and visual separation from the more active center. The surface and drainage details were also chosen for school use rather than public-park assumptions. Teachers needed to move groups through quickly, students needed places to line up, and maintenance staff needed easy startup and shutdown around class schedules. The final layout supports physical education, summer school, family literacy nights, and open neighborhood hours without feeling over-specialized for any one use. That versatility is what made the project financially sensible. The schools were not buying a luxury recess toy. They were building a shared outdoor classroom, cooling tool, and family gathering zone that could justify itself across many parts of the academic calendar.
The exchange idea became real through programming, not through the words sister schools alone
Many paired-school relationships remain symbolic: joint newsletters, a banner on event nights, and occasional assemblies. The splash pad changed that because it required the campuses to create shared routines. Summer school became the first test. Instead of scheduling recess separately around scarce shaded space, the schools now coordinate rotating splash blocks, with mixed-group activity days every Friday. Teachers use those days for paired reading buddies, language games, and collaborative art prompts under the shade structures after water play. The immersion school leads bilingual signage and vocabulary hunts on the plaza, while the neighborhood school contributes larger attendance from its district summer program, making the exchange reciprocal rather than one-way. During the first year, the site hosted thirty-four formal joint programming days, including family literacy nights where caregivers from both school communities moved between read-aloud circles, free-book tables, and open splash time. The principals also discovered a less visible benefit. Because students from the two schools now share positive physical space before and after events, the sister-school relationship feels less performative to families. Parents no longer hear about collaboration only at formal events; they see it in ordinary summer routines. That matters in districts where magnet and neighborhood programs can otherwise drift into soft competition over prestige and resources. The splash pad does not erase those structural dynamics, but it gives staff a concrete reason to coordinate and gives students a place where the partnership feels embodied. In education, shared infrastructure often does more for trust than shared slogans.
Operations required a written calendar compact because goodwill alone was not enough
Shared amenities can fail even when everyone likes them. The weak point is usually scheduling. Both schools wanted prime use windows, flexibility for special events, and a sense that their fundraising effort mattered. The district addressed that early by drafting a calendar compact approved by both principals and the facilities office before construction ended. The compact divides weekday school-year use by block, reserves summer mornings for program rotations, and sets community open hours in late afternoons and select weekends. It also defines how exceptions work: weather makeup days, field-day priority, community events, and maintenance closures. Just as important, the compact identifies one district administrator as the final resolver when conflicts arise. That sounds bureaucratic, but it saved the project. In year one, both schools requested the same June evening for culminating family events, and the compact allowed a fair resolution without spiraling into politics. Annual operating cost has settled near $49,000, covering water, electricity, chemistry, custodial support, and a seasonal aide who manages towels, supplies, and student transitions during summer blocks. Staff also learned that wet circulation into buildings needed stricter procedures than expected, especially for the immersion school whose library is closest to the shared entrance. Additional matting, cubbies, and line-management routines fixed that by midseason. The larger lesson was straightforward. The relationship between the schools was strong enough to inspire the project, but not strong enough to run it on vibes alone. Durable shared space needs rules that survive everyone's best intentions.
Year-one outcomes were strongest in attendance, family engagement, and the tone of interschool cooperation
The first-year numbers were good, but the relational outcomes may matter more. Combined summer-school participation rose 18 percent, which district staff attributed partly to improved parent confidence that children would have tolerable outdoor time during heat weeks. Absenteeism dipped modestly during the hottest stretch of July compared with the prior summer. Family events drew stronger turnout than expected because the splash pad made them easier to frame as outings rather than meetings. Parents who might skip an informational literacy night were more likely to attend a bilingual splash-and-books evening where children could move freely. Staff from both schools also reported softer but meaningful changes. Teachers knew each other's students better. Parent volunteers began organizing across campuses rather than through separate PTA silos. The principals found that problem-solving conversations carried less territorial charge once the campuses had a visible, successful joint asset to point to. There were tensions too. Some families from each school initially worried the other campus would overuse the amenity or receive better scheduling. Those concerns eased as the compact produced predictable routines and as both communities saw their own children benefiting. The district also opened limited neighborhood hours, which was important politically. A shared school pad built with public money can look exclusionary if it never serves the wider community. By allowing controlled public access outside school blocks, the project strengthened neighborhood goodwill without compromising campus operations. For a sub-million-dollar capital project, the pad generated an unusually broad set of educational and social returns.
The main risk was not technical failure. It was reversion to separate-school habits
Splash-pad mechanics were manageable. The harder long-term risk is institutional drift. Schools change principals. PTAs turn over. District priorities shift. Shared spaces can slowly become nobody's mission or, worse, one school's de facto territory. The St. Paul composite addressed this risk in several ways. The calendar compact renews automatically but is reviewed each spring in a public meeting with both school communities. Facilities reports usage and maintenance cost by the combined site, not by school, which reinforces the notion of a single shared asset. The education foundation requires a short annual narrative on how the sister-school partnership used the space, keeping programming visible alongside operations. Students also contribute to continuity. Each year both campuses repaint bilingual etiquette panels and create exchange-art banners for the shade structure, small rituals that help new families understand the shared identity of the yard. None of that is foolproof. If one school's enrollment changes drastically or a major facilities project displaces the calendar, friction will return. But the project at least acknowledges the real challenge. Shared school infrastructure is rarely undermined by a broken pipe first. It is undermined by administrative amnesia. The solution is to build governance rituals as intentionally as drainage lines. When the institutions keep remembering together, the splash pad continues functioning as more than a nice object between buildings.
Replicability is strongest where schools are physically adjacent and willing to share credit as well as cost
Districts across the country have schools with similar needs, but not all should copy this model. The case is strongest where two campuses are physically adjacent or already share boundary space, where at least one runs summer programming, and where both leadership teams can tolerate a genuine loss of unilateral control. The financial logic is compelling. One well-designed shared amenity often costs less and works better than two compromised solo projects. Yet the model collapses if the campuses insist on treating every scheduling decision as a zero-sum competition. That is why the sister-school framing matters. The relationship does not have to be international or ceremonial; it just has to carry enough institutional meaning that both communities can see the amenity as a joint win. Where that exists, a shared splash pad can do more than cool children off. It can give districts a practical way to reduce duplication, improve summer attendance, and make cross-campus collaboration feel concrete to families. The St. Paul composite ultimately suggests that joint school projects succeed when they are designed around ordinary use, not special-event symbolism. The pad is valuable because it solves a daily problem and, in doing so, makes cooperation routine. That is a stronger educational outcome than any banner proclaiming partnership could deliver on its own.
Voices from the project
“For years we talked about being sister schools. The splash pad was the first project that forced us to act like it every single week.”
“One strong shared asset beat two weaker wish-list projects, but only because the district put the calendar rules in writing.”
“Parents stopped asking which school owned the pad once they saw both communities using it well.”
Lessons learned
- Choose a shared school site only where adjacency and supervision lines make equal access physically believable.
- Use a joint capital stack to avoid two underpowered solo projects, but prevent fundraising from turning into usage entitlement.
- Write a calendar compact before opening because shared amenities fail first through scheduling ambiguity.
- Program the exchange visibly through mixed-group summer days, bilingual family events, and repeated cross-campus routines.
- Track relational outcomes such as family participation and interschool cooperation, not just splash attendance.
- Build continuity rituals so the partnership survives leadership turnover and does not revert to separate-school habits.
FAQ
Why build one splash pad for two schools instead of two smaller cooling areas?
A shared pad usually provides better feature quality, shade, accessibility, and operating efficiency at a lower total cost than two smaller standalone projects.
What is the biggest operating challenge in a shared school splash pad?
Scheduling. A written calendar compact with escalation rules is more important than most design details because conflict over prime use windows can destabilize the partnership quickly.
Can the community use a school-based splash pad?
Yes, if the district sets controlled public hours outside school blocks and designs supervision, restroom access, and security procedures accordingly.
Related reports & data
Pair this case study with our original-data reports for citation and benchmarking.