VILLA OWNER GUIDES · BALI · Tabanan
Keep repair decisions traceable for your Tabanan villa
A repair register links a reported issue to a decision, an authorised scope and a verified result. It is a maintenance record, not a return forecast.
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.
Open one record for each issue
Describe the reported defect, its location and who observed it. Attach relevant evidence and record whether an assessment is needed. Keep an estimate separate from an approved instruction. The owner should be able to see what is proposed and what has actually been authorised.
Track scope changes explicitly
If a contractor proposes additional work, record the reason and revised scope before accepting it. Identify who may approve the change under the owner’s arrangement. Keep invoices and completion notes linked to the correct issue rather than grouping unrelated repairs under a vague maintenance entry.
Use an approval-to-completion row
A compact register helps distinguish pending decisions from finished work. Record the agreed expenditure without turning an estimate into a final cost.
Example row: “Issue ID — inspection needed — proposed scope — estimate status — approval date — contractor confirmation — completion evidence — owner notified.” Close the row after the agreed outcome is checked; retain any outstanding item separately.
Fictional example — A changed scope needs a new decision
A fictional Tabanan owner receives a proposal to replace one cupboard hinge. After looking at the cupboard, the contractor also proposes adjusting its frame. The initial approval mentions only the hinge, but a chat reply saying “go ahead” does not identify which version it refers to. The coordinator keeps both scopes in the repair record and requests an explicit answer on the revised proposal. No amount is invented or treated as an agreed limit. Work status and approval status appear separately, so a contractor appointment cannot be mistaken for authorisation of every suggested addition. This scenario is an administrative example, not a cost estimate or financial recommendation.
Keep scope changes visible
Do not overwrite the first proposal with the expanded one. Name the new scope, identify its supporting quotation and record the owner’s decision for that version. The repair row should distinguish awaiting approval, authorised work and checked completion, so changes can be understood later without reconstructing a long message thread.
| Issue | Scope version | Approval state | Completion evidence |
|---|---|---|---|
| Cupboard hinge | A: hinge only | Approved for A | Not yet supplied |
| Frame adjustment | B: additional adjustment | Awaiting explicit decision | Not applicable |
| Final cupboard check | Approved scope only | Review after work | Photo and operating note |
Practical owner checklist
- Issue and evidence identified.
- Estimate separate from approval.
- Scope changes explicitly confirmed.
- Completion checked and owner informed.
Questions owners ask
Does an approved estimate mean the repair is complete?
No. Approval authorises the agreed work. Completion still requires the contractor’s report and a check of the result against the recorded scope.
Keep a revised quote separate from approval
Hypothetical example — not a client result or a market forecast
Hypothetical example: a repair quote lists IDR 1,500,000 of labour and IDR 300,000 of parts, totalling IDR 1,800,000. An additional IDR 250,000 item raises the proposal to IDR 2,050,000. The register records the revised proposal and requests the required approval before the extra work is ordered.