Campground Length-of-Stay Rules That Protect Weekends

Indiana State Parks already printed the weekend fence. On camp.IN.gov, a Friday night must include Thursday or Saturday. A Saturday night must include Friday or Sunday. Holiday weekends are three named nights, not a mood. Guests already hit that wall on a public calendar. Your 50-amp pull-through should not be easier to pick apart than a state park pad.

A campground length-of-stay rule must fence Friday and Saturday together in peak season, name the three holiday nights, and drop the minimum on ordinary dates when the night is about to go empty. A Friday-only booking is not extra revenue. It is a Saturday you cannot sell. Same numbers on the guest site, the OTA, and the phone. Cabins can be tighter. April Tuesdays should not be.

TL;DR

• Indiana DNR attaches Friday to Thursday or Saturday, Saturday to Friday or Sunday, then names 2026 holiday blocks (Memorial Day May 22–24, Independence Day July 2–4, Labor Day September 4–6).

• North Carolina State Parks use a 2-night holiday minimum and lift it inside 7 days so last-minute holes still sell.

• Washington State Parks keep roofed units on a 2-night min in summer and on weekends year-round. Houses are 2 nights all year.

• One private example: Louisville South KOA wants 3 nights on Memorial Day, July 4, and Labor Day, and 2 nights on events.

• Keeprstay is vendor copy. The mechanism is still right: Saturday-only can kill the weekend.

• Related: fill Tuesday without cutting Friday. That post is occupancy. This one is the fence.

What is a length-of-stay rule at a campground?

A length-of-stay rule is a fence on which nights can be sold alone. It is not a rate. It is not a deposit. It says whether a 50-amp pull-through can be taken for Friday only, or whether Friday has to bring Saturday with it.

Rates tell the guest what a night costs. Deposits tell them what happens if they cancel. Length of stay tells the calendar which combinations exist. Mix the three and you get a poster nobody can enforce.

At a 40 to 80 site park the scarce object is usually Friday night plus Saturday night on a 50-amp or pull-through. Tent loops and weekday hookups are a different product. Write them as different rows, not as one “2-night minimum forever” line in the office window.

If your PMS cannot reject a below-min click, you do not have a stay rule. You have a preference you argue about at the gate.

Why does a Friday-only booking wreck the weekend?

Because Saturday is the scarce night. Sell Friday alone and Saturday becomes an orphan the next guest cannot attach. You took one night of peak demand and spent the second.

Keeprstay spells the same trap as Saturday-only. Treat that as vendor teaching, not a census. The grid math does not need their occupancy table.

Worksheet, not a survey. Insider Perks 2026 RV median is $62. One Saturday-only at $62 is $62. Friday plus Saturday at the same number is $124. If the Saturday-only guest blocks a two-night stay you would have sold, you did not “pick up a one-night.” You sold the cheap shape of a peak weekend.

Sunday can be a bridge or an orphan, depending on whether Saturday filled first. A Saturday-only booking is worse than a Sunday-only booking because it sits on the night everyone else also wants. Indiana’s attachment rule exists to stop exactly that cherry-pick.

Do not solve this with a midweek coupon. That is the shoulder-capacity job. This fence is for the nights that already want to sell.

What weekend and holiday minimums do guests already know?

They already know 2 nights on a busy weekend and a longer block on a named holiday. Public systems trained them. Copy the shape. Name the dates.

Indiana is the cleanest public spec we found in one PDF. Weekdays Monday through Thursday: 1 night. Weekends: 2 nights, with Friday and Saturday attached as above. Holidays: 3 named nights. For 2026 that is Memorial Day Friday–Sunday May 22–24, Independence Day Thursday–Saturday July 2–4, Labor Day Friday–Sunday September 4–6. If a stay touches any required holiday night, the rest of the block has to come too, unless those nights are already gone.

North Carolina is softer on holidays: 2 nights, not 3, and they lift it inside 7 days. Their own example: Saturday of Memorial Day becomes bookable as a single night starting Saturday the weekend before.

Washington spends the 2-night rule on roofed inventory: May 15 to September 15, and weekends all year. Vacation houses stay at 2 nights every calendar day.

Private parks already rhyme with this. Louisville South KOA puts 3 nights on Memorial Day, July 4, and Labor Day, and 2 nights on events including the Derby. That is one franchise page, not a KOA national statute. The guest still recognizes the pattern.

Do not run Indiana’s year-round weekend min on a 40-site April Tuesday. Demand justifies the fence. No demand, no fence.

When should you drop the minimum so gap nights still sell?

Drop it when the night will otherwise die. Keep it when the night will still sell as part of a longer stay. Write the clock. Do not leave it as “call us.”

Indiana’s One-night Relaxed Rule opens an unrented site to a 1-night stay within 3 days of arrival. Holiday minimums are excluded. They also ship a Gap Rule: if two reservations trap a Friday or Saturday alone, that night can sell as one. On a holiday, if two of the three required nights remain in a gap, both must book. No one-night holiday gaps.

North Carolina lifts the holiday 2-night min inside 7 days. Keeprstay’s vendor version is similar: strict far out, looser near arrival, fill gaps inside a week.

For a 40 to 80 site independent, a workable default is:

