Plan Community Swap Intake, Exchanges and Leftover Items
A practical planning template for community swap events: set intake rules, choose a one-in/one-out or token exchange, assign volunteers and agree what happens to leftover items.
Contents
- Inputs to gather before you write the plan
- Step 1: Define accepted contributions
- Step 2: Set up the intake record
- Step 3: Choose how exchanges work
- Step 4: Plan sorting and display
- Step 5: Assign volunteer roles
- Step 6: Agree what happens to leftover items
- Worked example (hypothetical)
- Copyable planning template
- Adding drinks for a sip-and-swap
- Check the plan for gaps and conflicts
Settle three decisions before you announce a community swap: what you will accept, how a contribution turns into the right to take something, and where unclaimed items go when the event ends. Write each one down as a rule that volunteers and participants can read before they arrive. Then build an intake record, a display layout and a volunteer rota around those rules.
This guide covers that planning workflow for clothing swaps, general item swaps and sip-and-swap socials. All of the rules described here are organizer choices. Your venue's requirements, and any local rules that apply to your event, sit outside this plan. Check those separately with whoever governs them.
Inputs to gather before you write the plan
- Accepted categories, such as adult clothing, children's clothing, shoes, accessories, books or housewares
- Item limits per participant, if you want them
- Condition criteria an item must meet to be accepted
- Drop-off window, either before the event or at the door
- Exchange arrangement: one-in/one-out, tokens or another rule you define
- Display materials you already have or can borrow, such as racks, tables and hangers
- Volunteer count and the shifts they can cover
- A leftover destination agreed in advance, plus who will transport items there
Step 1: Define accepted contributions
Publish your accepted categories, any per-person item limit, your condition criteria and your drop-off times together, so participants can sort their items at home. Also state what happens to items that don't meet the criteria. They might be handed straight back at the intake table, or set aside for the participant to collect at closing. Deciding this in advance means intake volunteers won't have to make judgment calls in front of a queue.
Write condition criteria that a volunteer can check in seconds. Examples include clean, no broken zips or missing buttons, and no heavy stains or odors. Vague standards like "good quality" lead to inconsistent decisions between volunteers.
Step 2: Set up the intake record
Keep one line per participant at the intake table. A paper sheet or a shared spreadsheet both work. The record lets you settle disputes about credit, find out whose items went unclaimed and follow each person's leftover instruction.
| Field | What to record | Why it matters |
| Participant ID | Name, number or wristband code | Links credit and leftovers to a person |
| Accepted count | Number of items that passed intake | Basis for exchange credit |
| Category/size | Main categories and sizes received | Tells display volunteers how much space each label needs |
| Credit issued | Tokens or swap allowance given | Prevents double-issuing |
| Return or leftover instruction | Return to owner, retain with permission, or give to agreed recipient | Drives the closing workflow |
Step 3: Choose how exchanges work
There are two common arrangements. One-in/one-out means each accepted item entitles the contributor to take one item. It is simple to explain and easy to track. A token system lets you weight items differently. The author of the Curiously Conscious blog describes assessing contributions at their largest swap and assigning each item between one and five tokens. The same author later suggests a simpler one-to-three-token scale. Wider scales need more judgment at intake, so a narrower one may suit volunteer teams with less experience.
Whichever arrangement you pick, answer these questions in your published rules:
- How does a contribution receive credit, and who decides the token value?
- When does browsing open? For example, after intake closes, or in staggered groups.
- How are competing claims resolved when two people want the same item? Options include first hand on the item or a quick coin toss, but choose one.
- Does unused credit expire at the end of the event or carry over to a future swap?
- Can people attend without contributing? If so, what can they take?
The Curiously Conscious author also reports displaying the organizers' own contributions as starting stock. This means early arrivals find full rails rather than empty tables while intake is still underway.
Step 4: Plan sorting and display
Sort displays using the same category and size labels you used on the intake record, so volunteers can move items from intake to display without re-sorting. Before the event, list your racks, tables, hangers, bins and signs against the intake you expect. If registrations suggest far more items in one category than your display space can hold, cap that category or find more materials. Discovering the shortfall on the day leaves volunteers with nowhere to put items.
Step 5: Assign volunteer roles
| Role | Responsibilities |
| Intake | Check items against criteria, record accepted count, issue credit, note leftover instructions |
| Sorting | Move accepted items into category and size groups |
| Display | Hang, fold and restock rails and tables; keep labels accurate |
| Exchange | Collect tokens or check allowances; resolve competing claims using the published rule |
| Closing | Apply leftover instructions, pack items for recipients, confirm collection, clear the venue |
Intake and sorting are busiest at the start, and closing is busiest at the end. A volunteer can often cover one early role and one late role, but name a lead for each role so participants know who decides.
Step 6: Agree what happens to leftover items
Plan the leftover route before the event, not at closing time. Each participant's intake line should already say whether their unclaimed items will be returned to them, kept by the organizers with permission, or offered to an agreed recipient. If you plan to donate, confirm that the recipient will accept the categories you expect, and agree when and how items will be collected or dropped off. The Curiously Conscious author describes two approaches for leftover clothing: a collection partnership with a charity, and contacting a charity shop ahead of a later event to agree a drop-off.
Worked example (hypothetical)
This illustration assumes a one-token-per-accepted-item rule. Under that rule a token is a swap allowance, not a statement that the items are worth the same amount.
Participant Accepted Category/size Tokens Taken Remaining Leftover instruction
P-014 4 Women's tops, M 4 3 1 Give to agreed recipient
P-015 2 Kids' shoes, 11-13 2 2 0 Return to owner
P-016 5 Books 5 1 4 Retain with permission
P-014 contributed four accepted items and took three, so one token is left. The published rule decides what that token means: it either expires or carries over. At closing, the closing lead checks each line. P-015's unclaimed items go back to P-015, P-016's are kept as agreed, and anything marked for the recipient is packed for the confirmed collection.
Copyable planning template
EVENT: ____________ DATE: ________ VENUE: ____________
ACCEPTED CONTRIBUTIONS
Categories: ____________________________
Item limit per person: ______
Condition criteria: ____________________
Drop-off window: _______________________
Items not accepted are: [ ] returned at intake [ ] held for collection at closing
EXCHANGE RULE
[ ] One-in/one-out [ ] Tokens (scale: ___ to ___) [ ] Other: ________
Browsing opens: ________
Competing claims resolved by: ________
Unused credit: [ ] expires at close [ ] carries over to: ________
Starting stock from organizers: [ ] yes [ ] no
DISPLAY
Labels (category/size): ________________
Racks ___ Tables ___ Hangers ___ Bins ___ Signs ___
VOLUNTEERS (lead / shift)
Intake: ________ Sorting: ________ Display: ________
Exchange: ________ Closing: ________
LEFTOVERS
Recipient: ________ Accepts categories: ________
Acceptance confirmed: [ ] yes Collection/drop-off time: ________
Transport by: ________
INTAKE RECORD COLUMNS
Participant ID | Accepted count | Category/size | Credit issued | Leftover instruction
Adding drinks for a sip-and-swap
If you plan to serve beverages, treat them as a separate item in the plan. Review the venue's requirements for drinks, and any rules that apply to what you plan to serve, with the venue before you promote the event. Keep drinks away from display tables and rails so spills don't damage stock.
Check the plan for gaps and conflicts
- Every accepted category has a display label and enough display space.
- The condition criteria and the handling of rejected items appear in participant-facing information.
- The exchange rule answers credit, browsing start, competing claims and unused credit.
- The intake record has a leftover instruction column, and volunteers know to fill it in.
- Each role has a named lead, and no one is scheduled for two roles at the same time.
- The leftover recipient has confirmed acceptance and a collection or drop-off time.
- If drinks are planned, the venue review is complete.
Related articles
Plan a Community Event Information Desk Enquiry Workflow
Build an information desk enquiry workflow for a community event or tournament: desk reference sheet, enquiry log template, referral steps and a printable desk copy.
Plan and Maintain a Community Event Attendee FAQ
Build an attendee FAQ from approved event information, with a named owner for each answer, publication approval and clear triggers for rechecking.
Prepare a Community Event Committee Handover
A practical handover template for community event and tournament committees: what to record, how to transfer each work area, and how successors confirm ownership.
Define Roles and Responsibilities for a Community Event Committee
A practical way to assign committee roles for a community event or amateur tournament: name an owner for every deliverable, set approval authority, map dependencies and agree when changes get reviewed.
Specify the Information and Presentation for an Event Ticket
Build a ticket design brief for your tournament or community event: confirm the required details, set a clear visual hierarchy and lock down print or digital output needs before design starts.
Compare Volunteer Management Software Against Event Requirements
Compare volunteer management software against your event's real needs with a requirements worksheet, scripted demo tests, like-for-like pricing and fair scoring.
Plan a Community Cleanup Event
A practical guide to planning a community cleanup: define the purpose and area, assign named owners, confirm collection arrangements and send participants a clear, final plan.
Plan Waste Collection and Cleanup for a Community Event
A step-by-step plan for community events and amateur tournaments: reduce materials, map collection points, assign volunteers and close out cleanup with confirmed collection.
Coordinate Community Event Accessibility Requests
A practical template for collecting, answering and confirming accessibility requests at community events and amateur tournaments, with restricted tracking and clear delivery owners.
Plan Accessibility Across a Community Event
An event accessibility checklist for community events and amateur tournaments: build an accessibility plan from publicity to arrival, venue, activities, vendors and emergencies.