Builder episode · Community

A gathering with a calm backstage.

Turn one event idea into a practical brief, timeline, RSVP plan, run of show, and warm follow-up. Built from the method I use for Mamahood ATX.

Time: 45 minutes
Difficulty: Guided beginner
Tools: Claude or ChatGPT, calendar, form, shared document

01 · Ingredients

Start with the people, not the decorations.

A clear reason for gathering makes every later decision easier. Know who the event serves, what they should feel, and what practical care they need.

The purposeOne sentence describing why this gathering should exist

The peopleAudience, capacity, ages or stages, accessibility needs

The boundariesBudget, location, date range, weather plan, privacy

The helpersHost, check-in person, setup, cleanup, safety contact

02 · The method

Build the container, then make it beautiful.

AI is the planning assistant. A real person still confirms the venue, costs, safety details, accessibility, and every promise made to guests.

Write the one-page brief

8 minutes

Do not begin with a giant task list. Begin with a small decision document that keeps the team aligned.

Build the event brief

Turn my notes into a one-page community event brief.

Event idea: [ADD]
Who it serves: [ADD]
What I want people to feel or receive: [ADD]
Possible date, time, and location: [ADD]
Capacity: [ADD]
Budget: [ADD]
Accessibility, privacy, child, or safety needs: [ADD]
Available helpers: [ADD]

Organize it under: Purpose, Guest promise, Format, Logistics, Care and accessibility, Team, Open decisions. Do not invent missing information.

Make the backwards timeline

8 minutes

Plan from the event date backwards so outreach, supplies, reminders, and venue confirmations happen at the right time.

Create the timeline

Using the confirmed event brief, make a backwards planning timeline from [EVENT DATE] to today.

Include only necessary tasks for:
• Venue and permissions
• Registration and capacity
• Guest communication
• Supplies and food
• Accessibility and safety
• Volunteer assignments
• Weather backup
• Day-before confirmation
• Post-event follow-up

Give each task an owner, due date, and clear definition of done. Mark anything that requires human confirmation.

Build a respectful RSVP

8 minutes

Collect only what the event genuinely needs. Explain why sensitive information is being requested, keep it private, and share exact location details only when appropriate.

Draft the RSVP form

Draft a short RSVP form for this event using the brief above.

Include:
• Name and preferred contact
• Number attending
• Only the accessibility, dietary, child, or stage questions the event truly needs
• Consent for event updates
• A short privacy note explaining how answers will be used
• A waitlist question if capacity is limited

Avoid collecting medical details, children’s full names, home addresses, or anything unnecessary.

Create the host run of show

12 minutes

This is the page everyone working the event can follow. Include setup, guest arrival, transitions, closing, cleanup, and the plan if something changes.

Make the day-of plan

Create a practical run of show for this event from team arrival through final cleanup.

Use a table with: Time | What happens | Owner | Supplies | Guest-facing note | Backup plan.

Include:
• Setup and safety check
• Volunteer huddle
• Check-in and welcome
• Each event segment and transition
• Accessibility check-ins
• Closing announcement
• Cleanup and lost items
• Emergency and weather contacts as placeholders for me to fill in

Keep the plan calm, specific, and realistic.

Close the loop

9 minutes

Send a warm thank-you, share any promised information, and record three lessons while the event is fresh. That is what turns one gathering into a reusable system.

Write the follow-up

Write a warm, concise follow-up for attendees of [EVENT NAME].

Include:
• A genuine thank-you
• One specific moment or outcome from the gathering
• Any promised resource or next step
• A two-question feedback request
• The next way to stay connected, if relevant

Tone: human, community-first, and appreciative. No hype and no em dashes.

03 · Finish line

The plan is done when care is visible.

A beautiful event is not only how the table looks. It is how clearly guests are welcomed, how easily helpers can act, and how thoughtfully people are followed up with.

The purpose and guest promise fit in one sentence

Every task has an owner and due date

The RSVP collects only necessary information

Accessibility, privacy, safety, and weather are addressed

The host team has one run of show

Thank-you and lessons are completed within 48 hours

You have the full builder collection.

Return to all recipes →