What is a pooled fund allocation table?
A pooled fund allocation table is the spreadsheet OCHA and the Humanitarian Coordinator use to assign money from a Country-Based Pooled Fund (CBPF) or the Central Emergency Response Fund (CERF) to specific organizations, broken out by sector, cluster, and project. Each row lists a project, its budget ceiling, and the caseload it covers against a sectoral envelope the strategy paper already set.
If you've sat through a strategic review committee call trying to figure out why shelter got a bigger envelope than WASH, you've already met this table. It's usually annexed to the allocation paper, and it's the thing donors and the Fund Board scrutinize line by line.
What the table contains
Formats vary slightly between funds and country offices, but most allocation tables carry the same core columns:
- Sector or cluster
- Implementing partner (UN agency, NGO, or national actor)
- Project title and budget ceiling
- Geographic area of implementation
- People in need and people targeted, usually split by sex and age where available
- Severity or priority ranking for the location
That severity column is where most of the argument happens in a strategic advisory group meeting. The money is limited, and in the first week after a sudden-onset event, cluster leads rarely agree on whose district is worse off, because verified needs data barely exists yet.
CBPF allocation strategy versus CERF allocation table format
A CBPF standard allocation runs on a strategy paper that sets sectoral envelopes and priority areas before partners submit project proposals, then rolls those proposals into the allocation table for HC sign-off. A CBPF reserve allocation, the rapid-response kind triggered by a sudden event, moves faster: envelopes get set within days, and the table gets built with whatever evidence is on hand at that moment, not six weeks later once assessment teams have driven every affected district.
CERF works on a similar logic but through OCHA's Geneva process, with its own rapid-response and underfunded-emergencies windows. The allocation table format there leans harder on quantified severity: country offices need a number, not an impression, to justify why one region's envelope is larger than another's.
In both cases the envelopes get split based on which geographic areas can show the worst damage, the most people in need, or the most acute gap. When that evidence is thin, the allocation defaults to population estimates or pre-crisis vulnerability data, which almost never matches what actually happened on the ground.
Where a damage count fits in the request
This is the gap that usually burns the first week of an allocation cycle. Clusters need an affected-area breakdown to populate the severity column and justify geographic targeting, and the standard sources (government damage reports, partner field assessments) take time nobody has when a reserve allocation window is open for ten days. Writing "assessment ongoing" into the strategy paper doesn't help the strategic advisory group decide anything, and it weakens the case when the Fund Board asks why one district's envelope is bigger than another's.
A structure-by-structure damage count from imagery doesn't replace the field assessment. It gives the allocation table a number to put in the severity and geographic-prioritization columns while that field work is still underway. Humanitarian Damage Assessment delivers exactly that kind of count, formatted for the row an appeal document already expects, inside the window a reserve allocation runs on.
If your strategy paper needs a damage figure before the next allocation deadline, that's the problem this exists to solve.