Letting your community submit regions without losing the plot

The fastest way to grow a map past what a small editor team can hand-draw is to let your community submit regions for review. The fastest way to kill a map is to let your community submit regions for review without thinking through what happens next. The two outcomes look identical from day one, and diverge sharply somewhere around week three.

The good news is the divergence is predictable. Communities that thrive on submissions all have the same operational habits. None of them are about the editor; they’re about how you treat the people on the other side of the form.

The submission template is the moderation tool

You’d think the moderation work happens at review time. It mostly happens at submission time. A vague submission form produces submissions that take 10 minutes each to evaluate. A specific submission form produces submissions that take 30 seconds.

What “specific” means in practice:

• One clearly defined region per submission. “Add three new districts” is three submissions, not one. Otherwise you’ll spend longer slicing it up than reviewing it.
• A required name field, not a required description. Names are easy to evaluate; descriptions invite essays.
• A category dropdown matching your taxonomy. No free-text categories. Free text is how a map ends up with eight slightly different ways of saying “territory”.
• An optional comment field. Most submissions don’t need one; the ones that do are the ones you actually want context on.

Set a review SLA you can actually hit

The single biggest predictor of whether contributors keep submitting is how long their first submission sits in the queue. Two days is fine. Five days is borderline. Ten days and they assume you’re dead.

Pick a target — we recommend 48 hours — and write it on the submission form. “We review submissions within 48 hours.” Then actually do it, even if the answer is sometimes “no, please resubmit with more detail”. A fast no is far better for retention than a slow yes.

Approve, reject, or send back — never ignore

Three outcomes; each has a script.

Approve — merge it, post a one-line thank-you in your community channel (“Added Eastside Park, submitted by @user”), and move on. The public credit is the incentive; it costs you nothing and keeps contributors coming back.

Reject — one specific reason, no boilerplate. “We don’t map private residences” lands fine. “Doesn’t meet our quality standards” reads as “we don’t like you”. Specificity is the kindness here.

Send back — your most useful tool. “Looks great, can you tighten the eastern boundary to follow the river?” lets the contributor improve their own submission and land it themselves, which builds far more loyalty than you fixing it for them.

The boundary the moderators have to enforce

Editors should never have to negotiate with submitters about the categories, the colour palette, or the level of detail. Those are decisions that were made when the map was planned. The moderation conversation is about whether this submission fits the existing rules, not whether the rules are right.

When a submitter pushes back hard on a rejection, route the conversation away from the editor and toward the planning conversation. “That’s a reasonable point about the colour palette; want to bring it up in the styling thread?”. This protects editors from becoming the lightning rod for every contested decision.

Recognise contributors visibly

A surprising amount of map energy comes from the dopamine hit of seeing your submission go live and credited. Three small habits move the needle disproportionately:

• Public credit. One-line announcement when a submission is merged. Their handle, the region name, a thank-you.
• Cumulative recognition. A leaderboard, a contributors page, a monthly “top ten contributors” post. Pick one and stick with it.
• Personal feedback on the first submission. A two-line comment from an editor on a person’s very first submission produces a return rate roughly twice as high as a silent approval. It’s the cheapest growth lever you have.

Watch the rejection rate

A healthy map has a rejection rate somewhere between 15% and 40%. Lower than that and the submission form isn’t filtering noise; you’re using editor time as the filter, which burns out editors. Higher than that and the form is too vague or the rules are unclear, and contributors walk away frustrated.

When the rate drifts in either direction, the lever is almost always the form, not the editors. Tighten the form and most of your moderation problems disappear. The platform tracks this number for you; check it monthly.

Eventually, recruit moderators from contributors

Your best editors are almost always your most prolific submitters who have already absorbed the rules. Promoting one or two of them to editor status, somewhere around the three-month mark, is the natural way the editorial team scales without losing consistency. They’ve already proven they understand the conventions; you’re just removing a layer between them and the merge.

The promotion is also a powerful signal to the rest of the community: that contributing matters, and that the path from outsider to insider exists. Communities without that path stagnate. Communities with it compound.