VILLA OWNER GUIDES · BALI · Jembrana
Make the status of personal dates explicit
A personal stay request is not the same as a confirmed calendar block. For your Jembrana villa, define how dates are checked and approved before anybody promises availability or changes existing arrangements.
This is an owner guide. HostKeeper’s operating priority is Uluwatu and the Bukit; management in this area must be confirmed for the exact property before any agreement.
1. Label the calendar status
Use distinct labels for a requested stay, approved owner block, confirmed booking and scheduled work. Agree which calendar is authoritative. A pending request should remain visible without being mistaken for a final decision.
2. Check dependencies before confirmation
Ask the calendar coordinator to review existing arrangements, preparation needs and any conflicting work. Do not assume personal use automatically overrides another commitment. Record the decision and inform the people whose tasks are affected.
3. Keep a short change log
Use a line with request date, requested stay, previous status, decision and approver. Example: owner request received — dates under review — no confirmation sent. Add any required preparation task when the block is approved.
Fictional example — A personal stay still marked provisional
A hypothetical owner asks to use a Jembrana villa for a personal stay. Their message says the dates are likely, while the team calendar shows them as confirmed and a maintenance appointment is scheduled in the same period. The coordinator labels the stay provisional, checks the existing booking state and asks whether preparation dates also need to be held. The maintenance contact is consulted before any appointment is moved. Only the authorised calendar editor changes the final status after an explicit decision. This fictional conflict illustrates why a date request, a preparation block and a confirmed stay need separate labels; it does not assume a particular rental platform or cancellation arrangement.
Confirm the status and its dependencies
Record who approves a personal block and which reservations or appointments were checked before confirmation. Keep a requested change in the log even if the dates remain the same. The owner’s travel plan and the team’s preparation window are different entries, so neither should be silently substituted for the other.
| Entry | Requested state | Dependency checked | Final status |
|---|---|---|---|
| Owner stay | Likely dates | Existing booking record | Provisional |
| Preparation window | Needs clarification | Readiness tasks | Not yet blocked |
| Maintenance visit | Already scheduled | Contractor consulted | Decision pending |
Practical owner checklist
- One authoritative calendar identified.
- Requests and approved blocks distinguished.
- Conflicts reviewed before confirmation.
- Decisions and preparation tasks recorded.
Questions owners ask
Can owner dates be added directly to every calendar?
Choose one controlled update process, then synchronise relevant views. Direct edits in several places can leave different people working from conflicting dates.
A five-night owner request stays under review
Hypothetical example — not a client result or a market forecast
Hypothetical example: an owner requests five nights. Two overlap a confirmed reservation; three appear clear on the reference calendar. All five remain a request until commitments and preparation needs are checked. The coordinator records the decision and any approved dates, rather than automatically treating the three apparently clear nights as confirmed.