Booking rules that match
how your floor actually works.

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.

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.

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.