Most small campgrounds have a two-night weekend minimum because the park down the road has one. It got copied from a rules sheet years ago, it feels responsible, and nobody has looked at it since.
The rule exists for a good reason. But applied park-wide, year-round, it quietly turns away money — and with booking windows getting shorter, it turns away more of it every season. Here's how to figure out where your minimum is earning its keep and where it's just a locked door.
Why the two-night minimum exists
The villain is the orphan night.
A guest books Saturday only. Now your Friday night on that site is stranded — almost nobody books a standalone Friday at a weekend park, because the people who want Friday want Saturday too, and your one-nighter just took it. One $60 booking killed a $120 weekend.
There's also turnover. A one-night stay costs you the same as a four-night stay in check-in effort, site cleanup, and the inevitable question about the WiFi password. Short stays are your most expensive nights to service per dollar earned.
So the two-night minimum isn't superstition. On the right nights, it's the correct call.
The orphan-night math
Run the numbers for your own park, but here's the shape of it. Say a site goes for $60 a night, and on a July weekend you reliably sell both Friday and Saturday.
- Accept a Saturday-only booking: you earn $60 and likely eat the Friday. Net for the weekend: $60.
- Hold out for a two-night guest: you earn $120.
If you have 20 sites and 15 peak weekends a year, letting one-nighters chew up even a handful of those weekends adds up to real money. That's the case for the minimum, and in peak season it's a strong one.
Now flip the calendar to late September. Same site, same rule — but this Saturday, half your park is going to sit empty no matter what. A one-night guest asks to book. The two-night minimum says no. You just paid $60 to enforce a rule that was protecting nothing.
When the minimum makes you money
- Peak weekends you actually fill. If Friday and Saturday both sell most weeks in July, the minimum is protecting real revenue. Keep it.
- Holiday weekends. A three-night minimum on Memorial Day, July 4th, and Labor Day is standard, and guests expect it. This is the easiest yes in pricing.
- Event weekends. Fair in town, race weekend, leaf season peak — anywhere demand reliably outruns supply, minimums let you sell the weekend as a unit.
When the minimum costs you
- Shoulder season. If the night next door was going to be empty anyway, there's no orphan to protect. A one-night booking on an empty September Saturday is pure found money.
- Midweek. A two-night rule on a Tuesday is solving a problem you don't have. If anything, midweek needs the opposite — see the empty Tuesday problem for what actually fills those nights.
- Inside the booking window. It's Thursday, this weekend's Friday and Saturday are still open, and someone wants just Saturday. The two-night guest you were holding out for isn't coming — if they were, they'd have booked by now. Take the one-nighter.
- Gap nights. Friday is booked, Sunday is booked, and one Saturday sits stranded between them. A minimum-stay rule that blocks a one-night booking on that gap is protecting nothing at all.
A simple framework
Set minimums by season and date, not park-wide. Three tiers cover almost every small park:
- Holiday weekends: 3 nights
- Peak-season weekends: 2 nights
- Everything else: 1 night
This pairs naturally with seasonal rates — if you've already built a seasonal pricing calendar, your minimum-stay tiers should follow the same lines.
Release the rule late. Pick a number — say, 7 days out. Inside that window, drop the minimum for any weekend that hasn't filled. Every night you rescue this way was headed for zero.
Fill the gaps. Watch for stranded single nights between bookings and let one-nighters have them. Guests hunting for a last-minute night are doing you a favor; don't make them call to beg for an exception.
Check the rule once a year. Count the peak weekends where both nights actually sold. If your "peak" minimum is guarding weekends that only fill half the time, the tier is drawn too wide.
The honest trade-off
One-night stays are more work per dollar. More check-ins, more turnovers, more chances for a late arrival on a night you'd rather close the office early. If a site is expensive to turn over — a rental cabin you clean yourself, say — a one-nighter on a dead night might genuinely not be worth it to you. That's a legitimate call. Make it deliberately, per site type, not by accident with a blanket rule.
The other cost is complexity. Three tiers plus a release window plus gap-filling is easy to describe and miserable to enforce by hand. On paper or a spreadsheet, you become the enforcement — every booking request gets checked against the calendar and the rules in your head, and the first time a helper takes a Saturday-only booking on a July weekend, you're back to orphan nights. This is a rules-engine job: the booking page should enforce the minimum on the dates that have one and quietly get out of the way on the dates that don't. That's how it works in Bunkpost — you set rates and stay rules once, and the calendar applies them (the rates, taxes, and policies chapter shows the setup).
The takeaway
A minimum stay is a peak-season tool, not a park policy. Keep it where both nights reliably sell, drop it where they don't, and release it when the window closes — the goal is to protect full weekends, not to turn away guests on nights that were going to be empty anyway.
If your current setup can't tell July from September, that's a software problem, not a you problem. Bunkpost is free for the park — no monthly fee, no percentage cut, just a flat $3 booking fee the guest pays at checkout — and most owners have rates and stay rules configured in an afternoon.