Document or Disappear: Why West African Civil Society Can No Longer Afford to Skip Knowledge Products

Carmelle Hountondji, former Project Officer, CKLE

Across West Africa, thousands of organisations do remarkable work that almost nobody hears about. They are not short of impact. They are short of a written record. The consequences are practical. An organisation that does not document its work leaves others to tell its story or lets that story disappear. It misses funding it could have won. Its lessons leave with every staff member who moves on. And it struggles to convince communities, governments and donors that it deserves their trust. At the centre of this problem is an idea that is still poorly understood: the knowledge product.

A knowledge product is more than an annual report

The term usually brings the annual report to mind, and often nothing else. In fact, it covers much more, including:

• case studies and stories of change, which set out an intervention in detail, with its context, results and limitations;
• market and context studies, which make the case for a programme and inform strategic choices;
• guides and procedures manuals, which record how an organisation works and protect that know-how when staff leave;
• policy briefs, advocacy notes and op-eds, which turn field experience into proposals for decision makers;
• progress reports and end-of-project reviews, which take stock of what was done, achieved or missed;
• internal memos, meeting notes and learning briefs, often overlooked, even though every other product is built from them;
• audio and video content (testimonial videos, podcasts), increasingly important for reaching audiences who read little.

In short, a knowledge product is any document that shows the outside world the value of an organisation's work. It does two jobs at once: it preserves what the organisation has learned, and it proves what the organisation has achieved. Its value also reaches beyond the organisation that produces it, because published lessons save others from repeating the same mistakes.

I saw what this looks like in practice over a year leading CKLE’s support to VJCA, a legal-education NGO in Togo whose radio programme reaches rural communities. Its work was real and valuable, but every episode vanished once it aired: nothing could be shared, found again or counted. Turning that work into lasting knowledge products, from podcasts and blog articles to progress reports and a website with analytics, is what finally gave VJCA something to show partners, donors and its own team. That experience, described in detail below, shapes everything in this piece.

Why so many organisations fall short

If these documents are so valuable, why are they so often missing? In my work with civil society organisations at CKLE, the same barriers came up again and again.

1. Not seeing the strategic value of documentation.

Many organisations still treat the annual report as paperwork, produced because a donor asked for it, rather than as a way to position themselves. Yet it is often this very document that lets an organisation move up a level: from informal association to recognised partner, from small grants to its first institutional funding, from working alone to joining a consortium or being invited to a national consultation. Donors, networks and public institutions are looking for evidence. Without a written record, there is nothing to show when those opportunities arrive, and they rarely give advance notice.

2. Lack of time.

This is the most common barrier, and it is real. Even when documentation is recognised as important, it loses out to whatever is urgent: the activity that has to happen, the financial report that is due, the community crisis that needs handling, the funding application due tomorrow. In small organisations, the same few people do everything. Documentation becomes something to do later, which in practice means never. When it finally happens, it is rushed and pieced together from patchy memories.

3. Lack of in-house skills.

A strong knowledge product calls for several skills: clear writing, data analysis, a well-structured argument, good design and a tone suited to each audience. Few grassroots organisations have these skills on staff. Consultants and designers are expensive, and grants rarely include a budget line for documentation. As a result, the organisations closest to communities, which often have the most powerful stories, are the least able to tell them.

4. Technical dependency.

Many organisations that have gone digital still rely on an outside contractor to update a website, publish content or pull analytics. When the contract ends or the contractor moves on, everything stops. A website that is never updated quickly looks abandoned, and it does the organisation more harm than good.

5. Fear of showing what did not work.

Many organisations would rather publish nothing than share mixed results, for fear of putting partners off. That is a miscalculation. Experienced donors know every project hits obstacles. What worries them is an organisation that cannot analyse its own setbacks.

6. Language and format.

West African organisations work across French, English, Portuguese and dozens of local languages. A report in one language reaches only some of its potential partners, and a dense 40-page document will be read neither by a busy policymaker nor by a community member. Publishing in both French and English, let alone in local languages or in shorter formats, is still the exception rather than the rule.

Time, quality and process: what allows an organisation to grow

In project management, three things determine whether an organisation can grow: time, the quality of its services and outputs, and knowledge of its own processes and procedures. Each depends on the others. Without documented processes, an organisation wastes time reinventing them. Without time, quality suffers. And poor-quality documents convince no one.

An organisation that is growing and wants to keep growing must therefore be able to document its procedures, successes and challenges quickly and without cutting corners on quality. This is a management issue, not only a communications one.

