Supply Lists for Scout Troops, Churches, and Small Community Groups

Small community groups run on the same fuel: one or two organized people, a group chat, and somebody's credit card. A scout troop needs camping gear. A church youth group needs supplies for a service project. A neighborhood association needs materials for the spring cleanup. The need is small, the budget is nothing, and the current process is that a leader buys it and hopes to be reimbursed.

That works until it doesn't, and it burns out the exact person you can least afford to lose.

Replace the group chat with one list, one link, quantities on every item, and a way to claim. It works less because it's better organized and more because "claim one item from this list" is a bounded thirty-second task with a visible finish line, while "bring supplies for the campout" is an open-ended obligation nobody wants to be first to accept.

Why the group chat approach breaks

The default is a message: "Can anyone bring paper plates, a folding table, and about 40 water bottles?" Then:

• Three people bring plates. Nobody brings the table.
• The replies scroll away. Someone who checks the chat on Thursday can't tell what's still needed without reading 60 messages.
• Nobody wants to be first. A message with no responses yet feels like being volunteered for the whole thing.
• One person covers the gap. The leader buys whatever didn't get claimed, again, and quietly absorbs the cost.
• The next event starts from zero. Nothing carries over, so the whole dance repeats monthly.

None of this is a commitment problem. Volunteer groups are usually full of people who'd happily grab one thing. The chat just makes it impossible to see which one thing to grab.

The pattern that works

One list, one link, quantities on everything, and a way to claim.

The list is the source of truth. Anyone can open it at any time, see exactly what's still needed, take one item, and be done in under a minute. No thread to read, no coordinating with anyone, no reimbursement.

This changes the psychology more than it changes the logistics. "Bring supplies for the campout" is a vague, open-ended obligation. "Claim one item from this list" is a small, bounded, visibly-finite task, and people say yes to those.

What this looks like for different groups

Scout troops. Camping consumables (propane, first aid restocks, trash bags, fire starters), shared gear that wears out (tarps, lanterns, cook kits), and badge or project materials. Troops usually have both a recurring need and event-specific pushes, so keep one standing list and add a section per campout.

Church groups and youth ministry. Service project materials, VBS or program supplies, kitchen and hospitality consumables, and specific items for families the group is supporting. The last category benefits most from a claim list, because families being helped shouldn't be in a group chat where their needs are discussed.

Sports teams and boosters. Practice equipment, first aid, snacks and water for the season, banquet supplies, uniform accessories. Quantity-heavy, which is exactly where claim counts shine.

Neighborhood and volunteer groups. Cleanup supplies, gloves, bags, tools, plants, paint. Often one-off events with a wide, loosely-connected pool of people — the ideal case for a link anyone can act on without joining anything.

Mutual aid and family support. A specific family's needs, listed without putting anyone's situation in a public thread. Anonymity matters here more than anywhere; see the note below.

Making the list easy to say yes to

A few things reliably raise the completion rate:

Set quantities. "Water bottles — need 40" lets eight people each grab a case. Without the number, one person buys 40 and nobody else participates.

Spread the price range. Include several items under $10. People who can't cover a $60 tarp will absolutely bring paper plates, and letting them participate keeps them in the group.

Allow the no-link items. Half of what a community group needs isn't a specific product: "a folding table," "a cooler of ice," "someone's truck for an hour." A list that only accepts product URLs pushes those into the chat and you're back where you started. Being able to type in a plain item matters more here than for most use cases.

Don't lock it to one store. Your members shop everywhere, some prefer local, some have a warehouse club membership, some have a gift card. A single-retailer list quietly excludes all of them.

Re-share it, twice. Once when it goes up, once about three days before the deadline with "still open: …" and the remaining items. The second message does most of the work.

For the standing list, let people follow it instead. Members leave an email once and get a note when you add something — one a day at most, no account, one click to stop. The next campout's supplies then do not need a fresh round of messages, which matters most for the loosely-connected people who joined the chat once and muted it.

The tool part

EZWishlist fits this shape closely: one free list, items from any store by link or barcode or just typed in plain words, quantities that count down, and claiming in two taps with no account for the person helping. That last part matters for volunteer groups more than most, because your pool includes people who joined the chat once and will never install anything.

Claims are anonymous, which is worth thinking about for mutual aid and family support in particular — supporters can help without the recipient feeling accounted for, and without a public record of who gave what. Abandoned claims expire and free the item back up, so a well-meaning "I'll grab that" that never happens doesn't silently sink the item.

A few practical notes

Deadlines beat open-ended asks. "By Friday" gets claimed. "Whenever you can" doesn't. Put the date on the list itself, not just in the message.

Pick a delivery point. Either items ship to one address or people bring them to a meeting. Say which on the list. If you're shipping, use the church, school, or organization address rather than a volunteer's home, and check that the address is only revealed after someone claims rather than published publicly.

Keep one standing list. Rebuilding a list per event is the thing that makes organizers quit. One list you edit is a fifteen-minute job; a new one each month is a chore.

Run it together. The list doesn't have to live with one person. Whoever creates it can invite co-leaders to help manage it, and everyone invited can add and update items — so the troop leader, the coach, and the parent coordinator can all keep the same list current.

Say thank you as a group. Since claims are anonymous, thank the group rather than individuals, or ask people to add their name in the claim note if they'd like to be recognized. Some will, plenty won't, and both should be fine.

The point

None of this is complicated, and that's rather the point. The reason supplies don't get covered isn't that people won't help — it's that "help with the campout" is a vague obligation and "claim one item from this list" is a thirty-second task with a visible finish line. Swap one for the other and the same group of people covers noticeably more, with nobody fronting the money.