VILLA OWNER GUIDES · BALI · Buleleng
Keep one reliable photo file for your Buleleng villa
A villa’s photographs can become confusing when edits and older images circulate in several folders. A structured photo file helps a Buleleng owner see which version is current and where it has been used.
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.
Label originals and published versions
Keep an original file separate from crops and edited exports. Name files using the capture date, space and version. For example: “date-bedroom2-terrace-view-v1”. Record the person who supplied the image and the agreed uses. Keep those instructions with the file instead of relying on a chat memory.
Maintain a simple publication register
Use columns for image reference, room shown, current status and publication location. Link each published version to its original. If a listing uses a crop, record that crop specifically. This lets the team replace the right image without accidentally reintroducing an older bedroom layout or removed amenity.
Archive changes without losing context
After a renovation or furniture change, mark affected photographs “replace” and review every location recorded in the register. Keep superseded images in an archive clearly separated from publishable files. Select a person to approve the current set and record the review date so everyone works from the same version.
Fictional example — One room change, several published photographs
A fictional Buleleng owner replaces a bedroom desk. The new photograph enters the team folder, but an old crop still appears on a listing and the welcome guide. Neither export is labelled with its source, so uploading the new image to one platform does not resolve the other uses. The coordinator connects each published file to its original reference and marks the outdated desk images for replacement. The archive preserves the old versions while keeping them outside the publishable set. Agreed image-use permissions remain with the source record. This example explains version control; it does not claim that an illustrative photograph proves a real villa feature or a customer result.
Track publication locations, not just files
For every current image, record the original, the exact export and each location where it is used. Review those locations after a visible room change. An archive label prevents accidental reuse, while source and agreed-use information help the editor choose a replacement without assuming that every available photograph can be published.
| Image reference | Room/version | Publication location | Current decision |
|---|---|---|---|
| Original B1 | Old bedroom desk | Source archive | Do not publish |
| Crop B1-C | Old desk crop | Listing and welcome guide | Replace both uses |
| Original B2 | Current bedroom desk | Approved source set | Confirm agreed exports |
Practical owner checklist
- Separate originals from edited exports.
- Record image source and agreed uses.
- Track every published version and location.
- Archive replaced images with clear labels.
Questions owners ask
Should I delete every old image immediately?
Not necessarily. A separate archive preserves context, while clear status labels prevent obsolete images from being reused publicly.
Archive six of twenty originals clearly
Hypothetical example — not a client result or a market forecast
Hypothetical example: a photo register contains twenty originals. Fourteen represent the current villa; six belong to an earlier layout and are archived. Two of the six old images are still used on a booking channel. The publication register identifies those two exports for replacement while preserving the original files and their source information.