How Community Organizations Can Build Writing Capacity Without Hiring a Comms Team

At a community centre in Widnes last spring, a session I was observing ground to a halt. Twelve residents had spent ninety minutes carefully working through concerns about a proposed housing development on former industrial land — drainage, traffic, what would happen to the informal play area their children had used for fifteen years. The facilitator closed the session, thanked everyone, and then a volunteer coordinator turned to me and said, almost as an afterthought: “Now someone has to write this up for the council by Friday, and I’ve got a full day of outreach tomorrow.”

That sentence captures something I have been trying to name for several years in community development work across Northwest England. The writing — the documentation, the narrative production, the translation of a two-hour conversation into something a planning officer or a funder can read — is almost always the bottleneck. Not because community workers cannot write. Most of them write extremely well when they have time. The problem is that writing capacity is treated as a free byproduct of organizing rather than as a distinct, demanding, and structurally underfunded form of labour. This piece is about that gap, and about what organizations can actually do about it without pretending a communications team is about to materialize from the core funding they do not have.

What We Are Actually Being Asked to Produce

The volume of written material a small community organization is now expected to generate has grown substantially over the past decade, and the trend has accelerated with devolution. In Greater Manchester, the combined authority’s consultation frameworks increasingly require structured written submissions from community groups that want to influence transport planning, housing strategy, or environmental policy. In Liverpool City Region, social value reporting requirements attached to procurement contracts ask community organizations to articulate their impact in language that mirrors corporate reporting — outcome frameworks, theory of change narratives, case studies with attributable metrics. In Lancashire and Cumbria, parish councils and community partnerships responding to neighbourhood planning exercises must produce consultation summaries that meet specific procedural standards to carry weight in planning decisions.

Layer on top of that the routine demands: funding applications, annual reports, safeguarding policies, board minutes, social media posts, newsletter articles, partnership bid narratives, Section 106 monitoring reports, and the increasingly common request to produce “lived experience” case studies for conferences, policy briefings, and academic research collaborations. Each of these has its own conventions, its own audience expectations, its own deadline structure. None of them, individually, looks unreasonable. Together, they constitute a writing workload that no organization with fewer than ten staff can sustain without either burning someone out or letting the quality slip in ways that have real consequences.

The Brookings Institution has documented how civic capacity — the organizational and communicative infrastructure that lets communities participate in governance — is unevenly distributed and frequently erodes precisely where it is most needed. Their work on how protest translates into policy change emphasizes that sustained organizational capacity, including the capacity to articulate and document community concerns in formats institutions recognize, is what separates mobilization that fades from organizing that lasts. This matters in Northwest England because devolution has shifted decision-making closer to home, but it has also raised the documentation threshold. A community group in Bolton that once might have sent a letter to their MP now needs to produce a structured response to a combined authority consultation, formatted correctly, submitted through a portal, with supporting evidence attached. The infrastructure for doing that — training, templates, staff time, editorial support — has not followed the new demands.

The Structural Problem: Writing as Invisible Labour

Here is what I see repeatedly, in organizations I work with and in research I have conducted with community workers across the region: writing falls to whoever is closest to the work, whoever is most articulate, whoever is least likely to say no. In practice, that means it falls disproportionately to women, to younger staff, to people of colour, and to workers whose contracts do not include “communications” in their job description but who are assumed to be “good with words.” It falls to the person who ran the session, which means the person who was managing group dynamics, watching for who was getting upset, making sure the interpreter had breaks, and tracking the logistics — and who is now expected to also produce a clean, well-structured narrative account of what happened.

This is invisible labour in the most literal sense. It does not appear in job descriptions. It is rarely costed into funding bids. It almost never shows up in work plans or supervision meetings unless someone is already struggling. And it carries a specific ethical weight in community settings, because the writing is not neutral transcription. When you write up a community conversation, you are making decisions about what to include, what to omit, how to represent disagreement, whose voice to foreground, how to characterize uncertainty. These are editorial decisions with political consequences, and they are being made by exhausted workers at the end of long days, often the morning before a deadline, with no editorial support and no time for the community to review what has been written in their name.

