Your address will show here +12 34 56 78
Africa Training Hub, Funding Guides & Tools, Grants & Funding, News & insights

ATI analysis | 8 September 2026

Featured image: an illustrative meeting image from ATI’s media library; it does not depict the PMNCH survey or a named partner.

Funding cuts can leave an NGO with approved activities but too little money to deliver them safely. A new PMNCH update makes service continuity an urgent management question for African organisations working with women, children and adolescents.

What the September PMNCH survey reports

In its 6 September 2026 report, PMNCH says 69% of responding partner organisations had reduced, suspended or closed programmes. Respondents were based in 67 countries. These are findings from a global partner survey, not an estimate of the share of all African NGOs affected.

The report includes African experiences: a Sierra Leone organisation described pressure on disability-inclusive programming, while Plan International Zambia highlighted working through community organisations and government stakeholders. The examples show why managers should examine who loses access when resources shrink.

An ATI service-continuity checklist for African NGOs

The following practical framework is ATI’s analysis. It is intended for a joint review by programme, finance, safeguarding and monitoring staff, adapted to the organisation’s agreements and context.

1. Identify the service at risk

Replace a broad statement such as “the project faces a shortfall” with a specific service, location, affected group and interruption date. Distinguish activities that can be postponed from those where interruption could leave people without a safe referral or support route. Ask frontline partners to check the assumptions.

2. Build a realistic cash timeline

Separate confirmed receipts from pending proposals. List existing commitments and the dates on which decisions must be made. Prepare a continuation option, a reduced-scope option and an orderly handover option. Show the assumptions behind each; a prospective grant should not be treated as money already available.

3. Test the consequences of each option

For every proposed reduction, record who would be excluded, what alternative provision actually exists and who has confirmed it. A referral is not a solution until the receiving provider can accept people. Include transport, language and disability-access barriers in that check.

4. Agree changes before implementation

Record the proposed scope, responsibilities, revised milestones and approvals needed under the relevant agreement. Avoid transferring additional work to a local partner without discussing staffing and delivery costs. Where responsibilities change, revisit ATI’s partner due diligence resource to identify questions that need renewed assessment.

5. Keep a short decision record

Use one row per affected service: current commitment; confirmed resources; interruption risk; proposed action; responsible person; approval status; next review date. Add the evidence that would trigger a change of plan. This makes the discussion usable at the next management meeting rather than leaving it as a general concern.

Communicate what communities can rely on

Give service users a clear explanation of confirmed changes through channels they can access. State when further information will be available and how concerns can be raised. Avoid promising a restart date that depends on an unconfirmed award. Monitor missed referrals and complaints alongside expenditure so financial adjustments do not conceal delivery failures.

Strengthen the management behind programme continuity

Bring one affected service to your next programme review and complete the decision record together. For further professional development, review ATI’s Grants Management Training Workshop and assess its relevance to your responsibilities.

Source note: Survey findings and country examples are attributed to PMNCH. The checklist and decision-record format are ATI’s original practical analysis. This article is not a grant announcement.

0

Africa Training Hub, News & insights

Analysis | 7 September 2026

Featured image: illustrative logistics planning photograph from ATI’s media library; it does not depict the South Kordofan incident.

The South Kordofan aid truck attack highlights a difficult question for humanitarian managers: when supplies cannot reach their destination, how should a programme protect people, revise commitments and account for the gap?

In a statement published on 2 September 2026, the World Food Programme reported that an aerial attack struck two trucks outside Dilling on 30 August. The vehicles were carrying food to Kadugli and displayed WFP markings. WFP said more than 50 metric tons of food were destroyed, equivalent to one month of assistance for 5,800 people. Its statement did not identify the party responsible.

The lessons below are ATI’s programme-management analysis, not a description of WFP’s internal procedures or a substitute for an organisation’s security decisions. They focus on how NGO programme, logistics, finance and monitoring teams can work together when assistance is interrupted.

1. Measure the delivery gap, not just the cargo loss

A stock write-off records what has disappeared from the supply chain. It does not explain what households will miss. Programme teams should connect the lost consignment to the intended distribution cycle, the needs it was meant to meet and the assistance still available through other confirmed channels.

Keep planned, dispatched, received and distributed quantities separate. Goods leaving a warehouse should never automatically count as assistance received by a community. Where delivery cannot be verified, report that uncertainty explicitly. Avoid estimating affected households from tonnage unless the ration assumptions and household definitions are documented.

2. Make continuity decisions across functions

A transport interruption affects budgets, delivery dates, staff workload and expectations. Bring programme, logistics, finance, security and relevant local partners into one decision process. Establish who can approve a revised plan, what evidence they need and when the decision will be reviewed.

Possible programme adjustments require context-specific assessment. Replacing in-kind assistance with cash, for example, is not an automatic solution: teams need evidence about market supply, payment access, protection concerns and donor conditions. Operational movement decisions should remain with authorised personnel using current information.

3. Protect local partners from unfunded changes

A revised delivery plan can transfer extra storage, communication or staffing costs to partners. Before changing expectations, record which organisation will bear each additional cost and whether the agreement permits it. Discuss capacity honestly rather than assuming that local teams can absorb another delay.

ATI’s NGO partner due diligence checklist provides a starting point for reviewing organisational responsibilities. During an interruption, that review should lead to practical support and clear decisions, rather than additional paperwork alone.

4. Give communities an honest update

Communities need to know what has changed, which commitments remain uncertain and where to ask questions. Agree a consistent message with delivery partners and use accessible channels. Do not promise a replacement date before it has been approved and confirmed.

Keep public communications separate from restricted operational information. A useful community update can explain a delay without publishing staff identities, detailed movement plans or sensitive locations. Feedback should also inform the revised response: a delay may affect different groups in different ways.

5. Keep donor reporting tied to verified results

Create a documented chain from the incident record to inventory adjustments, the revised work plan and the donor update. Explain what is confirmed, what remains under review and which decisions require approval. Check the grant agreement for notification and amendment requirements rather than assuming every funder follows the same process.

Distinguish expenditure from delivery and delivery from outcomes. Replacement costs may increase while the number of people reached falls. Reporting both changes clearly supports a more useful discussion about what the programme can realistically achieve.

A short agenda for the next programme review

  • What assistance is confirmed as delivered, delayed or lost?
  • Who is affected by the gap, and what evidence supports that assessment?
  • Which revised commitments need security, management or donor approval?
  • What additional support do implementing partners need?
  • What will communities be told, by whom and when?

Use these questions to produce a brief action record with named owners and review dates. The aim is a shared, evidence-based decision that teams can implement and explain.

Build the skills behind reliable humanitarian delivery

For practitioners reviewing their logistics skills, explore ATI’s Diploma in Humanitarian Logistics. The published course outline includes emergency-supply planning, partner coordination, stock controls and supply-chain risk management. Review the course details to assess its relevance to your role.

Source note: Incident details above are attributed to WFP’s 2 September statement. The checklist and management recommendations are ATI’s original analysis.

0