The day an organisation is entrusted with a CSO support facility — a fund to redistribute as grants to civil society organisations — its job changes in nature: it stops being only a beneficiary and becomes a second-tier donor. Calls for proposals to run, applications to appraise, agreements to sign, instalments to schedule, reports to collect from ten, thirty, sometimes a hundred organisations — then a consolidated report to produce for the upstream donor, who signed with you alone and holds you accountable for everything.
This guide describes the anatomy of a CSO support facility, the four workstreams that make it solid, the risks specific to cascade management, and how a shared information system — like Abvius — turns portfolio consolidation into a continuous process rather than a quarterly sprint.
CSO support facility: the fund manager's guide
Reading time: ~6 min
- When the operator becomes a donor
- The anatomy of a support facility
- Workstream 1: the fund's rulebook and procedures manual
- Workstream 2: traceable appraisal
- Workstream 3: cascading contractualisation
- Workstream 4: consolidated portfolio monitoring
- Risks specific to cascade management
- One system shared between the fund and its CSOs
- Mini FAQ
When the operator becomes a donor
CSO support facilities are multiplying, driven by the localisation agenda: rather than directly funding dozens of small organisations, donors entrust an envelope to an operator — agency, international NGO, consortium — tasked with redistributing it, providing support and accounting for it. For the operator, the responsibility is twofold: every euro paid to a CSO remains the upstream donor's euro, subject to its eligibility, visibility and audit rules; and each CSO's management quality becomes your risk. Our guide to sub-grants covers the bilateral relationship with one partner; here we take the whole-portfolio view.
The anatomy of a support facility
A complete facility chains six functions: publishing funding windows (calls for proposals, rolling or in waves), appraising and selecting applications, contracting with selected CSOs, scheduling instalments, technical and financial monitoring of supported projects, and consolidation-reporting to the upstream donor. Many facilities add a capacity-support component — because experience shows a fund that only disburses mostly produces late reports: see our article on strengthening CSO financial capacity.
Workstream 1: the fund's rulebook and procedures manual
Before the first call, the facility needs its internal law: CSO and project eligibility criteria, ceilings and funding rates, eligible costs (aligned with the upstream donor's — never more permissive), validation circuits, disbursement modalities and reporting requirements. This rulebook must be written before it is applied: every derogation granted in a hurry becomes a precedent the upstream donor's audit will examine. Good practice: have the upstream donor validate the manual at start-up, so the trade-offs are theirs.
Workstream 2: traceable appraisal
Selecting CSOs is a facility's most contested moment — by rejected applicants, and by auditors. It requires criteria published in advance, identical scoring grids for all applications, selection committees whose members declare their interests, and reasoned notifications. On the applicant side, require files that allow genuine analysis: our guide to building a call-for-proposals response describes what a good application contains — it doubles as an appraiser's reading grid. And for shortlisted CSOs, a financial management capacity assessment matches funding modalities to actual risk.
Workstream 3: cascading contractualisation
The agreement signed with each CSO must pass down the upstream contract's obligations: cost eligibility, implementation period, currency conversion rules, visibility, the upstream donor's and its controllers' audit rights down to CSO level, document retention, screening. Any obligation not passed down stays with you: if the upstream donor requires document retention for seven years and your CSO agreement says nothing, the gap is yours to bear. Contractual cascading is tedious legal plumbing — and absolutely central.
Workstream 4: consolidated portfolio monitoring
This is the workstream that overflows first. Thirty CSOs each reporting in their own format — a scanned PDF here, a spreadsheet there — produce a re-keying and reconciliation workload that absorbs the fund's team at every deadline. Consolidated monitoring requires three things: common reporting templates imposed from the agreement, a collection calendar offset from your own upstream deadlines (your CSOs report at D-30 so you report at D), and data structured at source rather than documents to re-key. The indicators to consolidate continuously: disbursements vs justifications per CSO, burn rates, report delays, open findings — the same reasoning as our article on grant portfolio monitoring.
Risks specific to cascade management
Double funding: a CSO funding the same activity from two windows — detectable only if your portfolio data is consolidated and comparable. Rule dilution: each level of the cascade that "simplifies" the upstream requirements a little produces, at the end of the chain, ineligible expenditure. Accounting heterogeneity: CSOs keeping their books on disparate tools make any consolidation approximate. CSO failure: without close monitoring of the first deadlines, it is discovered at final report stage, when nothing can be recovered. The upstream donor's review of the facility will focus precisely on your ability to detect these situations early.
One system shared between the fund and its CSOs
The structural answer to consolidation is to stop collecting documents and start collecting data. In Abvius, each supported CSO works in its own space — its grant budget, expense entry with attached documents, progress tracking — while the fund manager has a real-time consolidated view: disbursements, consumption per CSO and per line, alerts on delays and overruns. The upstream donor's eligibility rules are configured once and apply to the whole cascade; consolidated reporting is generated from the data the CSOs themselves entered, with no re-keying. And the tool itself becomes a capacity-strengthening component: CSOs come out equipped, not just funded.
Mini FAQ
What share of the fund should go to facility management?
The operator's management costs are negotiated with the upstream donor and vary with the intensity of the planned support. The classic mistake is undersizing monitoring: a CSO portfolio cannot be managed with single-project means.
Must supported CSOs be individually audited?
That depends on the thresholds set by the upstream contract and your rulebook. Audit rights down to CSO level must, however, always be contractually provided for.
Can a management tool be imposed on supported CSOs?
Yes, if the agreement provides for it and the tool is supplied to them — it is even one of the most durable forms of capacity strengthening. Imposing it without supplying or supporting it, however, is counterproductive.
Who is liable for a CSO's ineligible expenditure?
Towards the upstream donor: the operator, within the limits of the remedies provided by its agreement with the CSO. Hence the importance of the contractual cascade and early detection.
A support facility whose consolidation runs itself: request an Abvius demo.