The case is even stronger for civil society organisations. They work under heavy pressure: funding is more competitive and more tied to results, skilled staff are hard to keep on modest salaries, social problems must be tackled daily with limited means, and in several countries civic space is shrinking. Each departure takes part of the organisation's memory with it if nothing was written down. Each new donor asks for evidence that then has to be produced in a rush. For civil society organisations, documentation is not a luxury. It is a condition for survival, and sometimes for self-defence. Where civic space is under pressure, well-documented facts are also an advocacy tool.

One tool can change this picture: technology. It does not replace fieldwork or careful thinking. But it greatly reduces the time and cost of turning that work into knowledge and of sharing that knowledge widely. The experience of VJCA in Togo shows both what technology makes possible and what it takes for the results to last.

Case study: VJCA, from radio to digital

VJCA (Vulgarisation Juridique et Citoyenneté Active, or Legal Education and Active Citizenship; www.vjca.net) is an NGO based in Lomé, Togo. It works to make Togolese law accessible, understandable and useful to everyone, especially rural communities that live far from the justice system. Its work includes radio programmes in local languages, plain-language legal fact sheets, community legal clubs, legal caravans to remote villages and training for community liaison volunteers, in support of SDGs 16, 5 and 10. Its flagship radio programme, La Parenthèse Juridique ("The Legal Aside"), explains the law in simple terms, but like all radio it disappeared once it aired, and it was hard to share, find again or measure. From July 2025 to July 2026, I led CKLE’s support to VJCA in building a coherent digital ecosystem around the programme. A foundation phase delivered a full brand identity, a written communications strategy with audience personas and indicators, Facebook and LinkedIn accounts, and the vjca.net website with analytics. A roll-out phase, guided by a scoping note with a SWOT analysis and measurable targets, launched the YouTube channel @laparenthesejuridique, turned recordings into podcasts, and added legal blog articles, reusable templates, social media visuals and regular progress reports.

The regular radio slot now lives on as content that can be found, shared and replayed at any time, and its reach can finally be measured. Over the period, social media content had approximately 10,000 impressions and around 770 engagements. The brand, website, channels and documentation are solid and built to last, but audience growth stalled because content production depended on source recordings that arrived irregularly. The lessons I draw from it are clear: identify production bottlenecks early and plan a fallback, keep a buffer of ready-made content, choose a pace that can be sustained over targets that are missed, define every indicator precisely, and invest first in the best-performing channel. VJCA has gone from an idea for an organisation to an organisation with real digital assets on which an engaged community can now be built, and this frank review is part of those assets.

Ten practical tips for producing knowledge products

My experience with VJCA, and CKLE’s wider work with civil society organisations, points to ten practical tips for civil society organisations, especially community-based and grassroots groups, that want documentation to become second nature.

1. Document as you go, not at the end of the year

Most annual reports are written in December, from memory, against a deadline. That is a recipe for a thin report. A simple routine changes this:

• a shared folder (Google Drive, OneDrive or a dedicated WhatsApp group) with one subfolder per month;
• after every activity, three things go into it: 3–5 photos, the attendance list and a five-line summary (what, where, who, how many participants, what result);
• at the end of each quarter, one hour to review those summaries and note the highlights.

By December, most of the report is already written, and all that remains is to put it together.

2. Appoint a lead and protect the time

When everyone is responsible, no one is. Appoint a documentation focal person: not necessarily a communications officer, but someone organised and curious. Block out two fixed hours a week in the team calendar, like any other meeting. A five-minute documentation slot in team meetings also helps: what was done, what was learned, what was recorded?

3. Choose indicators before starting

Impact that is not measured cannot be proven. Each project should set 3–5 key indicators, recorded in a simple table with:

a precise definition (for example, "number of women who attended at least two sessions");

• a source (attendance sheet, Facebook analytics, survey);
• a collection schedule (every activity, every month);
• a named person responsible.

Vague indicators produce inconsistent figures, and donors spot them quickly. Clear indicators, by contrast, make it possible to adjust course along the way.

4. Get several pieces of content out of every activity

VJCA's experience shows how a single radio programme can become a podcast, a blog post, three social media posts, a WhatsApp message and a feature box in the annual report. Apply the "one piece of content, five uses" principle at the planning stage. Before every workshop, training or outreach caravan, ask: which photos should be taken, which quote should be captured, which figure should be recorded, and for which channels? Output goes up, with no extra effort in the field.

5. Build a buffer and map the bottlenecks

