Passes are the simplest way to give your riding school predictable revenue. The client pays once, rides for a month, you have money in the bank and stop worrying about every individual lesson.
That’s the theory. In practice most schools have three problems: wrong pricing, overcomplicated models and chaotic enforcement. Client says “I still have three rides left”, you say “two”, you settle on 2.5.
In this article I’ll go through 5 pass models that actually work in real riding schools. With pricing math, pros and cons, and how to enforce them without arguments.
Why passes at all, instead of single payments
Two arguments — one on the business side, one on the client side.
For the school:
- Cash flow — money in the bank on day one, not after every ride
- Lower churn — clients with passes cancel less (they want to use what they bought)
- Fewer operations — one payment instead of ten, less bookkeeping
- Easier planning — you know how many rides are “promised” this week
For the client:
- Lower per-ride price (typically 5-15% cheaper than single)
- Booking priority — pass holders get first dibs
- Easier planning for parents of children
A pass is a win-win contract — but only when priced correctly. A poorly priced pass = loss for you, or too high a price for the client. I’ll show you how to calculate it.
Model 1: Entry pass (4 or 8 rides, 30-day expiry)
The classic — 70% of European schools use this.
How it works:
- Client buys 4 or 8 rides
- Validity: 30 days from purchase
- Unused rides expire
- Extension possible for a fee (usually +20%)
Typical pricing (mid-sized European city, 2026):
| Item | Price |
|---|---|
| Single ride | €30 |
| 4-ride pass | €110 (€27.50 / ride — 8% off) |
| 8-ride pass | €210 (€26.25 / ride — 12% off) |
Pros:
- Simple — client gets it immediately
- Safe for you (30-day expiry = no frozen cash)
- Fits regular clients (once a week)
Cons:
- Doesn’t fit irregular clients (once a week in summer, none in winter)
- Client with 1 ride left “at end of month” feels stressed
- Without automation it’s easy to lose track
Best for: schools introducing passes, schools with regular client base.
Model 2: “Open” pass (12 rides, 90-day expiry)
A more flexible variant. Client buys a bigger pack, but has more time to use it.
How it works:
- Client buys 12 rides
- Validity: 90 days
- Great for irregular clients
Pricing:
| Item | Price |
|---|---|
| Single ride | €30 |
| 12/90 pass | €300 (€25 / ride — 17% off) |
Pros:
- Fits irregular clients (vacations, exam season)
- Bigger cash drop once per quarter
- Client feels relaxed, less use-it-or-lose-it pressure
Cons:
- Lower margin per ride (bigger discount)
- Cash flow rarer (once / 3 mo instead of monthly)
- Higher risk client churns with unused balance
Best for: schools with adult clients (irregular schedules), premium schools (lower per-ride as an attraction).
Model 3: Family pass (parent + child)
The most undervalued model in our market. Most schools don’t even offer it.
How it works:
- Pass is for 2 people (typically parent + child)
- Either person can use any number of rides from the pool
- 8 or 12 rides total, 30-60 day validity
Pricing:
| Item | Price |
|---|---|
| Family 8/30 | €220 (€27.50 / ride) |
| Family 12/60 | €315 (€26.25 / ride) |
Pros:
- Cross-sell — the parent dropping off the child starts riding too
- Lower CAC — one customer = two riders
- Higher LTV (parents stay longer because the child stays)
Cons:
- Needs a good system (who rode, who has rides left)
- Harder to enforce cancellation policy (whose account got debited)
Best for: schools with a strong family base (60%+ kids).
Tip: In Hovera the family pass has a single shared balance and any member can use it. The system tracks history — who, when, on which horse. See how it works →
Model 4: Monthly subscription (recurring)
The most modern model. Works like Netflix for horse riding.
How it works:
- Client pays a fixed monthly amount (auto-renewing card)
- Each month they get X rides to use
- Unused rides expire (like an unwatched Netflix episode)
- Cancellable any time at the end of the period
Pricing:
| Plan | Rides / mo | Price / mo | Per ride |
|---|---|---|---|
| Light | 4 | €105 | €26 |
| Standard | 8 | €200 | €25 |
| Pro | 12 | €285 | €24 |
Pros:
- Predictable revenue — client pays day 1 of every month, automatically
- Low churn (auto-renew = inertia)
- Great SaaS-style metrics: MRR, LTV, churn rate
- Client doesn’t think about the decision every month
Cons:
- Needs a system with auto-billing (Stripe, SEPA recurring)
- Some markets (esp. Eastern Europe) still less used to subscription for offline services
- Card-decline churn (1-2% monthly)
Best for: schools with 100+ clients, ready for modern tooling.
Trend: Subscription is still niche in PL/CEE riding (~5% of schools), but standard in UK and US. We expect rapid growth in CEE in 2026-2027.
Model 5: Hybrid pass (subscription + reserve pack)
A combination that boosts retention and gives clients flexibility.
How it works:
- Monthly subscription of 4 rides
- Plus extra rides from a one-off pack (bought seasonally, e.g. 6 rides for summer)
- Subscription rides expire monthly, reserve pack rides don’t
Pros:
- Client has “insurance” against vacations / illness
- Higher flexibility = higher retention
- Higher average customer value (subscription + occasional pack)
Cons:
- Complex model — client must understand the logic
- Hard to calculate (which pool deducts first?)
- Needs a system that can handle two pools
Best for: premium schools with loyal base, sport / advanced segment.
How to price a pass — the formula that works
Most common mistake: copying the competitor’s price list without calculating your own costs. Second most common: a 30% discount without checking if it still pays.
Break-even formula:
Cost per ride = (Horse upkeep / mo) / (Rides per horse / mo) +
(Instructor rate / hr) +
(Stable operating cost / hr)
Margin = Ride price - Cost per rideExample:
- Horse: €350/mo upkeep, does 20 rides/mo → €17.50/ride
- Instructor: €15/hr (at 60% of ride revenue)
- Operations (rent, electricity, bedding, insurance): €6/hr
Total cost per ride: €38.50
Single ride €30 = LOSS of €8.50 per ride!
That sounds absurd, but many schools operate this way without knowing. They generate revenue but don’t make a profit. Passes only multiply this if priced for revenue instead of margin.
Realistic pricing for the example above: single €50, 8-ride pass €360 (€45/ride — 10% off). That’s the minimum.
If the market won’t accept €50 — you have a structural problem. Cut costs or grow volume, but don’t sell below cost.
Cancellation policy in passes — what must be in there
Without it the pass system collapses. Client buys 8 rides, cancels 3 on the last day, asks for an extension. Repeats every month.
Minimum that must be in the pass terms:
- Validity period — e.g. “30 days from purchase, unused rides expire”
- Cancellation policy — e.g. “min. 24h before — slot returns to pool, less than 24h — slot lost”
- No-show policy — e.g. “no-show without cancellation = full ride registered”
- Extension option — yes/no, what fee (e.g. “+20% original price for 14-day extension”)
- Transferability — can the pass move to another person
- Refund of unused rides — yes/no (recommendation: no refund, but negotiable for exceptional cases)
- What at termination — what happens with unused rides if client leaves
Sample paragraph for terms:
“The pass is valid for 30 days from purchase. Cancellation must occur no later than 24 hours before the ride; otherwise the ride counts as completed. Unused rides are not refunded in cash. The pass is non-transferable.”
Client signs at purchase (online checkbox + IP/timestamp is enough in most EU jurisdictions). If they didn’t sign — you have a problem in disputes.
Enforcing passes — how not to argue with clients
Three rules:
1. The system shows the balance always, for both sides
Client logged into the app sees: “3 rides left, valid until 15 May”. You see the same. End of “but I had 4”.
2. Auto-decrement after a ride (and auto-revert on cancellation)
After every booked ride the pass ticks down by 1. If the client cancels per policy (24h+) — it returns. Less than 24h — it’s lost. All automatic.
3. Email/SMS at end-of-pass
“You have 1 ride left, valid until 15 May. Use it or buy a new pass with 5% off until end of week.”
This is both good service (client doesn’t “lose” the ride) and sales (push for renewal).
Which model: which pass for my school
The decision depends on your client base:
- Mostly regular (1-2x per week) → Model 1 or 2
- Lots of families → Model 1 + Model 3 as option
- Loyal base, 100+ clients → Model 4 (subscription)
- Premium, sport, individual plans → Model 5 (hybrid)
If you’re starting and have no data — start with Model 1. After 6 months analyze client behavior and add more options.
What you need to make it work without spreadsheets
Passes in Excel work up to ~30 clients. Above that, chaos starts:
- You don’t remember who bought when
- Client asks “how many rides left” → you search one sheet, check history in another
- Cancellation 23h before → you must manually return the ride
- Different policies for different clients (“but I always had 12h, not 24h”)
A system (like Hovera) has all this built in:
- Passes and packs with multiple models (4/30, 8/30, 12/60, family, subscription)
- Auto-decrement after a ride, auto-revert on in-policy cancellation
- Cancellation policy enforced automatically
- Client sees their balance in the app 24/7
- Email/SMS at purchase, cancel, end of pass
- Pass sales reports monthly / quarterly
- Invoicing integration — invoice issues automatically after purchase
Or see how passes work: Passes in Hovera →