I want to be precise about what this means in practice. A community development worker in St Helens told me recently that she spends roughly one day a week — twenty percent of her contracted hours — writing reports for three different funders, each with different formatting requirements, different outcome frameworks, and different definitions of what counts as evidence. None of those funders fund her writing time. She told me she writes faster now than she used to, and that she has stopped including things she is not sure how to frame — concerns raised by residents that do not fit neatly into outcome categories, moments of tension in a session, things she observed but cannot quite articulate in the language the funder expects. She is not lazy or unskilled. She is making rational decisions under structural pressure, and those decisions shape what funders actually learn about the work they are paying for.

Documentation Versus Storytelling: A Practical Distinction

One of the most useful moves I have seen organizations make is to separate documentation from storytelling — to treat them as different tasks with different purposes, different audiences, and different standards. This sounds simple, but it requires deliberate organizational discipline, because funders and partners routinely conflate the two and ask for both in a single document.

Documentation is the record of what happened: who attended, what was discussed, what decisions were made, what concerns were raised, what follow-up is needed. It should be factual, structured, and useful to the organization itself as well as to external readers. It does not need to be eloquent. It needs to be accurate and complete. Good documentation can be written quickly, in plain language, using a consistent template, by the person who facilitated the session — and it can be reviewed by participants for accuracy before it is finalized.

Storytelling is the narrative construction of meaning: why this work matters, what it reveals about a community’s priorities, how it connects to broader patterns, what it asks of a reader. It requires craft, editorial time, and a clear sense of audience. It is not something that should be produced under deadline pressure by someone who is also running the program being described. And it should never be produced without the explicit consent and review of the community members whose experiences are being narrated.

When funders ask for “case studies,” they are usually asking for storytelling dressed up as documentation. When they ask for “consultation summaries,” they are usually asking for documentation that reads like storytelling. The ambiguity is not accidental — it reflects a genuine tension in what institutions want from community organizations: they want both the authority of factual reporting and the emotional pull of narrative, and they want it in two thousand words by the end of the month. Naming this distinction, internally, lets organizations push back more precisely: “We can give you a documentation summary within a week. If you want a published case study, that is a different piece of work, it needs different time and different consent processes, and we need to discuss whether it is the right use of our capacity right now.”

A Framework for Deciding What to Write, Who Should Write It, and How

I want to offer something concrete, because the readers of this site do not need another article that describes a problem without offering a way through it. What follows is a decision framework I have developed with community organizations in the region and tested across about fifteen different settings over the past two years. It is not a formula. It is a set of questions that organizations can ask themselves — ideally together, in a staff meeting or a board discussion — to make writing decisions more deliberate and less driven by whoever sent the most recent email.

Question one: What is this document for, and who actually reads it? Before writing anything, establish whether the document serves a regulatory requirement, a funder relationship, a community accountability function, a campaign objective, or an organizational learning purpose. These are different audiences with different needs, and writing for all of them simultaneously produces documents that serve none of them well. A report written for a funder’s monitoring framework is not a community accountability document, and pretending it is erodes trust. If the real answer is “the funder requires it and nobody may read it carefully,” that should change how much time you invest.

Question two: Does this need to be written at all, or does it need to be written now? Not every piece of community work needs to be documented in narrative form. Some work is better served by a structured log, a set of attendance records, a photograph with a caption, or a brief bullet-point summary that the community can review and approve. The pressure to narrativize every interaction — to turn every conversation into a story, every session into a case study — is driven by funder expectations, not by community need. Ask whether the narrative form serves the community or the institution requesting it. If the answer is the institution, that is legitimate, but it should be named as institutional reporting, not community voice.

Question three: Who should write it, and what time do they need? Writing should be assigned, not assumed. The person who facilitated a session is often the worst person to write it up objectively, because they are too close to the dynamics and too invested in how the session went. They are also usually the most tired. If possible, have someone else document — a co-facilitator, a volunteer with note-taking skills, a staff member who was not in the room. Build in time for the community to review what has been written before it goes anywhere external. If the writing requires craft — a campaign briefing, a published case study, a consultation response that needs to be persuasive — assign it to someone with the skills and give them protected time, not the end of a fifteen-hour day.