1. Peak weekends, 30-plus days out: 2-night min holds.
2. Ordinary weekends inside 7 days: accept 1 night if the grid still shows a hole.
3. Holiday named nights: hold the 3-night (or 2-night) block until you are inside 3 days, then sell what is left.
4. True gap between two existing stays: sell the orphan as soon as it exists. Do not wait a week to be polite.

The gap is the one you should be proud to break. Guest A Thursday–Saturday. Guest B Sunday–Tuesday. Saturday is stranded. That is not a guest “getting around the rule.” That is inventory you created. Indiana sells it. You should too.

Walk-ins and same-day phone calls belong in the same bucket. If the 50-amp pad is empty tonight, the minimum already failed. Take the night.

Should cabins and RV pads use the same stay rule?

No. Cabins cost more to turn and guests already expect a longer stay. Pads can open to one night on a Tuesday. Roofed units usually should not.

Washington puts the 2-night min on cabins, yurts, and wall tents for the summer window and for weekends all year. Houses never drop to one night. North Carolina will not lift cabin minimums even inside the 7-day holiday window. Camper cabins stay at 2 nights. Vacation cabins go to a Monday-to-Monday week in summer.

That is the public tell. Cleaning a deluxe cabin is not resetting a picnic table. If your cabin still takes one-night Friday in July, you are using hotel logic on a house.

Site-type rows beat one park-wide toggle:

Weekly and monthly guests skip the weekend min. Indiana says 7-plus nights drop the weekend attachment, still capped at 14. Your monthly is a different contract. Do not make them click Friday-Saturday as a pair.

Where do stay rules have to live to actually fire?

In the booking engine, on the date picker, and in the mouth of whoever answers the phone. If Hipcamp sells Friday-only while the guest site refuses it, you trained the cheap path.

This is the markdown config argument with nights instead of pet fees. One text. The calendar rejects below-min clicks. The guest site shows “2-night weekend” before the card. The voice path recites the same attachment rule, including the gap exception, instead of inventing a courtesy one-night that the site forbids.

Enforceable means:

1. The min is visible before pay, on the dates it applies.
2. Holiday nights are listed as dates, not “busy weekends.”
3. OTAs and the guest site map the same fence. Different mins are a leak, not a channel strategy.
4. Staff override exists for gaps and last-minute holes, and it writes the calendar. A sticky note is not an override.
5. A cancel that opens a gap can sell as one night without a human rewriting the season.

Lunaria Booking keeps stay rules in the property markdown the guest site and the voice path both read, then lets the calendar refuse a Friday-only on a fenced weekend. If your current PMS can already do that, use it. The product is one fence, not a new speech at check-in.

What should you do this week?

Do not invent a 12-row matrix. Publish one peak-weekend sentence, one holiday block, and one release clock.

1. Write the attachment rule in plain English. Peak season Friday must include Saturday, or Saturday must include Friday or Sunday. Weekdays: no minimum.

1. Name this year’s holiday nights. Copy Indiana’s habit: actual dates, not “Labor Day weekend.” If you need 3 nights, say which three.

1. Pick a release clock. Seven days for ordinary weekends, three days for holidays, immediately for a true gap. Put the numbers in the same paragraph.

1. Split cabin vs pad. If you have deluxe cabins, they get the Washington-style 2-night floor even when the RV loop does not.

1. Put the rule on the guest checkout and in the confirmation. “See policies” is how people book Friday-only on the phone.

1. Audit one OTA listing this afternoon. If it accepts a one-night Saturday in July, that listing is punching a hole in your fence.

1. Pull last July’s Friday-only and Saturday-only stays. Count how many sat next to an empty neighbor night. That count is the case for the rule. It is a worksheet, not a census.

If the calendar cannot reject the click, stop decorating the website. Fix writeback. A stay rule that only lives on a printable PDF will lose to whoever answers after dark.

FAQ

Is a 2-night weekend minimum too aggressive for a small park?

Not in peak season, if you can still fill the attached night. Indiana runs it year-round on public pads. Independents should fence the months that actually sell out, then leave April Tuesdays alone.

What if I never sell Friday once I require Saturday too?

Then the min is too strict for that loop or that month. Drop it inside 7 days, or drop it on tent sites first. Empty Friday plus empty Saturday is the failure. A held min on a dead weekend is not integrity.

Should Hipcamp and the guest site use different minimums?

No. Different mins teach guests to shop the hole. Same fence, same gap exception, every door.

Do I need different rules by loop?

Yes if the loops sell differently. Pull-through 50-amp on the river is not overflow tent. Two rows beat one park-wide toggle you keep breaking.

When do I allow a one-night Saturday?

When it is a gap between two existing stays, when you are inside your release window, or when it is the last remaining holiday night after the others have passed. Indiana already wrote those three. Copy them.

Is this the same as dynamic pricing?

No. Pricing changes the number. Length of stay changes which nights exist as a product. You can keep a flat $62 and still refuse Friday-only. Do not hide a min inside a “call for rates” mess.

Does Lunaria Booking set my minimums?

It keeps one copy. You write the nights in the property markdown. The guest site can refuse a below-min click. The voice path can say the same attachment rule. It will not invent a season if you never typed the dates.

---

Guests already book under Friday-Saturday attachment and named holiday nights. They do it on public calendars. What they will not accept is a surprise min at the gate, or a Hipcamp hole that your own site forbids. Put the fence in the engine, release the gaps on purpose, and let Tuesday stay a one-night.