How can we fairly split park trail map verification tasks?

[GregoryJ]

I’m trying to organize a community-led restoration of our local park’s trail maps, but I’m hitting a wall on how to fairly divide the verification work. Everyone wants to contribute data, but nobody seems to want the tedious task of cross-checking the submissions for accuracy.

[Luke_W]

We tried splitting into small, rotating review pairs so no one got stuck doing the whole cross-checking. People liked contributing data but the pairing made the task feel doable. We kept a simple log so mistakes could be flagged quickly.

[Gary.L]

Maybe the problem isn’t the checks themselves but the sense of ownership. Some folks want to help but don’t want to own a quality gate. It might need a shared responsibility culture, not more rules.

[Paisley.W]

I tried a lightweight QA process and it bogged down the folks who were already busy. We did it for a couple of weeks, numbers didn’t improve, and I dropped it.

[EvelynWD]

I keep wondering if we’re chasing the wrong thing, arguing about who checks what instead of actually updating the maps. Maybe a rotating verifier role with a quick thumbs-up would work, maybe not. What do you think?