Where do you get your info?
Court Finder reads from the shared Forward Foundry venue platform. That data combines canonical venue records, source organization pages, Google Places details, and review-derived venue context where available.
About Court Finder
Built for tournament parents
Court Finder is part of the Forward Foundry venue platform. The goal is simple: help families understand a venue before arrival with faster maps, context, and venue-specific planning notes.
How we think about venue pages
Official venue pages are often incomplete for tournament families. We focus on the questions parents actually ask on the way to a gym.
That means surfacing likely entry issues, parking patterns, seating context, nearby essentials, and maps in one place.
When summaries appear, they should be read as planning context derived from source material, not as official venue policy.
FAQ
What do the summaries on each venue page mean?
Venue summaries are context layers, not official venue statements. They synthesize available source metadata and review patterns so parents can scan likely parking, entry, seating, and food issues faster.
How do I report an error?
Use the Tip Jar form on this page to capture the correction details now. The UI is ready, and the next backend step is connecting those validated submissions to a moderated inbox.
Can I save venues?
Yes. The current release supports saved venues on your device. The recommended next step is an email magic-link lookup so the same saved list can work across devices without a full password account.
How fresh is the data?
Venue pages are statically generated for SEO and revalidated on a short interval. Each detail page should also show source context and review freshness when that metadata exists.
Product direction
How feedback and saved venues should evolve
The right long-term flow is an email-required Tip Jar that stores venue-specific feedback in `ff-venues`, with moderation before anything becomes public.
For saved venues, I recommend the same identity model: email magic link lookup instead of a raw verified-email table. That keeps the experience lightweight while still letting families recover their list across devices.
Tip Jar
Parent feedback module
This release gets the structure right: email required, venue optional, and a clear topic bucket so a moderated feedback inbox can be connected next without redesigning the flow.
0 local tip entries