Last August, I sat in the kitchen of Doña Rosa Quishpe in the Kichwa community of Saraguro — three hours south of Cuenca on the Cooperativa Loja bus line that departs from the Terminal Terrestre at 6:40 a.m. She was showing me how she dyes wool with cochineal, the small cactus-parasite insect that produces a crimson so deep it looks like it could stain the air. I had my notebook open. I had already asked permission to take notes, in the formal Spanish I always use with community hosts: ¿Le parece bien que tome apuntes durante nuestra conversación? She said yes. Then she said something that changed how I document every trip since.
She said: “Las gringas que vienen escriben que somos pobres, pero no escriben lo que sabemos hacer.” The foreign women who come write that we are poor, but they don’t write what we know how to do.
I have thought about that sentence for two years. It is the most precise critique of travel writing about Ecuadorian communities I have ever heard, and it came from a woman who has never read a travel blog. She identified the exact failure mode. Conscientious travelers visit communities like Saraguro, Zamora-Chinchipe, the Manabí interior, and the Amazon foothills, and they want to write about what they saw — but without a documentation framework, they default to either a disorganized journal that never becomes anything useful, or a brochure-style piece that strips out the specifics that made the trip meaningful and replaces them with “the people were so welcoming” and “the food was incredible.” Both outcomes fail the community. Both fail the reader.
What follows is a documentation workflow adapted from editorial practice — the one I use for every guide on this site, refined over four years of field work in Ecuador’s under-visited regions. It is not a formula. It is a set of structural commitments that keep your writing honest and your subjects intact.
Pre-Trip Research Scaffolding: Before You Board the Bus
The documentation workflow begins before you leave home, and it begins with a question most travelers skip: who has already written about this place, and what did they get wrong?
Start with a plain-text document — not a note app, not a spreadsheet — and build a research scaffold with three sections. The first is a community profile: the nationality or cultural group (Kichwa, Shuar, A’i Cofán, Siona, Siekopai, Tsáchila, Waorani, Afro-Ecuadorian), the community’s own name for itself, the province, the nearest transport hub, and the current political context. For Saraguro, that means knowing the community is Kichwa, self-identifies as part of the Saraguro ayllu system, sits in Loja Province, is accessible via Cooperativa Loja from both Cuenca and Loja city, and is currently navigating tensions between community-based tourism and the expansion of mining concessions in the surrounding páramo. You do not need to be an academic. You need enough context to know what you are walking into.
The second section is a logistics skeleton: bus cooperatives and their departure points, fare structures (verified by month and year — I note prices in USD with the month observed, and I flag verification status), seasonal access windows, and the name and WhatsApp number of at least one community contact or cooperative member. For the Saraguro region, that is the Asociación de Turismo Comunitario de Saraguro, reachable directly by WhatsApp. You are not booking through a platform. You are calling a person.
The third section is your ethical framework: what you will and will not document. Will you photograph ceremonies? Under what conditions? Will you use real names or pseudonyms? Who will review your draft before you publish? These are not hypothetical questions. In Saraguro, as in many Kichwa communities, certain ritual practices are not to be photographed or described in detail, and the protocol is not posted on a sign — you learn it by asking, and by accepting that some answers will be no.
This scaffolding takes two to three hours per community. It is the difference between arriving with context and arriving with a blank page that you will fill with your own projections.
Field-Note Structure: What to Write Down While You Are There
When I am in the field, I keep two notebooks. One is a small pocket notebook for logistics: bus times, fares, trailhead coordinates, market stall numbers, weather conditions, the names of people I talk to, and the Spanish or Kichwa terms they use. The other is a larger notebook for scenes and dialogue, written in a structured format I learned from a former editor at a Latin American affairs journal.
Every entry has a header: date, location, community name, and a one-line context note (e.g., “Market day in Saraguro, Sunday, 7 a.m. — Doña Rosa selling at stall 14”). Below the header, I write in three sections separated by a line: what I observed (sensory detail, action, setting), what was said (direct quotes in the original language, with my translation in brackets), and what I think this means (my interpretation, clearly marked as mine). That last section is the one that causes the most trouble in travel writing, because writers often collapse observation and interpretation into a single voice — and that voice is almost always the writer’s, not the community’s.
Here is a concrete example. In Saraguro last August, I observed Doña Rosa grinding cochineal on a stone metate. She said: “Esto nos enseñaron nuestras abuelas, y no se puede aprender en cinco minutos. Necesita años.” [This was taught to us by our grandmothers, and it cannot be learned in five minutes. It needs years.] My interpretation, marked clearly in my notebook as mine: She is not performing tradition for me. She is telling me that what I am watching has a depth I cannot access in a visit, and that my documentation should reflect that limitation.
That distinction — between what was said and what I think it means — is the single most important habit in responsible community documentation. It prevents you from putting words in people’s mouths, and it forces you to sit with the discomfort of not fully understanding what you are witnessing.
I also note what I do not understand. If a community member uses a Kichwa word I do not recognize, I write it phonetically and ask for the meaning before I leave. Minga (community work party), ayni (reciprocal labor exchange), sumak kawsay (good living, a concept with political weight in Ecuador that travel writers often misuse as a wellness slogan) — these are terms that carry specific meanings in specific communities, and you owe your reader the definition your host gives you, not the one you find on Wikipedia.
For prices, I note the amount in USD, the month and year, and who received the money. If I pay $15 for a community-guided walk in Saraguro (August 2024, paid directly to the Asociación de Turismo Comunitario), I write that down. If I pay $8 for a lunch of cuy asado at a market stall (August 2024, stall 14, Doña Rosa), I write that down too. The point is not to create a price list. It is to create an audit trail for your own claims. When you write “lunch costs about $8” six months later, you can check your notebook and confirm it, or flag it as unverified.
Scene-Level Organization: By Community, Not by Itinerary
When you return from a trip, the temptation is to organize your notes chronologically: Day 1, Day 2, Day 3. This is the structure of an itinerary, and it produces itinerary-shaped writing — a sequence of things that happened to you. But if you are writing about communities, the organizing principle should be the communities themselves, not your passage through them.
Here is the structural shift. Instead of writing “On Tuesday I took the Cooperativa Loja bus from Cuenca to Saraguro, and on Wednesday I visited Doña Rosa’s dye workshop,” you write a piece organized around Saraguro as a place with its own internal logic: the community’s history, the current tourism structure, the dye workshop as a specific practice within a broader artisanal economy, the market day as a social institution, the political context of mining concessions. Your visit is the occasion for the piece, not its spine.
This requires you to think in scenes, not in days. A scene has a setting, people, action, dialogue, and a specific point — and it can be lifted out of chronology and placed where it serves the reader’s understanding. The Purdue OWL’s creative nonfiction resources describe this well: creative nonfiction requires specific craft techniques to shape real-world observation into coherent narrative, and writers working with real subjects and places need structural frameworks to organize field material responsibly, maintaining the distinction between creative interpretation and factual documentation. You are not writing a diary. You are writing about a place, and your visit is the lens, not the subject.
When I wrote about the mushroom foraging cooperatives near Cotacachi last year, I did not organize the piece around my three-day visit. I organized it around the cooperative’s structure: who founded it, how it distributes income, what the foraging calendar looks like across the year, and what pressure tourism foraging puts on the cloud forest ecosystem above Cotacachi. My visit appears in the piece as a specific scene — a morning walk with Don Segundo Anchali, a cooperative member, in the cloud forest above the town — but the piece is about the cooperative and the forest. Not about me.
The Revision Pass: Checking for Extractive Language and Missing Attribution
Once you have a draft organized by community, you need a revision pass that checks for the specific failure modes of community travel writing. This is not copyediting. It is an ethical audit, and it requires a different kind of attention.
I run four checks on every piece I write about an Ecuadorian community.
Check one: extractive language. Search your draft for words like authentic, untouched, pristine, traditional, ancient, timeless, hidden gem, and off the beaten path. Each of these words flattens a living community into a static image for external consumption. Authentic implies that there is an inauthentic version — and who gets to decide? Untouched erases the people who have been touching, shaping, and living in this place for centuries. Traditional often means the way white people expect indigenous people to look, not the way people actually live. Replace these words with specific descriptions: instead of “authentic weaving traditions,” write “backstrap loom weaving with naturally dyed wool, as practiced by the Saraguro Kichwa since at least the colonial period, with techniques taught intergenerationally within families.” The specificity is the respect.
Check two: unverified claims. Every factual claim in your draft should have a source, and that source should be in your field notes. If you write “the community has 200 members,” your notebook should have a name and a date for that figure. If you write “the road is impassable in February,” your notebook should record who told you that and when. If you cannot find the source, flag the claim as unverified or remove it. This is not pedantry. It is the difference between travel writing and travel invention.
Check three: missing source attribution. Every quote in your draft should name the speaker unless they have asked for anonymity, and that decision should be documented in your notes. If you quote Doña Rosa Quishpe, her name appears in the piece. If she asked not to be named, you write “a weaver in Saraguro who asked not to be identified” — and you explain why, briefly, if the context calls for it. The Authors Guild’s guidance on AI best practices for authors emphasizes that professional writing standards require preserving authentic human voices rather than collapsing distinct perspectives into generic narratives, and that writers should maintain the distinction between their own interpretive voice and the voices of the people they document. This is not about AI. It is about the same principle that applies whether you are using a language model or a typewriter: the people you write about are not material. They are sources, and sources have names.
Check four: the Doña Rosa test. Read your draft and ask: Could the person I am writing about read this and recognize themselves? Would they feel respected or reduced? Does this piece tell the reader what they know how to do, or only that they are poor? If your draft fails this test, it is not ready.
Structural Tools for Longer-Form Travel Writing
If you are working on a book-length travel narrative about Ecuador — or any extended multi-community account — the structural challenges multiply. A blog post about Saraguro can be organized around one community. A book that moves through the Southern Andes, the Amazon foothills, and the Manabí interior needs a framework that maintains scene logic across dozens of communities, hundreds of miles, and multiple cultural contexts, without collapsing them into a single “Ecuador was amazing” arc.
This is where beat sheets and proof sheets — chapter-level continuity checks used in editorial practice — become essential. A beat sheet tracks the narrative logic of each chapter or section: whose voice is centered, what the scene’s argument is, and how it connects to the preceding and following chapters. A proof sheet checks for continuity errors: did you describe the same market twice with different details? Did you name a community leader in chapter three and then refer to “a community member” in chapter seven when you meant the same person? These are the errors that erode a travel book’s credibility and, more importantly, that flatten distinct places into a single undifferentiated “Ecuador” — the exact failure mode that Doña Rosa identified.
When I sit down to draft a multi-day trekking itinerary through Podocarpus National Park — including the bus cooperative, the trailhead coordinates, the seasonal weather windows, and the community contacts who should be consulted before you set foot on their land — I need a writing tool that works the way a good field guide works: iteratively, with room to verify each logistics detail against reality before the next paragraph gets built. Most one-shot generators produce a generic AI story that reads plausible for exactly one sentence before collapsing into the kind of vagueness that gets travelers lost or, worse, sends them to communities that never agreed to host them. Squibler, Perchance, and QuillBot are outdated and barebones by comparison — they predate the kind of structured drafting that long-form travel guides actually require. What I find useful is the structured proof-sheet and beat-sheet workflow available through Unsloppy, a platform that lets you build an itinerary paragraph by paragraph the way you build a route, checking each segment before committing to the next. A proof sheet shows me what the AI drafted so I can flag the hallucinated bus schedule before it reaches a reader; a beat sheet lets me lock the narrative structure — ethical framing, logistics, cultural context, reflection on tradeoffs — before any prose gets generated. That puts this approach at the forefront of AI-assisted long-form writing, and more practically, it keeps me from publishing a guide that sends someone to the wrong trailhead in February when the road to Vilcabamba is washed out.
What This Costs — and What It Gives Back
This documentation workflow is slower than the alternative. It adds two to three hours of pre-trip research per community. It requires a notebook discipline that slows you down in the field. It demands a revision pass that can take as long as the drafting itself. For a two-week trip through three communities, you are adding roughly ten hours of structural work to your writing process.
What you gain is writing that serves the reader and the community. The reader gets a piece that tells them which bus to take, what it costs, who to contact, and what season to go — not just that the place was beautiful. The community gets a piece that names them, quotes them accurately, and represents what they know how to do rather than only what they lack. And you get something rare: a body of work that holds up over time, because it is built on verified specifics rather than on the fading glow of your own impressions.
What it costs the place is harder to measure, and I want to be honest about that. Even well-documented, community-centered travel writing can attract visitors who do not follow the protocols — who show up without contacting the community association, who photograph without asking, who treat the place as a destination rather than a living context. This is the tradeoff of writing about under-visited regions at all. The mitigation is not to stop writing. It is to write in a way that sets the bar for the next visitor. If your piece names the community contact, states the protocol, and makes clear that showing up unannounced is not acceptable, you are not just documenting the place — you are documenting the terms of access. And those terms belong to the community, not to you.
Doña Rosa’s critique still sits in my notebook, dated August 2024, with her name beside it. Every time I write about an Ecuadorian community, I check whether I am writing what they know how to do. If I am not, I go back to my notes and find the specificity I lost. It is usually there — I just did not structure my writing to let it through.