Question four: What format serves the purpose without overproducing? Match the format to the function. A consultation summary for a planning department does not need to be a beautifully designed PDF. It needs to be clearly structured, easy to navigate, and procedurally compliant. A case study for a funder’s annual report may benefit from narrative craft but does not need to be a magazine feature. A campaign briefing for elected members should be short, direct, and focused on the decision you want them to make. Overproduction — spending hours formatting something that only needs to be clear — is a sign that the writing task has not been properly scoped.

Question five: Does the community whose experience is being described know, consent, and have the chance to correct? This is the most important question and the one most frequently skipped. If you are writing about a community conversation, the people in that conversation should know what you are writing, why you are writing it, where it will go, and what it will be used for. They should have the chance to review drafts, correct errors, and withdraw contributions if they choose. This is not a bureaucratic step. It is the difference between documentation and extraction. The Authors Guild’s guidance on AI and authorship practices makes a parallel point about writing labour more broadly: when human voice, judgment, and lived experience are treated as raw material to be processed without credit or compensation, the result is not just ethically compromised — it produces worse writing, because the people closest to the experience have been cut out of the interpretation.

Tools, Templates, and the Limits of Technology

Organizations need practical writing infrastructure: templates for common documents, style guides that keep voice consistent across staff changes, shared drives where documentation is stored and searchable, and editorial processes that do not depend on a single person’s institutional memory. These are boring, administrative investments, and they are exactly the kind of thing that does not get funded because it is not a program. But they are what make writing sustainable. An organization that has a well-designed consultation summary template, tested across several uses and refined with community input, can produce documentation in a fraction of the time it takes an organization starting from scratch each time.

Some organizations are now experimenting with AI tools to support parts of the writing process — drafting boilerplate sections, formatting structured data into prose, generating first-pass summaries from notes. This is worth engaging with seriously, not dismissively, because the pressure on writing capacity is real and the tools exist. Using an AI script writer or similar drafting tool can be genuinely useful for producing a first pass of a routine document — a monitoring report with standard sections, a consultation summary structured against a known template — where the human writer’s job shifts from generating prose from nothing to editing, correcting, and sharpening a draft. The key is treating these tools as drafting aids, not as authors. Community narrative is not generic content. It carries specific voices, specific histories, specific political stakes, and it requires human judgment at every stage. The moment a tool becomes a substitute for the relational work of listening, interpreting, and checking back with people, it has been misused — and the writing it produces will be recognizable to anyone who reads community work with care as hollow, flattened, and wrong.

The risk, as the Authors Guild has noted in its guidance on AI use for writers, is that quality human writing becomes a luxury good — something only organizations with dedicated communications staff can produce. In the community sector, that would mean that small, grassroots organizations serving the communities with the least structural power are systematically disadvantaged in their ability to articulate their own work, while larger organizations with professional infrastructure shape the narrative landscape. That is not a technology problem. It is a capacity problem, and tools can help or worsen it depending on how they are deployed.

What Funders and Commissioners Should Do Differently

Most of this piece has been addressed to community organizations themselves, because that is where the readers of this site are working. But the structural problem is not going to be solved by organizations becoming more efficient at producing documents under pressure. Funders, commissioners, and local authorities need to change what they ask for and how they ask for it.

First, cost writing time into every grant. If a funder requires quarterly reports, case studies, and a year-end narrative, the budget should include paid hours for the person who produces them — not as overhead, not as a hidden tax on program staff, but as a visible, costed line item that acknowledges writing as labour. Second, accept structured documentation in place of narrative where the purpose is monitoring rather than communication. A well-designed reporting template that asks for specific, scannable information — attendance, activities, outputs, concerns raised, follow-up actions — is more useful to both parties than a prose narrative that someone has stayed late to produce and nobody has time to read. Third, stop asking for case studies as a default reporting requirement. Case studies involve real people, require consent processes, and carry editorial weight. They should be commissioned as specific pieces of work with appropriate time and compensation, not demanded as a standard attachment to a monitoring report. Fourth, align reporting cycles with community rhythms, not financial years. The expectation that community work produces clean outcomes on a quarterly cycle is a fiction that distorts practice and produces reports full of hedged language and selective framing. Funders who genuinely want to learn from the work they fund should accept that community timelines do not map neatly onto accounting periods.