Draft a complete starter kit for launching a new local chapter (governance, membership, and first events), grounded in your own bylaws and chapter handbook. Joy writes it; you copy it into your docs and run it.
Using our chapter handbook and bylaws in the Knowledge Center, draft a starter kit for launching a new [city] chapter with a [90-day] setup checklist covering governance, membership, and first events.
Um exemplo ilustrativo. Seu resultado vai refletir suas fontes, dados e pedidos.
I built this from the Chapter Handbook (2024 edition) and the National Bylaws in the Knowledge Center, using your standard charter thresholds. The 90-day plan below breaks into three phases, each tied to the handbook section it comes from.
Chartering a new chapter runs in three phases: stand up governance first, open membership once officers are in place, then hold the first two events to activate the base. The thresholds below come straight from the handbook, so nothing here needs a separate approval you didn't already plan for.
| Phase | Window | Goal |
|---|---|---|
| 1. Governance | Days 1–30 | Charter application filed, officers seated |
| 2. Membership | Days 31–60 | 25-member minimum met, dues flowing |
| 3. First events | Days 61–90 | Kickoff plus one recurring event booked |
Phase 1: Governance (Days 1–30).
Phase 2: Membership (Days 31–60).
Phase 3: First events (Days 61–90).
The two dates that gate everything else are the §2.1 charter filing and the 25-member threshold. If either slips, the 90-day charter date moves with it, so I'd put both on the calendar first.
Want me to break this into a week-by-week task list for the chapter lead, or draft the officer role descriptions from the bylaws?
The Nonprofit Chapter Starter Kit reads your bylaws, chapter handbook, and past launch notes in the Knowledge Center and drafts a plain, sequenced setup plan for a specific new city. Governance steps, membership setup, and the first few events, organized as a checklist a first-time volunteer can actually follow.
Upload your chapter handbook, bylaws, brand guidelines, and any past launch notes to the Knowledge Center so Joy grounds the kit in how your organization actually charters chapters.
Tell Joy the city, the rough member base, and any local constraints. Ask for the setup checklist and the timeline you want: 30, 60, or 90 days.
Joy returns a sequenced kit with governance, membership, and first-event steps. Tighten it with follow-ups like "add the insurance requirement" or "split the membership steps into weekly tasks."
Paste the kit into Google Docs, Word, or your project tool and share it with the chapter lead. Nothing is exported or sent for you. You place it where your team already runs launches.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
Governance, membership, and event tasks laid out in the order a new chapter should tackle them.
Uses your real bylaws, dues structure, and approval thresholds, cited to the handbook section they come from.
Ask for a 30-, 60-, or 90-day plan and Joy paces the tasks to fit the window.
Adapt any kit to local constraints with a follow-up instead of rewriting from scratch.
Tailor the plan for a student chapter with faculty advisor and academic-calendar steps.
Focus the kit on building the first volunteer roster and committee structure.
Draft the first-quarter fundraising and dues-collection steps for a new chapter.
Zoom in on planning the launch event, from venue checklist to member sign-up.
Upload your chapter handbook and bylaws to the Knowledge Center, then ask Joy for a starter kit for a specific city. It drafts a sequenced setup plan (governance, membership, and first events), grounded in your own rules, which you copy into your docs and run.
Your actual documents. Joy reads the bylaws, handbook, and any past launch notes you've added and cites the specific sections each step comes from, so the dues bands, member minimums, and approval thresholds are yours, not generic.
Yes. Tell Joy the window you want and it paces the governance, membership, and event tasks to fit. You can also ask it to break the plan into a week-by-week task list for the chapter lead.
No. Joy drafts the text in chat. You copy it into Google Docs, Word, or your project tool and share it yourself. Joy doesn't send email or post to channels on your behalf.
Save the ask as a custom command on your team's assistant. Then any staffer can run it for a new city, adjust the local details with a follow-up, and get a consistent kit every time.
Entre na lista de espera e seja o primeiro a experimentar este fluxo de trabalho quando o JoySuite for lançado.