Define required or optional pre-check steps for one or more guidebooks.
Features
Guest pre-checks
Collect the details, acknowledgements, and documents each stay requires before arrival.
Use configurable pre-check steps to collect guest details, house-rule acceptance, waivers, signatures, ID review, and evidence logs inside the guest flow.
Operational loop
Pre-checks are the first readiness checkpoint for each booking.
The listing playbook defines what is required. Each reservation then runs that requirement before arrival so sensitive details, access, and protected guidebook content are not handled by scattered emails.
1
Define required or optional pre-check steps for one or more guidebooks.
2
Ask guests for details, confirmations, documents, signatures, and opt-ins where needed.
3
Gate protected guidebook content until required steps are complete.
How pre-arrival compliance works
The exact steps vary by listing and account settings, but the shape is consistent: define the standard, run the stay, and keep exceptions visible.
Ask guests for details, confirmations, documents, signatures, and opt-ins where needed.
Gate protected guidebook content until required steps are complete.
Review intake logs, evidence, guest receipts, and host receipts.
Keep the completed record tied to the reservation and guest.
Capabilities operators can put to work.
These are the practical pieces teams use to keep guest experience, listing work, and readiness signals connected.
Guest detail forms
Collect the fields your operation needs before the guest arrives.
Rules acceptance
Present house rules and record acceptance before protected stay details are shown.
Waivers and acknowledgements
Collect signatures, typed names, and agreement evidence for amenities or stay requirements.
ID review
Collect and analyze government-issued identification where your account and process require it.
Electronic signatures
Send documents for signature where the account supports document signing.
Evidence logs
Review timestamps, completed steps, receipts, and submitted artifacts from the management app.
Connected context
Connected to guidebooks, reservations, and access
Pre-checks work best when they are not a separate form tool. They protect the stay information guests need and give operators a clear record before arrival.
Guidebooks can reveal protected sections after required steps are complete.
Reservation matching keeps the intake connected to the stay.
Arrival access can stay aligned with required guest steps.
Operator alerts help teams follow up when something is missing.
Who gets value from pre-checks
Operations manager
Sees which arrivals still need guest action before day-of-arrival pressure starts.
Guest experience lead
Collects requirements without a fragmented thread of forms, attachments, and reminders.
Owner-operator
Keeps records for rules, waivers, and guest confirmations in one place.
Feature questions
A few practical details operators usually want to understand before adding this to their workflow.
Related features
Can pre-checks be required before guests see arrival details?
Yes. Required pre-checks can gate protected guidebook content so guests complete the right steps before viewing sensitive stay information.
What kinds of steps can operators collect?
Operators can collect guest details, rule acceptance, waivers, acknowledgements, signatures, ID information, signed documents, and opt-ins.
Are completed pre-checks visible to the operator?
Yes. Intake records, submitted evidence, receipts, signed artifacts, and completion logs are available for review.
Rental readiness your team can run on every stay.
Start a 14-day free trial with no credit card required, or book a demo and we will walk through your playbook and operational loop.