Richmond community swap events with sorting rules

A community swap needs a clear point where an offered item becomes an accepted item. Without that distinction, a volunteer may receive something the event cannot use while the contributor assumes the organizer has taken responsibility for it.

For a Richmond swap, confirm the room's permitted use, storage, access, and final clearing requirements with its operator. Use the community swap planning checklist for the overall event; this guide focuses on intake, sorting, and closing ownership.

Publish a short intake rule sheet

Choose categories the team can actually manage and explain condition requirements, quantity limits, arrival times, and what is outside scope. A focused exchange is easier to explain than an invitation to bring anything unwanted.

Use fields such as:

• Accepted categories: [specific list].
• Condition and completeness requirements: [agreed criteria].
• Limit per contributor: [limit or clearly stated arrangement].
• Intake hours: [start and cutoff].
• Unaccepted items: [who retains them and how].
• Remaining accepted items: [confirmed return or collection arrangement].

Do not describe acceptance as a guarantee about an item's suitability. If the team cannot assess a category appropriately, resolve that before including it in the event.

Give items a defined route

Separate the intake decision from browsing. The physical arrangement should make it clear which items are ready to choose and which are still being checked.

Keep routes and room use consistent with the operator's arrangements. Do not let a sorting area grow into an unplanned storage zone.

Resolve uncertain items before the contributor leaves

Suppose a contributor brings a box containing both accepted and excluded categories. In this illustrative situation, the intake volunteer separates the categories, explains the rule, and confirms what the contributor will take back.

The volunteer should not accept the entire box merely to shorten the queue. Give one person authority to resolve questions and a clear way for helpers to reach them.

Use the volunteer role checklist to distinguish welcoming, intake decisions, table organization, and closing work. One person may hold several roles only when the timing makes that practical.

Track enough to reconcile the closing

For example, an illustrative count of 80 accepted books and 55 selected books leaves 25 books requiring the agreed closing route. Do not count rejected items as accepted stock or assume every empty table means every item was collected properly.

Record quantities by useful category rather than collecting unnecessary personal details. If the event offers contributor returns, establish an identification method and collection window before intake begins.

Confirm where remaining items go

A potential recipient is not a collection plan. Confirm what they accept, who transports it, when the handover happens, and what happens if collection falls through. Do not promise that every leftover will be donated.

Reserve time to count remaining items, remove signs, return borrowed supplies, and clear the room. The event-day coordinator checklist helps assign those final checks.

Use the community event collection, then plan the swap with responsibility for each item clear from arrival through closing.