Community coverage reads like a press release when it repeats the organiser’s framing, uses only positive adjectives, and quotes nobody outside the people running the project. Fixing it means naming one concrete detail, including at least one person who was not in charge, and being willing to state plainly what did not work, since an account with no friction reads as an advertisement rather than a report.
It borrows the organisation’s own promotional adjectives — vibrant, dedicated, inspiring — instead of describing what was actually there to see. It repeats the mission statement rather than showing it in action, quotes only the organiser or founder, and tends to close with something closer to a call to donate or attend than a finding.
It happens for an understandable reason: the writer spoke to one person, the organiser, who naturally describes their own project in its best light, and the writer — wanting to be supportive of something worthwhile — leaves in language that reads as advertising because nobody involved noticed it was doing that.
Generic language and specific detail are easy to tell apart once you are looking for it. "A wonderful turnout" is generic. "Around fifteen of the forty chairs set out were filled" is specific, and it is also the more interesting sentence, because it tells the reader something they could not have guessed from the project’s own description of itself.
The same applies to quotes, sounds and small physical facts — what the room actually smelled like, what somebody said off the cuff rather than for the piece, the detail that would be cut from an official newsletter because it is too ordinary. Ordinary is usually what makes a piece feel true.
A count, a measurement or a time is checkable and specific in a way "wonderful", "amazing" and "inspiring" never are. Reach for the number before the adjective.
An organiser’s account is necessarily one-sided — they built the project and want it to continue, which is a completely reasonable position and also not a neutral one. A participant, a sceptical neighbour, or someone who stopped attending will complicate the picture, and that complication is usually where the honest version of the story is.
Talking to them last means their framing does not become the lens you see everything else through.
Someone who benefits from the project and someone who has no reason to promote it.
Disagreement between sources is often the most honest and most useful part of what you end up writing.
Every real project has a setback somewhere — a week with low turnout, a funding gap, a disagreement about direction that took months to settle. Naming it does not undermine the piece; it is what makes the parts that did go well believable, because a reader correctly discounts an account with zero friction in it as an advertisement rather than a report.
This does not mean manufacturing balance where none exists, or giving a genuine success story an artificial complaint to seem more objective. It means not editing out the setback that actually happened because it complicates a tidier version of events.
A leaflet, a website and a grant application are all written to make a case for the project, which is a legitimate purpose for them and a poor source of sentences for anyone reporting on it. Phrases like "empowering the next generation" or "building a stronger community" describe an intention, not an observed event, and lifting them into a piece quietly imports the organisation’s framing as if it were the writer’s own conclusion.
The fix is mechanical rather than a matter of style: write down only what you saw, heard or were told by name, and treat any phrase you recognise from the project’s own materials as a signal to go back and describe the thing itself instead.
No — it is the opposite. Omitting a setback you noticed yourself to keep the piece flattering is the dishonest choice. If the setback is something you observed or were told by someone involved, it belongs in an honest account of the project.
Rely more on direct observation and specific detail, and say plainly in the piece that it reflects one person’s account rather than presenting a single perspective as if it were consensus. One honestly limited source is better than a piece that hides how narrow its reporting was.
A review states an opinion openly, as an opinion. Coverage that reads like a press release hides an opinion — approval of the project — inside language that presents itself as neutral reporting. The habits above are about removing that disguise, not about being negative.
That is promotion, not reporting, so it does not belong inside the narrative. If it is genuinely useful to a reader, one plain factual line at the end — where and when the project meets — is enough, without folding a call to action into the story itself.