When an earthquake flattens a city or a flood redraws a delta, the world's volunteer mappers converge on the same few square kilometers at once, and without coordination they would collide: three people tracing the same road, nobody tracing the hospital district, no way to know when the map is done. The HOT Tasking Manager is the machine the Humanitarian OpenStreetMap Team built to prevent exactly that. It takes a project's area of interest and divides it into a grid of task squares; each mapper claims one square at a time, maps it in the OpenStreetMap editors, and reports back; each finished square is then checked by a second mapper before it counts. Around that simple loop the tool builds a complete coordination system: project instructions, difficulty ratings, live statistics, and a public record of who did what. This guide teaches the workflow as its users live it, from choosing a project to validating a stranger's square. The institution behind the tool is profiled in our HOT guide, and the mapathon, the social event built around this board, has its own guide; both are linked below. Here, the board itself is the subject.
Home / GIS and Open Map Data for Beginners
HOT Tasking Manager: How Humanitarian Mapping Gets Coordinated, Square by Square

Photo: Anna Shvets / Pexels
One Square, Mapped Well: The Tasking Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 7 complete
0% done
The Project Page: Read Before You Map
Every job in the Tasking Manager is a project, created by a humanitarian organization for a defined need: a disaster response, a development program, a preparedness campaign in a place the map has not reached. The project page is the contract, and reading it fully is the first professional habit the tool teaches. It states what to map (buildings only, roads and waterways, a full base map), which imagery to trace from and any alignment offsets that imagery carries in that area, the instructions that localize the global rules (how this region's roads are classified, what its buildings look like from above), and the project's difficulty and priority. The page also carries the board itself: the grid over the area, each square colored by its state, and the statistics that summarize the whole effort. A mapper who reads the page maps the project that was asked for; a mapper who skips it maps the project they imagined, and the validator will send the difference back. In humanitarian mapping the instructions are not bureaucracy; they are how a thousand strangers produce one coherent dataset for people who will plan aid deliveries on it.
The Loop: Lock, Map, Mark
The core interaction takes minutes to learn and a season to master. You choose a square, ideally adjacent to finished work so the map grows coherently, and lock it: the square becomes yours for a working session, and the board shows the world that it is taken, which is the entire anti-collision mechanism, one square, one mapper, one lock at a time. You then map it, in the iD editor in your browser or in JOSM if the project and your setup favor it, launched from the task page with the square's extent and the project's imagery loaded, tracing every feature the instructions ask for within the square's borders and a careful margin of attention to how features cross its edges. When the square is done, you return, write a changeset comment that says what you did, and mark the task as mapped. The square changes state, your lock releases, and the work enters the record. The etiquette inside the loop is the craft: if you cannot finish, release the lock rather than letting it expire in silence; if the imagery is cloudy or the area is already mapped, say so in the task comments instead of forcing traces through fog. The board forgives honesty instantly and guesses never.

Task States and the Meaning of Validated
The board's colors are a small state machine, and reading it fluently is how a contributor sees a whole campaign at a glance. A square begins ready: unclaimed, unmapped. Locked squares show as in progress under someone's name. Marked squares become mapped, awaiting review. And reviewed squares become validated, the state that counts toward the project's true completion, or are invalidated, returned to the pool with the reviewer's reasons attached, to be mapped again, better. The distinction between mapped and validated is the system's quality spine, and it deserves emphasis because newcomers routinely mistake the first for the finish: a project at 100 percent mapped and 40 percent validated is a draft, not a map, and the statistics on the project page report both numbers so that nobody, least of all the organization depending on the data, confuses them. Validation is done by experienced mappers, and the path to becoming one runs through having your own squares validated, and occasionally invalidated, which the culture treats as tuition rather than shame.
What Validation Actually Checks
Validation is a review with a checklist, not a vibe, and knowing it improves your mapping before any validator sees it. The validator opens the square in an editor with the mapped data over the imagery and checks: completeness, that the features the instructions asked for are all traced, no building cluster skipped in a corner; geometry, that buildings are squared where the buildings are square, roads connect where roads connect, and nothing is drawn in double; tagging, that features carry the project's classifications rather than the mapper's guesses; and edges, that features crossing the square's boundary meet their continuations in the neighboring squares, so the dataset is one fabric rather than a quilt of mismatched tiles. Failures return as specific, actionable comments, and a good invalidation note is a tiny tutorial aimed at one square. Mappers who internalize the checklist start validating their own work as they go, which is the moment the system scales: every mapper their own first validator, the board's reviewers catching what self-review cannot.
Difficulty, Priority, and Choosing Your Square
Projects and squares carry difficulty signals, and the Tasking Manager's design expects you to respect them. Beginner-friendly projects ask for one feature class from clear imagery; harder work involves dense informal settlements, poor imagery, complex road hierarchies, or local knowledge the instructions must supply. Priority is the other axis: during an active response, projects are ranked by the organizations on the ground, and the board's front page is a triage list where the highest-priority project is, by the community's compact, where spare mapping hours go first. Choosing a square is therefore a small act of citizenship: take work at your level, from the project that needs it most, next to finished squares, and leave the last confusing square of a hard project to someone equipped for it, with a comment explaining what you found. Your OpenStreetMap account is your identity throughout, sign-in uses it, your statistics accumulate under it, and your reputation in this system is simply the sum of your squares and how they fared at validation. That is the whole economy of the thing: attention, coordinated, checked, and credited.
The Social Layer: Comments, Changesets, and Talk
The board coordinates hands; the conversation around it coordinates judgment, and the Tasking Manager carries that conversation in three places a new mapper should learn to use. Task comments live on the square itself: questions about a confusing corner, a note that the imagery predates a new settlement, the validator's invalidation reasons, all attached to the work they concern, where the next mapper of that square will find them. Changeset comments, written when you save your edits in the editor, are the permanent record on the data itself, and the discipline the project pages teach, say what you mapped and cite the project, is what lets a stranger audit the map's growth years later. Project discussion happens in the channels each campaign maintains, the HOT community's chat spaces and the project's own threads, where imagery offsets, local conventions, and calls for validators circulate faster than any board can announce them. The through-line is that humanitarian mapping is a correspondence as much as a production line: the mappers who write clearly, in task comments and changesets alike, are the ones whose squares validate fastest, because a reviewer who can follow your reasoning trusts your geometry sooner. Silent competence finishes squares; articulate competence finishes projects.
Editors and Imagery: The Working Details
Two practicalities decide a square's fate more than any others, and both live at the seam between the board and the editor. Editor choice is the first: iD, in the browser, launches straight from the task page with the square framed and the project's imagery loaded, and it is the right tool for most squares and all beginners; JOSM, the desktop editor, serves validators and dense urban squares with its validation tools, alignment aids, and building plugins, at the price of setup the board cannot do for you. Imagery discipline is the second: the project page names the imagery source to trace from, because sources disagree, in age, in season, and in positional offset, and a square traced faithfully from the wrong layer is wrong with great precision. Where the project's instructions give an offset for the imagery, apply it before the first node, not after the validator's comment. And where the imagery and the existing map disagree, believe the project's instructions about which is stale, because in a mapped-before area the map may be newer than the photograph. These are unglamorous crafts, and they are the difference between squares that validate and squares that return.
Finally, a word on what the board does for the mapper, since the system's generosity runs both ways. A contributor's Tasking Manager history is a portfolio: projects served, squares mapped, validation rate, a record that humanitarian organizations genuinely read when they recruit experienced hands. The board that coordinates strangers also credentials them, and a season of careful squares is a qualification no certificate in this field matches.
New mappers ask one question above all: which project should I start with. The board answers it structurally, a beginner-difficulty project, a square beside validated work, instructions read twice, and it answers it socially too, because the fastest way to improve is to have your first square validated by someone kind enough to explain the note they left.
Related Guides
If this page answered part of the question, these GIS guides cover the rest of the same ground:
- The Humanitarian OpenStreetMap Team: The Institution: Who HOT is and the toolkit this board belongs to.
- HOT Export Tool: Filtered, Formatted OpenStreetMap Extracts: The other end of the pipeline: data out, for the field.
- Mapathons: The Event Format Built on This Board: The social occasion that fills the board with mappers.
- OpenStreetMap ZIM File: The Wiki in a File, and Maps in a File: The offline reference kit field teams carry beside this workflow.
Frequently Asked Questions
What is the HOT Tasking Manager?
The coordination tool of the Humanitarian OpenStreetMap Team. A project divides its area into task squares; mappers lock one square at a time, map it in iD or JOSM, and mark it mapped; experienced validators then check each square before it counts as validated.
Do I need a special account?
You sign in with your OpenStreetMap account. Your locks, your mapped squares, and your validation record all accumulate under that identity.
What is the difference between mapped and validated?
Mapped means a mapper has finished the square and said so. Validated means a second, experienced mapper has reviewed it against the project's instructions for completeness, geometry, tagging, and edge-matching, and approved it, or invalidated it back for rework.
What happens if I lock a square and cannot finish?
Release the lock and leave a comment saying what state the square is in. The board is built for honesty: an unfinished square released promptly costs the project nothing, while a square silently held blocks other mappers.
How do I become a validator?
By mapping first: validators are experienced contributors whose own squares have passed validation repeatedly. There is no separate application in the tool; the record of your work is the credential, and projects grant validation rights on that basis.
Photo credits: Anna Shvets (Pexels); Anna Shvets (Pexels). Photos are served from this site; follow the credit to the library page for the original.