UUJAZ Journal ·
Designing a Welcoming Advocacy Gathering
Plan a public learning event that is clear, accessible, and useful to people with different levels of experience.
An advocacy gathering can bring neighbors together around a public question, but a crowded agenda does not guarantee a useful experience. People arrive with different levels of policy knowledge, access needs, and comfort with speaking in public. A welcoming event makes those differences part of the design. It gives people a clear reason to attend, explains what will happen, and offers more than one way to take part. Organizers can do this without turning a gathering into a complicated production.
Set one purpose and make it visible
Start by writing one sentence that says what participants should understand or be able to do by the end. A session meant to introduce a local issue needs a different structure from a meeting designed to prepare written comments. If the purpose is unclear, the agenda tends to accumulate speeches, updates, and activities that compete for attention.
State the purpose in the invitation and repeat it when the gathering begins. Include the audience, approximate schedule, and a note about whether participants will be asked to share anything. People should decide if the event fits without guessing what will happen after they arrive.
Plan access as part of the event
Access choices affect who can attend and contribute. Consider the entrance, seating, restrooms, transportation, sound, lighting, language, schedule, cost, and online options. Ask potential participants what would make the event workable; do not assume a familiar room is accessible to everyone. Put practical details in the invitation early enough for people to plan.
Offer multiple participation formats. A person might speak in a small group, write a question, use a remote option, or simply listen. Build pauses into the agenda and identify someone who can help with logistics. If food is served, explain what will be available and how participants can share dietary needs without disclosing more than necessary.
Make the learning active without making it stressful
Participants learn more when they can connect information to a question they care about. Keep the opening presentation short, define unfamiliar terms, and make space to compare perspectives. A facilitator can invite questions on cards or through a form so one confident speaker does not set the entire conversation.
Before asking people to act, explain what the action involves and what may happen to their contribution. Practice is helpful, but it should remain optional. Some people may want a clear script; others may prefer an outline and room to choose their own words. Provide context without implying one event can resolve a complex issue.
A sample 90-minute format
A community learning session might begin with ten minutes of welcome and access information, followed by a fifteen-minute plain-language overview. Participants could spend twenty minutes in small groups discussing a shared question, take a short break, then identify useful public sources and unanswered questions. The final portion can offer optional preparation for a next step and time to reflect.
This format is only a starting point. A gathering with a community partner may need more time for their priorities and fewer slides. A meeting about public comment may require practice, current rules, and alternative ways to contribute. Shape the agenda around the purpose instead of preserving a schedule for its own sake.
Review the invitation and the room
A short checklist helps a planning team see the event from a participant's point of view. Can someone understand the purpose quickly? Are the location and entrance directions clear? Does the invitation explain cost, schedule, language, accessibility, and follow-up? Are facilitators prepared if someone shares a concern the event cannot address?
- Can a first-time participant understand the schedule?
- Is there an accessible route or remote option?
- Who will send participants a follow-up?
One team member who did not write the invitation can review it for clarity. Another can walk from the street or transit stop to the meeting space. These checks often reveal issues that a planning group misses because it already knows the venue.
Close with a useful next step
A gathering should end with a clear sense of what happens afterward. Summarize open questions, share reliable resources, and explain whether participants will receive a follow-up. Do not promise a policy outcome organizers cannot control. A thank-you and an honest timeline help people decide whether they want to stay involved.
Within a few days, the team can review access requests, feedback, and partner guidance. Decide what to repeat and what to change. UUJAZ offers more planning help through the pages on gatherings and learning, Issues and Action Day, and hosting a community event.
Plan the follow-up before people arrive
Follow-up is easier when it is part of the event plan. Decide who will send a summary, what materials participants will receive, and how people can opt in to another activity. A short note that arrives on time is more useful than a detailed report that never appears. Include open questions alongside decisions so that participants can see where learning continues.
Invite feedback in a way that respects people's time. A two-question form, a brief conversation with a partner, or a quiet reply channel may be enough. Tell people how their responses will be used, then make one visible adjustment based on what you hear. A welcoming gathering is not defined only by what happens in the room; it also depends on what the hosts do with the trust participants offered.
At a glance
| Moment | Organizer's task | Participant's experience |
|---|---|---|
| Before | Share purpose and access details | Know what to expect |
| Opening | Set context and agreements | Understand how to take part |
| Learning | Offer several formats | Ask, listen, or reflect |
| Closing | Name follow-up and limits | Leave with a next step |