Maawa
← Maawa blog · Field guide

How to number, map and track every shelter in a camp

By Abdallah Al Raggad, founder of Maawa · Published · Updated · 8 min read

THE SHORT ANSWER

Give every shelter a permanent ID that never changes and fix it to the unit. Record its location only from a physical visit. Log every change (a move, a new household, a repair) as a dated event instead of overwriting the old value. Then tie requests and complaints to that same ID, so you can see what each unit needs and prove when it was resolved.

Most site registers start as a spreadsheet with one row per shelter. That works until the first re-plan, the first tent replacement, or the first family that moves three rows over. Then the row no longer describes a real place, and nobody can say what happened to it. This guide sets up shelter tracking so it stays true as the site changes. It assumes nothing about tools: everything here works on paper, in a spreadsheet, or in dedicated software.

It follows the spirit of the CCCM Cluster's Camp Management Minimum Standards.[1] Use those for the full picture of site management.

Step 1: Separate the shelter's ID from its address

Sites use addresses such as Block C, Row 4, Plot 12. Addresses are for people: they help a staff member find a place. But addresses change when blocks are re-drawn or plots merged. So give every unit two things:

  • A permanent ID, for example ZX-04821. It is short and unique, never reused, and means nothing on its own, so it never needs to change.
  • An address, kept as an attribute of the unit that can be updated when the site plan changes.

Everything else (occupancy, requests, repairs) hangs off the ID, never the address.

Step 2: Put the ID on the unit, twice

An ID that lives only in a spreadsheet is a guess. Fix a weatherproof label to the unit in two places, for example beside the door and on a side panel, so one damaged label doesn't orphan the unit. A machine-readable code (a QR code or barcode) next to the human-readable ID lets staff open the right record without typing.

Plan for replacement. UNHCR says relief tents usually need replacing after about one year of use.[2] When a tent is replaced, decide in advance whether the new tent keeps the old ID or gets a new one linked to the old record. Either works. Mixing the two does not.

Never put personal data on the label. No names, no registration numbers, no nationality. The label identifies the shelter, not the people inside it.

Step 3: Take location from a visit, not from a desk

Record the unit's coordinates when someone is physically standing at it: the first survey visit or the first scan of its label. Then change location only on another physical visit. Maps edited at a desk drift from reality within weeks, and a map you can't trust gets abandoned.

Step 4: Keep history, not just current state

A register that overwrites values can tell you where unit ZX-04821 is today, but not where it was when a protection incident was reported last month. Record changes as an append-only log: what happened, to which unit, when, where, and who recorded it.

DateUnitEventLocationRecorded by
2026-03-02ZX-04821Unit placedBlock C, R4, P12Staff 17
2026-03-02ZX-04821Household 2291 moved in (5 people)Block C, R4, P12Staff 17
2026-06-19ZX-04821Repair: door frameBlock C, R4, P12Staff 08
2026-09-30ZX-04821Unit movedBlock F, R1, P03Staff 17
Nothing is edited or deleted. Mistakes are corrected by adding a new event that closes the wrong one.

In a spreadsheet, that is a second sheet with one row per event. In software it is an event log. Either way, the current state of a unit is simply its latest events.

Step 5: Link households to units with start and end dates

Occupancy is a relationship that starts and ends: household 2291 lived in ZX-04821 from 2 March to 30 September. Store it that way. You can then answer "who lived here when?" and "how often do households move?" without guessing.

Collect the minimum personal data you need, keep it separate from the public-facing label, and agree in advance who can see it.

Step 6: Tie requests and complaints to the unit

This is where most sites lose the thread. In 2024, only 19% of households in crisis knew how to make a complaint, and only 43% of those who did received a response.[3] Both numbers improve when the feedback channel is attached to the shelter itself:

  • The channel is where people already are. A code on the shelter that opens a short request form (water, food, medical, repair, security) needs no hotline number, no app and no account. UNICEF used QR codes on relief kits after a cyclone in India to collect feedback from recipients.[4]
  • The request arrives already located. Staff know which unit asked, so they don't have to search for it.
  • Resolution is recorded at the unit. When the repair is done, the person who did it closes the request there. That gives you a time-stamped record of "asked" and "answered": the response rate donors increasingly ask for.

Step 7: Review the register every week

A register is only useful if someone reads it. Once a week, look for:

  • Silent units: no visit, scan or request in, say, 14 days. Is anyone living there?
  • Repeat faults: the same unit reporting the same problem two or three times. Fix the cause, not the symptom.
  • Slow requests: anything open longer than your usual resolution time, especially from households with children, older people or people with disabilities.
  • Ageing stock: units near the end of their expected life. In Zaatari, more than 10,500 prefabricated shelters house over 47,000 people, and most have exceeded their lifespan. Limited 2026 funding meant only 59 families had their shelters rehabilitated in the first half of the year.[5] With a budget that tight, knowing which units are worst is the whole job.

Which tools work for shelter tracking?

  • Paper and a spreadsheet are fine for a few hundred units with a stable team, if you keep the event log discipline.
  • Survey tools such as KoboToolbox or ODK are good for structured assessments, but they are built for one-off forms, not a living record of each unit.
  • Site-operations software brings the register, the map, requests and history together. We build Maawa OS for this: every unit gets a permanent QR code, location changes only on a physical scan, history is append-only, and occupants can ask for help or raise an SOS without an app. Whatever you use, steps 1 to 7 are what make it work.

Frequently asked questions

What is a shelter numbering system in a camp?

It is the way each shelter is identified so staff can find it, record its occupancy and track repairs. Good systems give every unit a permanent ID that never changes, plus a separate address (block, row, plot) that can be updated when the site plan changes.

Should a QR code on a shelter contain personal data?

No. The label should identify the shelter, not the people inside it. Keep names and registration details in a protected record linked to the unit ID, with access limited to the staff who need it.

How often should a camp site register be updated?

Changes should be recorded as they happen, at the unit, as dated events. Review the whole register at least weekly for silent units, repeat faults, overdue requests and ageing shelters.

Can you track shelters without software?

Yes. A paper register plus a spreadsheet with one sheet for units and one for dated events works for a few hundred units. Software helps most when the site is large, staff rotate often, or requests and SOS calls need to reach the team in real time.

Try the register, the map and the requests together

The Maawa OS sandbox builds a live demo camp in about 30 seconds: mapped units, open requests, an SOS board and the history behind each unit. No signup, no card.

Sources

  1. CCCM Cluster, Camp Management Minimum Standards. cccmcluster.org
  2. UNHCR Help Syria, Shelter assistance. help.unhcr.org
  3. ALNAP, State of the Humanitarian System 2026: In brief. alnap.org
  4. UNICEF India, "The power of a scan": QR codes in cyclone recovery. unicef.org
  5. UNHCR Jordan, Zaatari Refugee Camp factsheet, July 2026. data.unhcr.org

Figures are quoted as published by each source on the date shown. Spotted an error or a newer figure? Write to hello@maawa.co.

Keep reading