A reserve of two to four weeks of ready-to-publish content protects against late data, photos or recordings, staff absences and emergencies. At the start of every project, identify who or what production depends on. If a partner must supply materials, a written delivery schedule agreed by both sides prevents gaps.

6. Train the team so it does not depend on a contractor

A tool is only worth something if the team can keep it running after the contractor leaves. Any technical support (website, social media, database) should include:

• hands-on training for at least two staff members, so the know-how does not rest with one person;
• a simple user guide written in the team's working language;
• handover of all access (passwords, accounts, hosting) to the organisation, not just the contractor;
• a mentoring period during which the team publishes on its own, with support on hand.

Digital security matters too: regular backups, strong passwords and two-factor authentication. Documentation that is lost or hacked is of no use to anyone.

7. Start small, but start

A published 8-page annual report is worth more than a 40-page report that is never finished. For an organisation producing its first report, a realistic progression is:

first, a two-page fact sheet: who the organisation is, what it did, key figures, one story, partners;

the following year, a short report of 8–12 pages;

then, step by step, case stories, guides and advocacy briefs drawn from practice.

Consistency builds credibility far more than volume does.

8. Share what did not work, and put faces to the figures

Serious donors place more trust in organisations that examine their own shortfalls. Every report benefits from a "Lessons learned" section built around three questions: what worked, what did not and why, and what will change? This signals maturity, not weakness.

Figures persuade, but stories stick. The case story format, common across the development sector, is a good model: a starting situation, an intervention, a change, and the voice of someone affected. A few rules:

• always obtain written consent to use a testimony or photo;
• respect people's dignity and avoid images that portray them only as victims;
• anonymise when the subject is sensitive, particularly legal matters or violence;
• tell the story before, during and after.

9. Use free tools built for civil society

A professional annual report does not require a designer or a consultant. CKLE built the NGO Annual Report Builder (report.ckle.org) to address the barriers described above: time, skills and cost. It is a free, bilingual (English/French) tool for African NGOs, associations and civil society organisations, especially in francophone West Africa. In practice, the tool:

• guides users section by section (director's message, activities, impact figures, success stories, finances, partners) with simple prompts, so no one has to start from a blank page;
• offers AI writing assistance to draft and polish text, which makes up for the lack of specialist writers;
• saves work automatically, so teams can make progress in short sessions between field activities;
• exports a print-ready PDF in one of two professional layouts, with no design costs.

For a community-based organisation or a neighbourhood association, this means a team of two or three people can produce a credible annual report in a few days, ready to share with a donor, local government, a network or a technical partner. The bilingual interface also makes it easier to produce an English or French version for partners across the region and beyond.

Suggested approach:

• Gather the material: the monthly folder contents (tip 1), indicators (tip 3), one or two stories (tip 8) and approved financial figures.
• Set aside two half-days with a small team.
• Work through the tool section by section, using the writing assistant to sharpen the text while keeping the organisation's voice and facts.
• Get an outside reader to review it, such as a board member or trusted partner.
• Export the PDF and move straight on to distribution (tip 10).
• AI can help with the writing, but it cannot replace the data: check every figure and every name before exporting.

10. Share it widely, then reuse it

A report that sits on a hard drive helps no one. Plan distribution while the report is being written:

• publish it on the organisation's website or Facebook page;
• send it personally to partners, donors, local authorities and networks, with a short cover note;
• turn it into 3–5 social media posts (key figures, a story, thank-yous);
• present it at the annual general meeting and to communities, in the languages they speak;
• attach it to every funding application that year;
• share it with regional civil society networks and platforms, which multiply its reach.
• Finally, reuse it: its content can feed concept notes, presentations and proposals. A good knowledge product keeps paying off for years.

Conclusion: taking back the narrative

Documentation is not about filling in forms. It is about owning the story. At a time of shrinking funding, growing competition among organisations, narrowing civic space in several countries and trust that has to be earned, the civil society organisations that can show what they do, and what they learn from it, are the ones that will endure.

West African civil society has powerful stories to tell: rights explained in rural villages, women gaining access to justice, young people stepping into public life, communities taking charge of their own development. These stories deserve to be written down, shared and passed on, in French and in English. The tools exist, and many are free. The skills can be learned. What remains is to make documentation a habit: one report, one case story, one learning brief at a time.

Carmelle Hountondji was a Project Officer at CKLE, a bilingual creative communications agency based in Cotonou, Benin, where she led the agency’s support to VJCA in Togo from 2025 to 2026.