Park district websites, wired into RecTrac.
Your registration system is the system of record, and your website is where patrons meet it. When those two are not connected, staff enter every program twice and the site drifts out of date between seasons. We build park district websites that pull from Vermont Systems RecTrac and WebTrac directly, meet WCAG 2.1 AA, and hand day-to-day content back to your staff. We have done exactly this for one of the larger districts in Illinois.
Illustrative screens in the style of the build
Sound familiar?
Everything gets entered twice
A program changes in RecTrac and someone has to remember to change it on the website. Miss one and a patron shows up for a class that moved.
Patrons call instead of registering
The information they need is on the site but the thing they came to do is not, so the front desk fields calls that a working registration flow would have absorbed.
The site goes stale between seasons
Staff cannot change much without help, so hours, closures and seasonal programs lag reality until someone has time to file a request.
The accessibility deadline is real
The DOJ's ADA Title II rule sets WCAG 2.1 AA as the standard for public entities. Districts serving 50,000 or more have until April 26, 2027, and smaller districts until April 26, 2028. It applies to PDFs and forms, not just pages.
What we build for park districts
RecTrac and WebTrac integration
Programs, schedules, availability and registration pulled straight from the API, so the website reflects the system of record without anyone retyping it.
Registration and reservations patrons finish
Program signup, facility and shelter reservations, and household accounts, in a flow built for a phone rather than a desktop from 2014.
Alerts, closures and the seasonal guide
Banner alerts for a pool closure or a weather cancellation, an events calendar with real filtering, and the program guide where patrons look for it.
Content your staff actually own
Hours, notices, events, board documents and staff pages, all editable by the people who hold that information, with training included.
Already in your RFP
These are the requirements park districts put in their website RFPs. We have delivered every one of them.
- Vermont Systems RecTrac / WebTrac API integrationBuilt and running for an Illinois district.
- WCAG 2.1 AA accessibility complianceBuilt to the standard, verified before launch.
- CMS training for district staffIncluded, with documentation your team keeps.
- Migration of existing content and documentsPlanned as part of the build, not bolted on after.
- Hosting, DNS and performance optimizationHosted on Vercel, tuned before we hand it over.
- Ongoing monitoring and maintenance planA care plan with defined response times.
- Security updates and CMS patchesIncluded every month, not billed as incidents.
- Calendar, banner alerts, forms and searchStandard in every district site we build.
Proof from your world
Two promises the software industry hates making
$
One monthly fee, starting at launch
Design, development, hosting, and support in one number you can budget like rent. No hourly meters, no change-order invoices, and no per-seat fees that grow with your team. Billing does not begin until version 1.0 is live and your team is using it.
See the plans →{}
You own the code. All of it.
The repository, the documentation, and the infrastructure are in your name from day one. If you ever leave us, you take everything and any developer can pick it up. No ransom, no rebuild, no being trapped in someone else's platform.
How we work →Questions we hear from park districts
Have you actually integrated with RecTrac, or is this a plan?
We have done it. We built a full revamp for one of the larger park districts in Illinois with a deep RecTrac integration, so programs and registration flow from the system of record instead of being copied by hand. We cannot name the district, but we can walk your team through the work in detail on a call.
We use WebTrac already. Do we have to leave it?
No. Plenty of districts keep RecTrac and WebTrac doing what they do well and simply stop letting WebTrac dictate what the public website looks like. We pull from the API so your staff keep working the way they already do, and patrons get a site that was designed rather than inherited.
Will the site meet WCAG 2.1 AA?
Yes, and we treat it as a requirement rather than an add-on. The DOJ's ADA Title II rule adopts WCAG 2.1 AA for public entities. Districts serving populations of 50,000 or more must comply by April 26, 2027, and smaller districts and special district governments by April 26, 2028. It covers PDFs, online forms and third-party tools you embed, which is the part most districts discover late.
Can you respond to our RFP?
Yes. We price websites as a build plus a monthly care plan, which is the structure most district RFPs ask for: a project figure you can bid against a capital budget, and a support line you can renew. We can also quote a rate for work beyond the approved scope, which RFPs usually require.
What happens after launch?
You pick a care plan. Every one covers hosting, monitoring, security patching and backups; the higher ones add build hours each month and maintenance of the integrations underneath, so a RecTrac change on their side does not become your emergency.
Tell us what's slowing your business down.
In a free 30-minute call we map what the platform needs to do, tell you which tier it lands in, and give you a monthly number. No proposal theater, no pressure.
One monthly fee · Built, hosted & improving · You own the code