Add guest-detail, rules, waiver, acknowledgement, or signature steps to the applicable guidebook.
Features
Waivers and required fields
Collect the stay requirements your operation needs before arrival.
Configure guest fields, rules acceptance, waivers, acknowledgements, signatures, and supporting evidence as required or optional pre-check steps.
Property playbook and operational loop
Define the requirement once, then run it for every applicable reservation.
The property playbook determines which guest details and agreements matter. Each stay then presents those requirements before protected arrival information is revealed.
1
Add guest-detail, rules, waiver, acknowledgement, or signature steps to the applicable guidebook.
2
Mark each field or step as required or optional for the stay.
3
Present the requirements inside the reservation-aware guest pre-check flow.
From requirement setup to completed record
The exact steps vary by listing and account settings, but the shape is consistent: define the standard, run the stay, and keep exceptions visible.
Mark each field or step as required or optional for the stay.
Present the requirements inside the reservation-aware guest pre-check flow.
Gate protected guidebook sections until required steps are complete.
Review submitted fields, acceptance evidence, signed artifacts, receipts, and timestamps.
Capabilities operators can put to work.
These are the practical pieces teams use to keep guest experience, listing work, and readiness signals connected.
Required guest fields
Collect the contact and stay details the operation needs before arrival.
House-rule acceptance
Present property rules and record the guest's acknowledgement.
Waivers
Collect liability releases for property amenities or stay requirements.
Typed signatures
Record typed names and signature evidence for supported acknowledgement steps.
Electronic signatures
Send supported documents through an electronic-signature flow when configured.
Evidence logs
Keep completion records, receipts, timestamps, and submitted artifacts available to operators.
Connected context
Connected to guidebook access and reservation evidence
Required fields and waivers live inside the guest flow so operators do not have to reconcile a separate form with the reservation later.
The applicable guidebook determines which pre-check requirements the guest receives.
Reservation matching keeps the submitted record tied to the stay.
Protected arrival content can remain gated until required steps are complete.
Operator alerts and evidence logs support follow-up and review.
Who gets value from waivers and required fields
Operations manager
Sees which arrivals are still missing a required guest action.
Owner-operator
Keeps property requirements and completion evidence attached to the stay.
Guest
Completes the required details and agreements in one clear pre-arrival flow.
Feature questions
A few practical details operators usually want to understand before adding this to their workflow.
Related features
Can a field be required before arrival details appear?
Yes. Required pre-check steps can gate protected guidebook sections until completion.
What kinds of waivers can operators collect?
Operators can configure waiver or acknowledgement steps for relevant property amenities, rules, and stay requirements.
Can operators review completion evidence?
Yes. Available records can include submitted fields, signatures, receipts, timestamps, and signed artifacts.
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.