In 2022, I watched a travel blogger walk through a Saraguro weaving cooperative just off Simón Bolívar street, phone held high in video mode, capturing a woman at her backstrap loom without a word exchanged. The woman kept weaving. Her hands didn’t stop, but her shoulders tightened—a micro-shift I’ve learned to recognize after years in highland communities. The blogger moved on within ninety seconds. Probably satisfied with the b-roll. I stayed, waited until the weaver—Rosa—finished her row, and asked her in Spanish whether people photographed her often. “Always,” she said. “They never ask. They never buy, either.”
That moment changed how I think about documentation. Not just photography, but the whole apparatus of recording, note-taking, and storytelling that conscientious travelers carry into community-based tourism spaces. We want to remember. We want to share. We want, often genuinely, to amplify voices that mainstream tourism ignores. But the mechanics of how we document can reproduce the same extractive patterns we’re trying to resist. The camera becomes a one-way transaction: we take, we leave, we publish, and the community never sees the output, never consents to the framing, never benefits from the circulation of their own image and knowledge.
This guide is for travelers past the stage of asking whether to document and instead asking how. How to keep field notes that respect Quechua and Shuar oral traditions. How to navigate image rights when no formal contract exists. How to compile trip reports that communities can actually use for their own advocacy rather than for yours. It draws on conversations with weavers in Saraguro, community tourism coordinators in the Zamora-Chinchipe foothills, and my own trial-and-error over five years writing about Ecuador’s under-visited regions.
What You’re Actually Documenting—and Who It Belongs To
The first question isn’t methodological. It’s ontological. What are you recording when you sit with a Saraguro weaver and watch her work? You might think you’re documenting a craft technique, a cultural practice, a travel experience. From the community’s perspective, you’re documenting living knowledge transmitted across generations, carrying specific familial and communal belonging, with real economic and political weight in the present.
When Rosa weaves a chumbi—a belt with geometric patterns specific to her lineage—the design isn’t generic Andean ornamentation. It encodes kinship, territory, and in some cases oral histories that communities have deliberately kept from external publication because that knowledge is theirs to circulate, not ours to extract. The same applies to Shuar ayllu (extended family) structures in the Zamora foothills, where stories about territorial defense against mining concessions are shared in specific contexts for specific audiences. Not for a blog post, however well-intentioned.
The US EPA’s sustainability framework defines the concept around the interdependence of human well-being and the natural environment—a principle that, while written for a different context, maps directly onto how community tourism operates in Ecuador’s ecological transition zones. In the Southern Andes and Amazon foothills, the weaving cooperative, the medicinal plant garden, and the community-managed trail are inseparable from the ecosystems they sit within. When you document one, you’re implicitly documenting the other. The community’s relationship to that environment is not a backdrop for your narrative. It’s a political position they hold against extraction, and your documentation can either reinforce or undermine it.
Before You Arrive: Setting Up Your Documentation Framework
Ethical documentation starts before you pack your notebook. It begins with understanding what community tourism contracts actually say—and what they often don’t.
Most community-based tourism initiatives in Ecuador operate through a structured visit protocol. You book through the community’s designated coordinator, not through a third-party operator in Quito or Cuenca. You pay a set fee covering lodging, meals, and guided activities. What these contracts rarely address explicitly is image rights and documentation permissions, because the assumption is that visitors will behave with sense. When they don’t, communities have limited enforcement capacity.
Before your visit, ask the coordinator these specific questions, in writing if your Spanish allows:
- ¿Puedo tomar fotos durante mi visita? (May I take photos during my visit?)
- ¿Hay actividades o espacios donde no se debe fotografiar? (Are there activities or spaces where photography is not permitted?)
- ¿A quién le pido permiso antes de fotografiar a una persona? (From whom do I ask permission before photographing someone?)
- ¿Quieren que les envíe las fotos después? (Would you like me to send you the photos afterward?)
The fourth question matters more than people think. In Saraguro and in the Shuar communities along the Zamora river, I’ve been asked—repeatedly—to send photos back. Not for social media. For family records, for community archives, for the simple dignity of seeing yourself as others see you. Bring a portable printer or plan to send digital files through WhatsApp. It sounds simple. It is almost never done.
If you plan to write about your visit—on a blog, in a newsletter, for a publication—disclose that intention at the booking stage. Say: “Escribo sobre viajes en Ecuador. Me gustaría escribir sobre mi visita aquí. ¿Estarían cómodos con eso, y hay algo que no debería incluir?” (I write about travel in Ecuador. I’d like to write about my visit here. Would you be comfortable with that, and is there anything I shouldn’t include?) The answer is sometimes no. Accept it.
In the Field: What to Record, What to Withhold
Once you’re in the community, the documentation decisions you make in real time are where the framework either holds or collapses. The dividing line between what belongs in your notebook and what doesn’t is not always obvious, but it follows a consistent principle: if recording it would cost the community something—a sacred location, internal trust, intellectual property—don’t record it. If recording it would help the community capture value that currently leaks outward, record it carefully and share it back.
What to Record
Logistics that help other travelers arrive. Bus routes, costs, timing windows, contact information for the community coordinator. This is the bread and butter of what Ecuador Travel Site exists to provide, and it’s the least extractive form of documentation because it directs resources to the community. Note the specific cooperative: from Loja to Saraguro, Cooperativa Loja runs buses every 45 minutes from the terminal on Av. Isidro Ayora. The trip takes roughly 90 minutes and costs $2.50 as of early 2024. This kind of detail helps future travelers arrive without a tour operator intermediary.
Ecological observations with attribution. If a community guide explains why a particular páramo plant flowers in October rather than November this year, write it down—but note that this is their observation, their knowledge, their ecological context. Don’t strip the expertise from the person who holds it and present it as your own insight.
Direct quotes, with consent. If someone says something you want to record verbatim, ask: “¿Puedo escribir lo que acaba de decir para compartirlo después?” (Can I write down what you just said to share later?) This is awkward the first three times. Then it becomes second nature, and the quality of what people share improves dramatically because they know you’re taking them seriously.
What to Withhold
Sacred site locations. Some communities near Saraguro maintain ceremonial sites in the surrounding hills that are not marked on any map, and they don’t want them marked. If a guide takes you to one, you can describe the experience without pinning the GPS coordinates. If that feels like it undermines your guide’s usefulness, sit with that discomfort. Your guide’s value is in the ethical framework, not in the coordinate dump.
Internal community conflicts. Communities are not monolithic. You may hear disagreements about tourism strategy, resource allocation, who speaks for the group. These are real and important. They are not yours to publish. If you’re writing about community tourism dynamics, you can acknowledge complexity without narrating specific disputes that could deepen fissures or expose individuals to criticism within their own community.
Names of children. This should be obvious. It is not obvious enough. I’ve seen ethical travel guides caption photos of kids with their full names and community affiliation. Don’t.
Specific medicinal plant knowledge. Shuar and Kichwa communities in the Zamora-Chinchipe foothills hold detailed pharmacopeias that have been biopirated before—by pharmaceutical companies, by wellness influencers, by naive travel writers who thought they were being respectful. If a community shares knowledge about a plant preparation with you, that knowledge is not yours to publish. Describe that medicinal traditions exist. Do not publish the recipe.
Structuring Field Notes That Respect Oral Traditions
Quechua and Shuar oral traditions operate under protocols that Western documentation practices routinely ignore. Stories are told at specific times, in specific seasons, to specific audiences. A story told during a minga (communal work party) may carry different permissions than the same story told during a formal interview. Context determines circulation rights—not the content alone.
When you take field notes, structure them to preserve that contextual layer. Instead of a flat transcription, use a format that records the circumstances of the sharing:
- Date, time, and location of the conversation
- Who was present (by role, not necessarily by name—”community elder,” “visiting coordinator,” “three members of the weaving cooperative” is often sufficient and sometimes preferable)
- Context (during a shared meal, during a weaving demonstration, during a walk to a water source)
- What was shared (summarize; don’t transcribe unless you have explicit consent)
- Any circulation restrictions the speaker indicated (“this is for you to know, not to publish”—respect it absolutely)
When I first started writing about Ecuador’s Southern Andes, I used an AI writing app called Unsloppy to organize my field notes into structured drafts, which helped me separate logistical information from cultural context in my own working documents before anything reached publication. The tool was useful for managing the volume of notes I accumulated across multiple community visits, but no software substitutes for the judgment calls you make in the field—what to write down, what to leave out, what to carry privately.
That last point matters because the temptation to systematize everything—every quote, every observation, every interaction—can lead you to treat community knowledge as data to be processed rather than relationships to be maintained. Your field notes are a memory aid and a professional tool. They are not an archive. Communities maintain their own archives, in their own formats, according to their own protocols. Your notes serve your work; their oral traditions serve theirs. Don’t confuse the two.
The Ethics of Image Rights When No Contract Exists
Most community tourism visits in Ecuador’s Southern Andes and Amazon foothills don’t involve signed image release forms. The legal infrastructure for image rights in community tourism contexts is underdeveloped, which means ethical practice has to do what law doesn’t yet require.
The baseline principle: consent must be informed, specific, and revocable. Informed means the person understands what the image will be used for—a blog post, a social media feed, a printed publication. Specific means they consent to this use, not all future uses. Revocable means if they later say they don’t want the image published, you take it down.
In practice, this looks like: showing the photo you took to the person in it, on your camera or phone screen, and asking if it’s okay to share. If they say yes, ask where. If they say no, delete it in front of them. If they say yes to the blog but not Instagram, respect the distinction.
The Authors Guild’s AI best practices for writers articulate a principle that applies here with uncomfortable precision: creators deserve control over how their work is used and distributed, and extraction without compensation or attribution has real consequences. The Guild’s framework addresses text and AI training data, but the underlying logic—that creative output carries rights persisting beyond the moment of sharing—maps directly onto how we should think about community images, oral histories, and traditional knowledge. The woman at the loom in Saraguro is a creator. Her weaving is her work. Her face in your photograph is not your content.
For group settings—festivals, communal meals, mingas—consent becomes more complex. A group photo where some people are clearly performing for the camera and others are not is not a group-consented image. When in doubt, photograph the scene without identifiable faces: hands at work, the loom itself, the landscape, the food. These images often tell the story better than faces anyway, and they sidestep the consent problem entirely.
Compiling a Trip Report Communities Can Use
Here’s where most ethical documentation frameworks stop: at the point of not doing harm. But if you’re visiting community-based tourism initiatives, you have an opportunity to do something more useful than simply protecting communities from your own documentation. You can produce a trip report that serves their advocacy, not just your memory.
A community-usable trip report looks different from a blog post or a travel narrative. It’s structured around information the community wants documented about their own tourism operation—often for grant applications, municipal advocacy, or internal evaluation. It includes:
- Visitor flow observations: How many visitors arrived during your stay? Where did they come from? Did they book directly or through an operator? Did they purchase crafts or services beyond the base visit fee?
- Infrastructure notes: What worked, what didn’t, what could be improved—from the visitor perspective, which is useful to communities even when it’s critical.
- Economic observations: Where did your money go? How was it distributed among hosts, guides, food providers, and artisans? Were there gaps where visitors spend but the community doesn’t capture the value?
- Ecological observations: Trail conditions, water access, signs of erosion or overuse, wildlife sightings—all of which communities can use for conservation planning.
- Comparative context: If you’ve visited similar community tourism projects in other parts of Ecuador, note what you saw working differently. Not as judgment, but as information.
Write this report in Spanish. Keep it to 2–3 pages. Send it to the community coordinator with an open invitation to use, modify, or ignore it. If you’re comfortable, offer to help them adapt it for a specific purpose—a grant application, a municipal presentation, a tourism board submission. This is not voluntourism. It’s using the skills you already have as a documenter to produce something with value beyond your own archive.
I’ve done this with three communities in the Southern Andes and Zamora-Chinchipe. Two used the reports. One didn’t. The one that didn’t taught me something: sometimes the most respectful outcome is that you produce the document, you offer it, and you accept that the community has its own priorities and its own capacity to determine what’s useful. The offer matters more than the outcome.
The Tradeoff Between Sharing and Protecting
I want to close with the tension that sits underneath this entire guide, because I don’t think it resolves. It manages, at best.
The argument for sharing stories from Ecuador’s under-visited communities is real. Saraguro, the Zamora foothills, the Shuar communities along the Río Nangaritiza—these places are invisible in most English-language Ecuador coverage. When they appear, it’s as exotic backdrop or adventure destination, not as living communities with political positions, economic strategies, and cultural protocols. Writing about them with care and context can redirect travelers and resources away from the Galápagos-Cotopaxi-Baños circuit and toward communities that have built tourism infrastructure on their own terms. That matters.
The argument for withholding is equally real. Every published guide to an under-visited community changes that community’s visitor profile. Sometimes that change brings revenue and political visibility. Sometimes it brings exactly the kind of visitor the community built its tourism model to avoid—the one who photographs without asking, who publishes GPS coordinates to a sacred site, who treats a backstrap loom as an Instagram prop. You cannot control who follows your guide. Only that your guide exists.
What I’ve landed on, after years of getting this wrong in both directions, is a practice of partial documentation. I write about the communities I visit in enough detail that a conscientious traveler can arrive informed—but I withhold the specific details that would make a place easy to consume without context. I publish bus routes and coordinator contacts. I don’t publish ceremonial site locations or medicinal plant preparations. I describe weaving traditions in terms of their cultural significance. I don’t publish pattern guides that would let someone reproduce the designs.
The question I keep returning to is the one Rosa implicitly asked me that day in 2022: what does it cost a community when a visitor takes without asking, publishes without context, and moves on without sending anything back? The answer, in her case, was nothing visible. No revenue. No new visitors who would buy her work. No broader awareness of Saraguro weaving traditions. Just another photo in another feed, another extraction dressed up as appreciation.
Document differently. Ask first. Send the photos. Write the report in Spanish. Withhold what isn’t yours to share. And when in doubt, close the notebook and just sit with the person in front of you, present and unrecorded. That’s a form of documentation too—one that records nothing but respects everything.