Bunkpost

Chapter 05 — Run the park

The calendar is the source of truth

Every site, every night, one screen — plus maintenance blocks, and the database rule that makes double-booking physically impossible.

At a glance

One grid
Every site down the side, every night across the top. Online, phone, and walk-in bookings all land here.
Blocks
Maintenance and owner holds that take a site out of availability exactly like a reservation would.
Double-booking
Prevented by the database itself, not by an app-level check. Two overlapping stays cannot be stored.
Same-day turnover
A checkout and a check-in on the same day is allowed — nights are counted, not days.

Every site, every night, one screen

The calendar is a grid: sites down the side, nights across the top, reservations as bars. A booking made online at midnight looks exactly like one you typed in during a phone call — same bars, same rules, same screen your staff already has open. Long-term stays stretch across it as one continuous bar, so a seasonal guest never looks like an empty site.

app.bunkpost.com/calendar
The Bunkpost calendar: sites down the side, nights across the top, reservation bars filling the grid

A July week at a 60-site park — reservations, long-term stays, and one blocked site.

Blocks: holding a site without inventing a fake guest

Water line burst on site 9? Add a blockwith a date range and a note. Blocks participate in availability exactly like reservations do — the site vanishes from online search for those dates, and nobody can book over it, including you. Delete the block when the repair's done and the site is instantly sellable again. No more “JOHN — DO NOT BOOK” placeholder guests haunting your reports.

Why double-booking is impossible, not just unlikely

Most booking systems check whether a site is free, then save the reservation — and if two requests land in the same instant, both checks pass and you get the Saturday-morning driveway standoff. Bunkpost puts the rule in the database itself: an exclusion constraint that makes it physically impossibleto store two overlapping stays on one site. Not “we check first” — the second write is rejected by the database, no matter how it arrives: booking page, front desk, or two staff on two laptops at once.

The same hard rule covers blocks and long-term stays, so every kind of occupancy defends its dates the same way.