Site Readiness & Gating
Project: Hilltop
Purpose: Define the conditions under which Hilltop is permitted to host guests
Status: Required before first booking
Why This Note Exists
Hilltop operates under real constraints: rural location, limited owner availability, and a low-engagement hosting model.
Once a guest arrives, unresolved gaps in access, safety, or clarity cannot be patched casually. Small oversights become disproportionate failures.
This note establishes a gating rule:
Hilltop does not open to guests until the site meets explicit readiness criteria.
This is not about polish.
It is about preventing predictable harm.
The Site Readiness Checklist
Hilltop maintains a single authoritative artifact:
Hilltop Site Readiness Checklist (Pre-Hosting)
The checklist defines:
Physical infrastructure required for guest use
Systems that must function without host intervention
Information guests must be able to understand independently
Clear separation between guest and host areas
The checklist is organized by failure mode, not by amenities or features.
Gating Rule (Non-Negotiable)
If any Critical item on the Site Readiness Checklist is incomplete, hosting does not open.
There are no exceptions based on:
calendar pressure,
financial motivation,
guest enthusiasm,
or confidence that “it will probably be fine.”
This rule exists to protect:
guest safety,
host capacity,
and Hilltop’s reputation.
Severity Levels
Each checklist item is assigned a severity:
Critical
Required for access, safety, or basic functionality
Important
Reduces confusion, discomfort, or risk, but does not block hosting
Deferred
Enhancements or optimizations planned for later seasons
Only Critical items gate hosting.
Severity is assigned conservatively and reviewed periodically.
How the Checklist Is Used
The checklist is walked physically on-site, not reviewed abstractly
Items are tested under realistic conditions:
first-time arrival
nighttime
poor weather
low energy or distraction
An item is marked complete only after repeated success
Temporary workarounds do not qualify as completion
The checklist may evolve, but the gating rule does not.
Relationship to Hosting Model
This note supports Hilltop’s operating posture:
On-site, low-engagement host
High guest self-sufficiency
Minimal tolerance for ambiguity
The checklist reduces reliance on:
mid-stay explanations,
ad-hoc fixes,
and emotional labor.
If a system requires explanation to function, it is not ready.
Known Risks
Expanding the checklist beyond what is necessary
Treating “Important” items as “Critical” due to anxiety
Ignoring checklist signals to meet a target date
These risks are managed through discipline and review, not urgency.
Bottom Line
Hilltop opens only when the site can:
be entered without assistance,
be navigated without confusion,
operate safely without host intervention,
and handle predictable issues without panic.
