Meetings

The DTA board meets monthly, and we host community meetings throughout the year. Both follow a consistent process designed to respect everyone’s time and produce visible follow-through.

Cadence

• Board meetings: first Monday after the 4th Friday of each month, 6–7 PM ET. (When that lands on a holiday — like Memorial Day — we move it; e.g., May 2026 moved to June 1.)
• Community meetings: ad-hoc, typically tied to a specific topic. The June 9, 2026 Downtown Watch with Fayetteville Police is one example.
• Next Downtown Watch after each one: announced in the recap so members can put it on the calendar immediately.

All meetings are listed on the calendar. Public meetings sync to the Discord server’s Events tab automatically when they’re created in the admin portal.

Before the meeting

For meetings where context matters (community sessions, partner sit-downs), we publish a Member Guide at faydta.com/meetings/<slug>/guide. The guide is a structured briefing that includes:

• Why this meeting matters — one sentence north star
• The longer story — the problem, what’s at stake, how this meeting addresses it
• Background — facts members benefit from knowing going in
• Before the meeting — suggestions (not orders) for how to come prepared
• What changes after — dated, observable outcomes members can watch for
• Headlines — honest framings if someone asks “why this meeting?”
• Openings — starter sentences if you want to speak in the room
• Worth bringing — practical prep
• Help spread the word — copy-paste sentences + shareable links

The guide is login-required (member-only). It’s not a marketing page — it’s an internal briefing that respects members as adults and explains what success looks like with observable outcomes, not vague aspirations.

The structure of these guides is documented in our internal authoring rules — descriptive section labels (not prescriptive ones), collaborative language (not adversarial), commitments owned by the org (not individuals).

During the meeting

• RSVPs accepted from both the FAYDTA web page and the Discord server’s Events tab (Discord “Interested” syncs to the FAYDTA RSVP list once a day)
• Agendas are published on the meeting page in advance
• Public meetings: open mic during a “Public Response” section near the end — anyone in the room can speak, with reminders on how to use 911 reporting to build a paper trail downtown businesses can act on

After the meeting

Within 48 hours of any meeting where the board committed to follow-up, a recap goes out:

• Posted on the meeting page (canonical record)
• Cross-posted to Discord #announcements (so members see it without checking the website)
• Lists what was raised, what the board committed to, what to watch for in the next 30 days

The recap is the accountability mechanism. If the board promises follow-up, the recap is where members verify it’s tracked.

For other boards

The patterns worth borrowing:

• Public cadence — first Monday after 4th Friday is a rule, not a guess. Members can plan months out.
• Member Guide before the meeting — not a marketing flyer; a working briefing. Use descriptive section names like “Background” instead of “What to think.” Respect members as adults.
• Impact section is mandatory — every guide commits to specific observable outcomes with dates. Volunteers donate time. They need to see the feedback loop.
• Recap within 48 hours — the difference between “we talked about it” and “we’re tracking it.” A specific outcome with a date beats every other accountability mechanism.

Avoid

• “What to think / Feel / Do” headings — too prescriptive, members tune out
• “Don’t miss out!” or “Last chance!” — fake urgency reads as marketing
• Naming specific people, businesses, or addresses as problems publicly (private records only — save it for the meeting itself)
• Vague “many issues were discussed” recaps — be specific or don’t post one