AA Remote Communities Committees: Start With the Access Barrier
A meeting can be nearby on a map and still hard to reach. The barrier might be the language used, an unreliable connection or a location people cannot get to after work. A Remote Communities project begins by learning which part of access is actually missing.
Describe the barrier in usable terms
Before proposing a platform or venue, ask what someone trying to attend would encounter. The obstacle could be a road that is difficult in winter, a listing that assumes reliable data or a meeting whose language is different from the one prospective participants use. Avoid deciding which of these applies on their behalf.
Translate the answer into a testable task. Instead of asking volunteers to improve access generally, ask whether someone can find a meeting with the correct language, confirm how to enter and reach a contact if the listing is wrong. That description tells the team what it must check.
Build with local members
Use the committee's workbook and the local service structure to find out who already supports the community. Ask about existing meetings before creating another listing. People closest to the problem may know which venue, contact or format can be maintained after outside volunteers leave.
Agree how the group wants to be described publicly, what language to use and which information can be shared. Write down who owns the listing and who can update it. If the answer is nobody, the project needs a handover plan before it needs more publicity.
Test the simplest option
Try the instructions as a newcomer would. Does the link open on a phone? Is the day and time clearly stated for local readers? Does the advertised contact work, and has the person agreed to be listed? If the connection drops, check whether the stated backup is actually available.
Give the test a realistic ending. A good result might be one accurate meeting entry and a willing contact who can answer questions. Keep a note of the barriers still present and the parts a local group can own. An impressive launch is less useful than information someone can trust next month.
For a small project, make a one-page handover sheet with the listing link, the person authorised to update it and a date to recheck it. Test the instructions with someone who was not in the planning discussion. If they need the organiser to explain how to join, revise the instructions before sharing them more widely.
Separate participation and recognition
A newcomer may ask about tokens once they find a meeting. Point them to the group for its practices. Our guide to obtaining AA chips explains the distinction between asking about chips and shopping for a personal keepsake. Do not add a chip ceremony to an access project unless the group has agreed how it would work.
If a member independently wants an anniversary gift, ask which date, design and handover they prefer. A purchase should never be the price of taking part. The main measure of the project remains whether the path to the meeting works for the people who need it.
Medallions to consider
For a separately confirmed AA anniversary, these are two optional retail keepsakes. Check the recipient's preferred design before ordering.
Tricolor Jet Black Diamond Sparkle (1-50y)
The milestone selector lists 1 to 50 years. The photo shows XLV as a sample. Select the recipient's confirmed milestone on the product page.
Tricolor Opulent Deep Blue (24h, 1-65y)
The milestone selector lists 1 to 65 years, plus 24 Hours, 18 Months. The photo shows XXV as a sample. Select the recipient's confirmed milestone on the product page.
Common questions
Does remote always mean rural?
No. AA's committee guidance also recognises barriers involving language and culture.
What is a sensible first result?
A specific barrier addressed, with an agreed owner for keeping the solution usable.
Keep reading
Explore Elite Medallions and Deluxe Coins to compare designs and available milestones.
