# Build an organizer for a shared gathering

Build a shared web application for organizing a dinner, barbecue, camping weekend, or similar gathering. People can say whether they are coming, explain relevant needs, and volunteer to bring what is required. Build it extremely well for the group. Follow the [shared launch](../shared/launch.md).

Use an ordinary web link on phones and computers, with hosting that remains available when the builder's computer is off. Prefer a suitable free cloud option and explain its current limits. Participants use the application; the builder owns and manages its hosting setup.

## Organize the gathering people are actually having

Learn what the group needs to coordinate. A shared meal needs different preparation from a weekend with tents, vehicles, and cooking equipment. Give the organizer a clear event description, time, place, and practical instructions.

Let people respond with attendance and the information relevant to planning, including how many people they are bringing and dietary or other needs they choose to share. Make the resulting headcount understandable. Give personal information an audience appropriate to the group and its purpose.

Keep the current event details easy to find so someone returning from an invitation can immediately see when and where to arrive.

## Let people take responsibility for a contribution

The organizer can describe what is needed and in what quantity. Guests can claim a contribution, explain what they will bring, and see what still needs covering. Distinguish a request such as enough rice for eight people from a request for one camping stove.

Make the person's commitment clear after they claim it. When two people try to take the last available slot, give each an accurate outcome and keep the remaining needs correct. Let a guest revise or release a contribution when their plans change.

Show the organizer both the requested items and the commitments that cover them. They should be able to adjust quantities, clarify an unsuitable offer, and coordinate an alternative with the guest. Keep those decisions attached to the relevant contribution.

## Let plans change

If someone changes their attendance, make any related contribution easy to review. When a guest cancels, their promised equipment may need a new volunteer. Changes to the headcount may also change quantities needed for food or transport.

Keep the group's current arrangements visible and make important updates recognizable when people return. Give the organizer an appropriate way to prepare or send reminders if the group wants them, with a clear account of what the chosen connection does.

Choose a joining and identification method that fits this actual group. Explain who can see the event, change their own response, and manage the gathering. Keep the invitation process simple enough to use with the intended guests.

## Use it to organize one event

Deliver the hosted application with a useful example the person can adapt. Use separate participant sessions to respond, claim contributions, change a plan, and inspect what remains uncovered. Check the experience from a phone, including the practical information needed on the day.

Give the organizer a usable export or printable summary when they need it. Explain where the shared records live and apply the shared launch's ownership and recovery guidance, including any maintenance the selected free hosting requires.

Use the experience to teach how several people can act on shared information. A posted list becomes a working coordination tool when the application understands who has committed to what and what remains to be done.

Later, let the group reuse an arrangement for another gathering while starting with fresh attendance and commitments.