Keep the booking story intact.

Every unresolved guest question needs an owner and a next action, not just a read indicator.

Verify the property, date and accepted task again when a booking changes.

Preserve both reservation references and stop speculative changes while you establish the authoritative facts.

Keep a privacy-conscious continuity plan that does not depend entirely on the unavailable application.

Separate account ownership from day-to-day collaboration and keep access removal part of the workflow.

Use the minimum information needed for each task and keep private records out of public tools and examples.

Review unresolved work, actual costs and changed requirements rather than collecting dashboard numbers without a purpose.

Know what can be exported, what remains connected and what happens to access before cancelling.

Launch only when property mapping, booking responsibilities and recovery are understood—not when the website merely looks finished.