# Booking rules that match how your floor actually works.

Per-tier horizons, blackouts, member-only resources, and front-desk overrides that never leave the calendar. Conflicts surface where the booking lives — not in a 9pm email.

## 01 — Capability

### Three primitives. Every coworking edge case.

Booking rules in LiteHQ aren’t a settings tab — they’re first-class objects with conditions, actions, exceptions, and an audit trail. Compose them like Lego.

- **Per-tier horizons**  
  Pro books 14 days out, Day Pass 24h, Resident 60. Each tier carries its own rule, applied at the resource level — not a single global setting.
  
  Stacks with member-only rooms and time-of-day windows.

- **Blackouts**  
  Close a resource for the holidays, an event take-over, or scheduled maintenance. Members see the closure in the same calendar UI they book from.
  
  One-off date, recurring window, or whole-location.

- **Override without leaving**  
  Front desk can bypass any rule from the booking modal — with a reason captured to the audit log. No back-office dance, no shadow spreadsheets.
  
  Permissioned per role. Every override is logged.

## 02 — Rule builder

### Conditions. Actions. Audit.

Every rule reads like a sentence. Conditions stack with AND/OR. Actions trigger inline — block, queue, bump, notify, charge tokens, require override. The audit log ties every fired rule back to the booking that triggered it.

- **No DSL**  
  Plain English in the UI; JSON under the hood for the API

- **Live preview**  
  See affected bookings before you publish

- **Stage + ship**  
  Draft, simulate against last 30 days, then enable

### New rule · Member rooms — after-hours

**Draft**

**Conditions**  
When member books Atrium · Forum · Studio  
AND tier is Day Pass · Lite  
AND time is after 18:00 on weekdays

**Actions**  
Then block booking  
Message “Evening rooms reserved for Pro tier.”  
Override allowed for Front desk · Manager  
Affects ~12 bookings/wk in the last 30 days

**DiscardSimulatePublish**

## 03 — Example rules

### Five rules every coworking space ends up writing.

Real examples from the LiteHQ template library. Copy them to your space in one click, or compose your own. Every rule is reversible.

- **When**  
  Pro members booking · any resource  
**Then**  
  Can book up to 14 days in advance  
  **Horizon**

- **When**  
  Day Pass · any resource  
**Then**  
  Can book within the next 24h only  
  **Horizon**

- **When**  
  Anyone · Boardroom · Penthouse  
**Then**  
  Require manager approval before confirming  
  **Approval**

- **When**  
  All resources · Dec 24 → Jan 2  
**Then**  
  Closed for holidays — display blackout in calendar  
  **Blackout**

- **When**  
  Resident tier · Studio · weekdays before 09:00  
**Then**  
  Auto-confirm and waive token charge (early-bird perk)  
  **Perk**

## 04 — Conflict surface

### Conflicts surface where the booking lives.

On the left, the rule engine evaluates the request in milliseconds. On the right, the calendar highlights the exact slot — and the rule that triggered. Front desk sees the same view the member does.

**Rule evaluation live**  
1. 01 Resource lookup · Atrium matched  
2. 02 Tier check · Day Pass · Lite matched  
3. 03 Horizon check · 13 days out max 1 day  
4. 04 Blackout check  
5. 05 Result rule #r_8e2

**Atrium · Friday May 22 Conflict**

Standup · Eng 10:00 – 11:30 Requested · blocked 13:00 – 15:00 · rule #r_8e2

Day Pass tier can book max 24h ahead. Try Sunday — or upgrade tier.

**Override**

**Operator**  
> “The rule builder is the first time I’ve seen a booking system that thinks like an operator. We turned three Notion docs into seven rules. The night-staff spreadsheet is gone.”

### See your own rules in 24 hours.

Send us your current rules — Notion docs, spreadsheets, whatever — and we’ll load them into a live LiteHQ demo with your bookings.