Operating workflow

A compliance workflow, not a loose collection of tools

Each stage produces the next one: bookings create guest links, completed forms unlock exports or submissions, and every important action leaves operational history behind.

Booking, guest intake, submission, and evidence workflow illustration
One operating flow

Everything starts from the booking

A booking creates the guest link, the completed form unlocks reporting, and the final record stays connected to the evidence trail.

1

Capture the booking

Create bookings manually or ingest them via iCal. Claveo turns each reservation into an operational object with guest-link and compliance status.

2

Collect guest data safely

Send one guest link, let guests finish later, fill details from a document photo, and avoid storing document copies when you do not need them.

3

Run the authority pipeline

Submit to SES.Hospedajes when credentials are configured, keep XML/export fallback, and use higher-plan recovery tools when reports need follow-up.

4

Prove what happened

Use evidence exports, audit logs, informative models, and retained history when finance, ops, or inspectors ask for proof.

5

Scale beyond one host

Add owner roles, team roles, listing monitoring, guest billing, and portfolio operations with role-based access around guest data.

Pick the workflow that matches your volume

Once the workflow is clear, plan choice becomes simple: Basic for one property, Pro for more capacity and proof, Business for more users, owner roles, and portfolio operations.