Registration lists vs. satellite shelter counts for ration planning

Every camp management officer who has had to defend a ration order knows the awkward question: are these numbers from the last registration sweep, or from what's actually on the ground now? Most of the time the honest answer is "the sweep," and the sweep is three months old.

What a registration sweep actually gives you

A registration exercise is still the only way to get names, family size, vulnerability flags, and ration entitlements tied to an individual household. Nothing replaces it for protection casework or targeted distribution lists. But a sweep is a point-in-time headcount that depends on households showing up, staff capacity to process them, and arrivals knowing registration exists and choosing to queue for it. In a camp that's growing fast, all three of those break down at once.

New arrivals build a shelter the first week and get registered the sixth, if the backlog allows it. Some households split to access double rations and never correct the record. Others leave and the shelter stays standing, counted as occupied long after it isn't.

None of this is a failure of the registration team. It's what happens to any list-based count when the population it's tracking is moving faster than the list can be updated.

Where a shelter count fits

A shelter count works from a different signal: structures visible in an overhead image, counted and dated. It doesn't know who lives in a shelter, what the family size is, or whether anyone there qualifies for a supplementary feeding program. It can't replace registration data for that. What it does tell you, reliably and on a schedule you set, is whether the footprint is expanding, where the new construction is clustering, and roughly how many shelters exist against how many names are on the list.

That gap between shelter count and registered households is the number worth watching. If the two tracks are close, the registration backlog is manageable and ration planning built on the list is probably sound. If the shelter count keeps pulling ahead of registered households month over month, that's the growing settlement that outdated registration data won't show you until the complaints start at the distribution point.

Using both instead of picking one

Registration sweep and shelter count work best run side by side, read as a gap rather than treated as a choice between two systems. Registration still drives the entitlement list. The shelter count becomes the early-warning layer that tells a CCCM or food security team when the next sweep is overdue, and roughly by how much, before a formal verification confirms the gap on the ground.

For a settlement where new arrivals are building shelters faster than intake staff can process paperwork, a monthly shelter count mapped against the previous month's footprint gives that early-warning read without waiting for the next full registration cycle. It's dated, it's a count of structures rather than names, and it shows where the growth is so a verification team knows which sector to prioritize first.

A quick way to frame it

• Registration list: who is here, household by household, as of the last sweep.
• Shelter count: how many structures are standing, as of this month's imagery.
• The gap between the two: how far the ration plan has drifted from the camp's actual footprint.

None of this argues for dropping registration. It argues for not treating a three-month-old sweep as current just because it's the only number on file. A camp that's holding steady can run on registration data alone for a long stretch. A camp that's adding shelters every week needs a second, faster-moving number next to it, or ration planning ends up reacting to shortages instead of seeing them coming.

If your caseload estimates keep drifting from what's showing up at distribution, it might be time to put a shelter count next to the registration list and see how far apart they've gotten.