First Steps on Your Church Journey
Start a Local Meetup Group
(Cost to start the group is tax-deductible)
BPW: How to Start a Meetup Group (before forming a branch church)
Start a local BPW meetup first. Only expand into a formal branch church after you have consistent attendance, reliable leadership, and stable norms.
Quick-start checklist
Set up (1–3 days)
-
Pick a name: “BPW / Imposition Ethics — [City]”
-
Write a 1-paragraph purpose + 5 bullet points of what happens
-
Choose a consistent cadence: biweekly is the default
-
Pick an accessible venue: library room / community center / quiet café
-
Publish the group + schedule the first 3 events immediately
Run (first 4 events)
-
Use the same agenda every time (predictability)
-
Moderate firmly (no derailments, no harassment, no coercion)
-
Collect opt-in emails
-
Track: RSVPs, attendance, return rate, and what confused newcomers
Scale (months 2–3)
-
Add 1–2 co-hosts
-
Rotate topics (principles + case studies)
-
Do one “newcomer night” per month
-
Begin discussing branch church only when readiness criteria are met
Step 1 — Define the meetup’s purpose (BPW-aligned)
One-sentence purpose (template)
-
“A local discussion and community group for BPW / Imposition Ethics: exploring consent-first ethics, reducing involuntary imposition, and building voluntary cooperation.”
Three promises (pick 3)
-
Structured, moderated discussion (not chaos debates)
-
Clear BPW framework (not vague spirituality)
-
Non-coercive culture (no pressure to join, donate, or agree)
-
Practical application to real-world dilemmas and institutions
-
Community and friendship for people who resonate with BPW
Step 2 — Create the group page (copy/paste templates)
Group description (copy/paste)
BPW / Imposition Ethics — [City]
We’re a local meetup for people interested in BPW (Imposition Ethics): a consent-first moral framework focused on minimizing involuntary imposition on conscious agents and maximizing voluntary cooperation.
What meetings are like
-
Short BPW concept/principle (10–15 min)
-
Moderated discussion (30–45 min)
-
Case study / real-world application (15–20 min)
-
Optional social time afterward
Culture
-
No pressure to speak, join, or donate
-
Respectful moderation (no harassment, no “gotcha” debates)
-
You’re free to disagree or leave at any time
Who it’s for
-
People curious about BPW ethics
-
People who want serious discussion without coercive religion culture
Group rules (short, enforceable)
-
Be respectful; no harassment or personal attacks
-
No manipulation, guilt, or pressure tactics
-
Stay on topic; moderators may redirect or end discussion
-
No recording/photos without explicit consent
-
Violations may result in removal
Step 3 — Schedule the first 3 events (important)
People hesitate to join “empty” groups. Having three events posted signals stability.
Recommended cadence
-
Biweekly (best for consistency without burnout)
-
Same day/time if possible
Recommended event titles
-
“Intro to BPW / Imposition Ethics (Newcomers Night)”
-
“Applying BPW to Real Moral Dilemmas (Case Studies)”
-
“Consent, Coercion, and Community: BPW in Practice”
Step 4 — Use a standard meeting format (75 minutes)
Default agenda
-
Welcome + what BPW is (5)
-
Principle/topic of the week (10–15)
-
Case study (15)
-
Moderated discussion (30–35)
-
Wrap-up + next event (5)
-
Optional social time (10+)
Facilitator scripts (use verbatim if you want)
-
“Participation is optional; listening is fine.”
-
“We’re here to understand BPW and apply it, not win debates.”
-
“If this isn’t your thing, no problem—no pressure.”
Step 5 — Make the meetup easy to find (without spam)
High-yield promotion (local)
-
Local Facebook groups (philosophy, community, secular, volunteering)
-
Local subreddit and city Discords (post once per event series, not daily)
-
Library/community center event boards
-
Partner events with adjacent groups (philosophy clubs, service orgs)
Posting style
-
Clear invitation
-
No urgency
-
No moral framing like “you should attend”
-
Emphasize safety + structure + topic
Step 6 — Get retention (the metric that matters)
Track these three numbers:
-
Attendance (not RSVPs)
-
Return rate (how many come back within 30 days)
-
Co-host pipeline (are leaders emerging?)
Simple retention moves
-
Start/end on time
-
Always explain the agenda upfront
-
Always announce the next meeting date before people leave
-
One follow-up message only (opt-in reminders)
Step 7 — When to expand from meetup → branch church
Only propose forming an official branch church after you reliably have:
Minimum readiness criteria
-
8–12 consistent attendees (not one-time RSVPs)
-
At least 2 reliable leaders (lead + backup)
-
Meetings held consistently for 6–8 weeks
-
No major unresolved conflicts
-
A stable venue plan for 2–3 months ahead
Transition language (BPW-aligned)
-
“If enough people want a more formal BPW branch church in this area, we can discuss it. No pressure; the meetup remains valid as-is.”
Event description template (copy/paste)
Title: [Topic] — BPW / Imposition Ethics [City]
Description:
We’ll do a short intro to the BPW framework, then apply it to a real scenario.
Agenda
-
BPW concept (10–15 min)
-
Case study (15 min)
-
Moderated discussion (30–35 min)
-
Wrap-up + next steps
Ground rules
Respectful discussion, no coercion/pressure, no recording without consent. Listening-only is welcome.
Who this is for
Newcomers and regulars. No prior knowledge required.
Estimate: suggest forming a BPW branch church when the meetup has ~15–30 “active members” and ~8–15 consistent weekly/biweekly attendees, sustained for 8–12 weeks, with 2–3 reliable leaders.
Membership counts on platforms are noisy; the decision should be driven by repeat attendance + leadership capacity, not total “joins.”
Recommended thresholds (use whichever is easiest to measure)
A) Attendance-based (most reliable)
-
Weekly meetup: 10–20 attendees per meeting for 8–12 weeks
-
Biweekly meetup: 8–15 attendees per meeting for 3–4 cycles (6–8 meetings)
B) Active-member-based (good second metric)
“Active” = attended at least 1 meeting in the last 30 days (or RSVPed and showed up).
-
15–30 active members is typically enough to justify a branch structure
-
Below ~15 active, a “church branch” often becomes a fragile label over a small discussion circle
C) Team capacity (non-negotiable regardless of size)
-
2 leaders minimum (Lead + Backup) who can run meetings without each other
-
Ideally 3–4 roles covered: Lead, Moderator, Admin/Treasurer, Safety/Conduct (can be combined early)
Quick decision rule
Form a branch church if all are true:
-
Consistency: meetings are happening on schedule (no cancellations) for 2–3 months
-
Critical mass: at least 8–15 regulars (people who attend repeatedly)
-
Leadership: at least 2 reliable leaders
-
Stability: no recurring conflicts, clear norms, and a working moderation process
-
Continuity: you can schedule the next 6–8 weeks right now (venue + hosts)
If any one fails, stay a meetup.
Pitfalls to avoid
-
Using “Meetup members” as the trigger (it inflates easily; doesn’t indicate commitment)
-
Branching with one charismatic organizer (high collapse risk)
-
Branching before norms are proven (conflict handling isn’t theoretical—test it first)
Simple templates (pick one and publish it)
Conservative policy:
-
“We consider forming a BPW branch church after 12 weeks of stable meetings with 10+ consistent attendees and 2+ leaders.”
Growth policy:
-
“We consider forming a BPW branch church once we have 20–30 active members and 8–15 regular attendees, with a stable leadership team.”
If you tell me whether your meetup will be weekly or biweekly, I’ll give you a single clean threshold sentence that matches that cadence.
BPW Branch Church Starter Guide
This page explains how to start a BPW branch church in your area: how to get chartered, run meetings, build a stable core group, and stay compliant with the central BPW organization.
What a BPW Branch Church is
A BPW branch church is a local community that:
-
Teaches and practices the BPW / Imposition Ethics framework
-
Meets on a reliable schedule
-
Operates with non-coercive norms (consent-first, no pressure)
-
Follows central governance + financial + safety standards
-
Uses BPW branding only when chartered/recognized
Quick-start checklist
Before you launch (1–2 weeks)
-
Pick a Branch Lead and 1 backup leader
-
Choose your meeting format (discussion / teaching / service / mixed)
-
Secure a consistent location (library room is ideal)
-
Publish a simple public page: what it is, what happens, next date, rules
-
Apply for charter (see below)
Launch phase (first 4 meetings)
-
Keep meetings small, structured, and consistent
-
Collect opt-in contacts (email list)
-
Track attendance + feedback
-
Recruit 2–3 volunteers (hosting, setup, moderation)
Stabilize (months 2–3)
-
Create a core team (Lead, Facilitator, Treasurer/Admin, Safety)
-
Run 2 “newcomer friendly” nights per month
-
Add one service/outreach activity per month (optional)
Step 1 — Get a BPW Branch Charter
A charter is a lightweight agreement that makes a branch “official,” sets expectations, and protects the mission.
Minimum requirements to be chartered
-
You affirm BPW doctrine (Imposition Ethics canon)
-
You follow BPW code of conduct and non-coercion norms
-
You agree to baseline governance and reporting (see below)
-
You agree to financial handling rules (no private benefit, transparent records)
-
You commit to consistent meetings (at least monthly)
What you submit to the central org
-
Branch name + city/region
-
Branch Lead + backup lead contact info
-
Meeting location plan + intended schedule
-
A 1-paragraph “what happens at meetings”
-
Agreement to branch standards (templates below)
Step 2 — Choose your branch format (pick one and keep it consistent)
Option A: Discussion Church (best for growth)
-
Short teaching (10–15 min)
-
Moderated discussion (30–45 min)
-
Q&A + social time (15 min)
Option B: Teaching Church (best for clarity/discipline)
-
Opening reading / principles (5 min)
-
Main teaching (25–35 min)
-
Structured Q&A (20 min)
-
Community announcements + invitations (10 min)
Option C: Service-First Church (best for public legitimacy)
-
Group service activity (60–90 min)
-
Reflection circle using BPW lens (20–30 min)
Rule: do not reinvent the meeting every week. People return for predictability.
Step 3 — Run meetings that feel safe and worth returning to
BPW meeting norms (non-coercion standard)
-
No manipulation, guilt, fear, or social pressure to join/donate
-
No aggressive “debate-bro” environment
-
No shaming people for leaving or disagreeing
-
Explicit consent norms for contact, photos, and follow-up
Recommended first-time attendee flow (2 minutes)
-
“Here’s what BPW is in one sentence.”
-
“Here’s what tonight looks like.”
-
“You can participate as much or as little as you want.”
Step 4 — Leadership structure (minimum viable team)
Required roles
-
Branch Lead: accountable for branch health + standards
-
Facilitator/Moderator: runs the room and enforces norms
-
Treasurer/Admin: handles money/admin logs (even if tiny)
-
Safety Officer (can be combined early): code of conduct, incident handling
Avoid early failure modes
-
Single-person control with no backup
-
Unmoderated discussion
-
Informal money handling
-
No conflict process
Step 5 — Financial and legal structure (how branches typically work)
You already have central 501(c)(3) status. Branches usually operate under one of these patterns:
Pattern 1: Branch as a program of the central org (simplest)
-
Donations flow to the central org and are allocated to branch activities.
-
Central org retains final control over funds and compliance.
This maps to standard “fiscal sponsorship” principles: the sponsor must maintain discretion/control over donated funds and ensure they’re used for exempt purposes.
Pattern 2: Separate local nonprofit (more autonomy, more admin)
-
Branch forms its own entity and seeks its own exemption (or other formal arrangement).
Pattern 3: Group exemption (only if already in place)
The IRS recognizes group exemptions for affiliated subordinates under a central organization, but new requests have been paused since June 17, 2020 pending updated guidance.
Important: Annual reporting rules depend on which pattern you use (e.g., a subordinate included in a central group return generally doesn’t file separately).
Step 6 — Branch reporting (lightweight, but mandatory)
Monthly (5 minutes):
-
Meeting dates held + attendance count
-
Any incidents / issues (even “none”)
-
Funds used + receipts logged (if any)
-
Next month’s planned topics/events
Quarterly:
-
Leader check-in with central org
-
Review branch health: retention, conflicts, outreach, financial clarity
Step 7 — Outreach that matches BPW (non-impositional growth)
Your goal is not “conversion pressure.” It’s informed invitation.
High-performing outreach channels
-
Local Facebook groups (philosophy, community, secular spirituality, volunteering)
-
Meetup-style listings (even if you also have your own site)
-
Eventbrite/Local library boards
-
Short clips explaining “what happens at a BPW meeting”
Outreach rules (BPW-aligned)
-
Say what you are, clearly
-
Invite participation without urgency
-
Make it safe to decline
-
Never frame non-attendance as moral failure
Templates (copy/paste)
Template A — BPW Branch Listing (public page text)
BPW Branch Church — [City]
We meet [weekly/biweekly/monthly] to study and practice BPW (Imposition Ethics): minimizing involuntary imposition on conscious agents and maximizing voluntary cooperation.
What happens at a meeting
-
Short teaching: one BPW principle or case study
-
Moderated discussion (no pressure to speak)
-
Community time + announcements
Who it’s for
-
People curious about BPW ethics and consent-first community
-
People who want serious discussion without coercive religion culture
Ground rules
-
Respect, consent, no harassment
-
No manipulation or pressure to join/donate
-
You can leave anytime, no hard feelings
Next meeting: [date/time/location]
Contact: [email / form]
Template B — Branch Charter (short form)
BPW Branch Charter — [City]
This branch agrees to:
-
Teach BPW / Imposition Ethics in good faith and not misrepresent the canon.
-
Maintain non-coercive community norms and enforce the code of conduct.
-
Use BPW branding only as an authorized branch and follow brand guidelines.
-
Follow approved financial handling procedures and keep transparent records.
-
Provide monthly branch reports and report serious incidents promptly.
-
Maintain at least two active leaders with succession continuity.
Signed: Branch Lead _________ Date _________
Template C — Standard Meeting Agenda (75 minutes)
-
Welcome + what BPW is (5)
-
Principle of the week (10)
-
Case study / dilemma / application (15)
-
Moderated discussion (30)
-
Announcements + next meeting (5)
-
Optional social time (10+)
Template D — Newcomer Follow-up (one message only)
Thanks for coming to BPW [City]. If you’d like reminders, reply “yes” and we’ll add you to the list. Next meeting is [date/time]. If BPW isn’t your thing, no worries.
Operating standards (non-negotiables)
-
No private benefit: money/resources must serve the mission, not individuals.
-
Financial control clarity: if operating under the central org, funds must remain under sponsor discretion/control with clear documentation.
-
Incident handling: document, de-escalate, protect attendees, escalate serious issues to central leadership.
30-day branch launch plan (minimal, reliable)
-
Week 1: charter request + location + publish listing
-
Week 2: first meeting (keep it simple, structured)
-
Week 3: second meeting + recruit 1 volunteer
-
Week 4: third meeting + create next month’s schedule (3 dates posted)
