A teaching week is a timetable
Bali volunteer teaching weeks fail when the itinerary is written as vibes. Treat the week as a service-learning file: lesson briefs teammates can run, host hours, cultural working conditions, and reflection that can be marked.
Families should ask for the day-by-day teaching load before they ask for leisure add-ons. Water after teaching, never instead of teaching.
Forty-eight hours before arrival
Confirm lodging, transport, dress expectations, and local contacts. Offline-save lesson briefs. Pack for heat, rain, and a classroom. Students write a respect note: what they will not photograph and how they will name hosts without turning people into scenery.
Listen, then teach short, then hand off
Opening days are observation with a job. Student teachers run short segments written so a teammate can continue. Midweek privileges lessons that can be handed over. Evenings revise briefs; they do not turn the day into content.
Close with specific gratitude and a dated portfolio page. Do not inflate impact. Preparation is a file; rhythm keeps the file honest.
Operational checklist 1
Treat block 1 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 2
Treat block 2 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 3
Treat block 3 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 4
Treat block 4 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 5
Treat block 5 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 6
Treat block 6 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 7
Treat block 7 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.