Ecotourism in a village only works if someone is clearly in charge of it — and if everyone knows who that is. This session covers the institutional side: mandate, structure, task division, record keeping and accountability.
1. Introduction to professional governance#
Governance is the answer to four questions: who decides, who does, who records, and who is answerable when something goes wrong. A village tourism operation that cannot answer those four questions will operate — but it will operate differently every week, and no procedure will hold.
2. Learning objectives#
By the end of the session participants should be able to explain the difference between the three organisational forms available to a village, describe the units a mangrove ecotourism operation needs, and run a visitor from first inquiry to post-visit feedback without losing the record.
3. Organisational structure#
The proposed structure has three levels: the village authority that holds the mandate, an operations coordinator who runs the destination day to day, and five working units — reservation and administration, guides and visitor service, safety, conservation, and finance.
Proposed model, not an adopted structure
The structure below is the model used in the session to organise the discussion. It has not been adopted by Desa Sugian or Desa Seruni Mumbul; each village decides its own institutional form.
4. Task division and responsibility#
Each unit receives a defined set of tasks, the authority to carry them out, and the record it must keep. The test used in the session is simple: if the coordinator is absent for a week, does the destination still run and is the record still complete?
5. Staff rotation#
Community-managed operations rely on people who also have other work. A rotation scheme keeps the operation running without depending on one person, and it spreads competence: every guide should be able to take a booking, and every reservations person should know the safety briefing.
6. Reservation management#
Reservation is the point where capacity, safety and revenue meet. The session's rule: no booking is confirmed without a record of date, group size, route, guide assignment and fee. Capacity limits come from the conservation rules, not from what the boat can physically carry.
7. Visitor service#
Service is standardised at the points where inconsistency damages either safety or the mangrove: the first response to an inquiry, the arrival greeting, the safety briefing, the conduct expected on the trail and on the water, and the closing feedback request.
8. Preparation before the visit#
Before visitors arrive the unit checks the route, the equipment, the tide and weather condition, the guide assignment and the briefing material. A preparation checklist is the difference between a routine and a habit.
9. Operational activity#
During the visit the guide holds the group to the agreed route, enforces the protection rules, keeps the group count, and stays within the competence of the team on duty. Activities outside the route require a decision, not an improvisation.
10. Complaint handling#
A complaint channel with a named owner, a written record and a response time. The session's position is that an unrecorded complaint cannot be fixed and will be repeated.
11. Facility checks#
Boardwalks, jetties, boats, life jackets and signage are checked on a schedule with a signed record. A facility that fails a check is closed until it passes, not used carefully.
12. Administration and reporting#
The operation keeps four records as a minimum: bookings, visitor numbers, money, and incidents. Those four produce the monthly report that the village and the programme both need.
13. Situational learning#
Participants worked through operating situations — a group arriving without a booking, a guide absent at short notice, a visitor refusing the safety briefing, a damaged section of boardwalk — and identified which unit owns the decision.
Recorded situations and responses pending
The specific situations used and the answers given in the room are entered from the facilitator notes. They are not reconstructed here.
14. Participant interaction#
Each village drafted its own structure and task list, then presented it to the other village for questions. The cross-questioning is the part participants used most, because it exposes a task that has no owner.
15. Output#
- Draft organisational structure and unit responsibilities per village.
- A visitor service routine from inquiry to reporting.
- An operational checklist set covering before, during and after the visit.
16. Expected outcome#
Each village has a written institutional proposal it can take to its own decision-making forum, and the SOP register has an owner for every procedure.
17. Recommendations#
- Take the organisational draft to the village forum before any SOP is approved.
- Assign each SOP in the registry to a named unit once the structure is decided.
- Adopt the four core records immediately, even at low visitor volume.
Learning objectives#
- Understand what a management mandate is and why it precedes every other procedure
- Distinguish a community group, a village-owned enterprise and a formal management body
- Design a task division that survives staff rotation
- Write the reservation, service and complaint routine as a procedure
Presentation method#
Technical input followed by group drafting; each village built its own organisational draft and walked a visitor inquiry through it.
Interaction & Q&A#
Situational exercises: participants were given operational situations and asked which unit owns the problem.
Output & outcome#
A draft organisational structure per village, a task-and-responsibility list, and a visitor service routine ready to be converted into SOP text.
Proposed framework for discussion. Not an institutional structure adopted by either village.
Proposed organisational levels#
-
01
Village authority#
Holds the mandate, adopts the rules, receives the reports.
-
02
Operations coordinator#
Runs the destination, coordinates the five units, answers for daily decisions.
-
03
Five working units#
Reservation & administration · Guides & visitor service · Safety · Conservation · Finance
Proposed model used to organise the discussion.
- Reservation & administration Bookings, records, reporting, correspondence
- Guides & visitor service Interpretation, briefing, conduct on the trail and water
- Safety Equipment, checks, emergency response, incident record
- Conservation Zoning compliance, monitoring, rehabilitation
- Finance Fee collection, recording, allocation and reporting
Working units proposed for the discussion. Not an adopted structure.
Visitor service flow#
-
1
Inquiry#
First response, information on route, capacity and rules.
-
2
Booking#
Record of date, group size, route, guide and fee.
-
3
Confirmation#
Written confirmation with the conduct rules attached.
-
4
Preparation#
Route, equipment, tide and guide assignment checked.
-
5
Guest arrival#
Registration and grouping.
-
6
Safety briefing#
Mandatory before entering the water or the trail.
-
7
Tour activity#
Agreed route, protection rules enforced, group count held.
-
8
Completion#
Equipment returned, area checked, feedback requested.
-
9
Feedback#
Complaint or compliment recorded with an owner.
-
10
Reporting#
Visitor numbers, money and incidents into the monthly report.
Operational checklist#
Before operating#
- Confirm today's bookings, group sizes and route
- Check tide, weather and route condition
- Check boats, life jackets, first aid kit and communication device
- Confirm guide assignment and briefing material
Receiving guests#
- Register the group and check the booking record
- Deliver the safety briefing before departure
- State the protection rules and the route
During the activity#
- Hold the agreed route and group count
- Enforce the protection rules without exception
- Stop the activity if a safety condition changes
After the activity#
- Return and check equipment; record any damage
- Ask for feedback and record complaints
Daily evaluation#
- Record visitor numbers, income and incidents
- Report any facility fault for repair before next use
Editable checklist used in the session. It is a template to be adopted per village, not an approved procedure.
Supporting documents & downloads
One page can carry several PDF attachments. Until the documentation team uploads them, this section says so instead of offering an empty download.
Supporting documents will be available after publication.
Sources & references
Workshop brief and three-day agenda supplied by the MARVEL – Wahana Visi Indonesia programme team (16–18 October 2026, Aston Inn Mataram). Session outline and speaker assignments as supplied.
Editorial status: Proposed framework.