assisted drafting, not automated writing

Bring up AI in a room full of development communicators and the mood shifts fast — and for good reason. This is a sector built on trust between storyteller and subject, where misrepresentation has real consequences for real communities, and “AI-generated” understandably sounds like a shortcut around the judgment that trust requires.

That skepticism deserves a straight answer, not a marketing dodge. So here it is: nothing about Storylines writes a story on someone’s behalf, invents details, or substitutes for a human’s understanding of what actually happened. What it does is smaller and, we think, more useful — helping a field officer who has real knowledge but isn’t a natural writer get from rough, honest notes to a clean, readable draft faster.

That’s a genuine gap in this sector. The people closest to the story — field staff, local partners, program officers — often have the most valuable material and the least time or writing confidence to shape it. The choice they’re usually left with is: write it themselves under deadline pressure, or hand it to someone further from the work who has to reconstruct context secondhand. Neither produces the best version of the story.

Assisted drafting sits in between. It takes rough notes — fragmented, conversational, exactly as captured in the field — and helps shape them into a coherent draft, preserving the specifics and the voice of whoever wrote them. The author reviews, corrects, and owns every word that ships. Nothing publishes without a human decision behind it.

We use the term “assisted drafting,” deliberately, instead of “AI-generated,” because it describes what actually happens: a tool helping a person write faster, not a system writing instead of them. The editorial judgment, the relationship with the community, the responsibility for accuracy — all of that stays exactly where it should, with the human who was there.

Faster doesn’t have to mean less careful. That’s the balance this is built around.