What is a household size multiplier in camp population estimates?

If you've sat through a coordination meeting where two agencies quoted different population figures for the same camp, the household size multiplier is usually where the gap comes from.

A household size multiplier is the average number of people assumed to live in one household, used to convert a count of households (or shelters) into an estimated population. If your multiplier is 4.8 and you count 1,200 shelters, your working population estimate is 5,760. Change the multiplier to 5.5 and the same shelter count gives you 6,600. Nobody touched the ground truth. The number on your ration plan just moved by 850 people because of an assumption buried three steps back in the math.

Where the multiplier actually comes from

Most multipliers trace back to a registration exercise, a verification sweep, or a demographic survey done at some point in the camp's history. Someone counted households and individuals directly in a sample, divided people by households, and got a ratio. That ratio becomes the standing assumption applied to every future shelter count until someone updates it.

The problem is that household size isn't fixed. It drifts with the things that happen in a growing settlement:

• New arrivals doubling up in existing shelters before new plots are allocated
• Births, and the deaths and departures nobody formally deregisters
• Splitting, where one household becomes two as children marry or extended family regroups
• Secondary movement, where people register in one block and sleep in another

A multiplier calculated during initial registration, when the camp was smaller and more tightly managed, often doesn't hold six months or a year later once the settlement has grown organically. The shelters you can see from above tell you something the registration list can't: how many structures actually exist right now. The multiplier is still an assumption about how many people are in each one.

Shelter count plus multiplier, not shelter count alone

This is the part that gets skipped in a lot of planning documents: a shelter count is not a population estimate. It's an input to one. The arithmetic looks simple, population equals shelter count times multiplier, but the multiplier carries all the uncertainty. A precise, dated, monthly shelter count built on a stale or wrong multiplier will still produce a wrong caseload number, just a wrong number you can trust the structure-counting part of.

That's why pairing a fresh structural count with a periodically revalidated multiplier matters more than chasing precision in either input alone. If your last household size survey is eighteen months old and the camp has absorbed two influx waves since, the multiplier is probably doing more damage to your estimate than any imprecision in counting shelters.

In practice, most camp management teams don't have the field capacity to re-survey household size every month. What they can do is update the shelter count monthly and apply whatever multiplier their latest demographic data supports, flagging it as provisional when that data is older than it should be. That at least keeps the two sources of error visible instead of burying them inside one combined number where a counting miss and a stale multiplier cancel out or stack and nobody can tell which one moved.

What to ask before you trust a population figure

Before you sign off on a caseload number for ration planning or a shelter allocation ask, it's worth asking three things: when was the household size multiplier last measured, against what sample, and how much has the camp's footprint changed since the last shelter count that fed into it. If the answer to any of those is "we're not sure," the population figure is a guess wearing a decimal point.

A monthly footprint and shelter count, dated and mapped against the previous month's boundary, at least gives you a current structural baseline to apply the multiplier to, rather than working off whatever shelter total was last confirmed at registration. Refugee Camp Mapping builds that monthly shelter-count layer and footprint-change map from a VHR pass over the camp, so the multiplier isn't the only moving part left unaccounted for in your estimate.

If your caseload planning is still anchored to the last registration sweep, it might be worth seeing what a current monthly count looks like next to it.