1.0 Executive Summary

What is SociBubble?

SociBubble is an algorithm-powered social connection tool that creates meaningful groupings at events based on personality compatibility and shared interests. Unlike traditional networking where people stick with those they already know or face awkward forced mingling, SociBubble uses data-driven matching to connect compatible individuals in structured small groups.

Event Format Overview

Key Success Metrics

• Participant signup rate: Target 40-60% of attendees
• Connection quality ratings: Post-event feedback from participants
• Host execution smoothness: Host feedback survey results

Staffing Requirements

2.0 Event Overview

The Problem We're Solving

At typical potlucks and community gatherings:

• People stick with those they already know
• Newcomers feel isolated and struggle to break into existing social circles
• Random groupings feel forced and awkward
• Meaningful connections happen by chance, if at all
• Introverted individuals find random mingling overwhelming

The SociBubble Solution

Our approach transforms this experience through five key steps:

1. Participants complete a 2-minute interest survey - Quick, engaging, and mobile-friendly via QR code
2. Algorithm matches people by personality compatibility - Not just shared hobbies, but compatible ways of thinking
3. Small groups (5-7 people) meet for structured connection time - Intimate enough for meaningful conversation, diverse enough for rich interaction
4. Activities include conversation, light games, or refreshments together - Multiple formats to suit different comfort levels
5. Feedback collected to continuously improve - Data-driven refinement of the matching algorithm and event format

Event Structure: Three Distinct Phases

Phase 1: Potluck (7:00-8:00 PM)

• Guests arrive, eat, and socialize normally on the right side of the venue
• Signup window for SociBubble (scan QR code on food tables)
• Front Desk person greets and pitches the concept with demo materials
• Left side of hall prepared for SociBubble (setup happens behind the scenes)
• Traditional potluck activities continue uninterrupted

Phase 2: Transition (8:00-8:20 PM)

• Guests briefly leave for another activity (typically prayer)
• Hosts finalize table setup, print scorecards, arrange seating
• Algorithm runs and groups are formed
• CRM process generates personality scorecards and table assignments
• Table coordinators adjust chairs and place materials
• Everything is prepared for guests' return

Phase 3: SociBubble Activity (8:20-9:00 PM)

• Guests return and find their assigned tables using the wall display
• Each person receives a scorecard showing their personality profile and interests
• 15-20 minutes of facilitated connection at tables
• QA facilitators circulate to support groups
• Feedback collection via QR codes
• Event concludes with thank you and cleanup

3.0 Room Layout & Setup

Venue Split: Two Zones

The venue is divided into two distinct zones throughout the event:

╔════════════════════════════════════════════════════════════╗
║                        VENUE LAYOUT                        ║
╠══════════════════════════════╦═════════════════════════════╣
║          LEFT SIDE           ║         RIGHT SIDE          ║
║   (SociBubble Activity Zone) ║       (Potluck Zone)        ║
╠══════════════════════════════╬═════════════════════════════╣
║                              ║                             ║
║  📍 Table 1                  ║  🍽️ Food Tables             ║
║  • Numbered flag             ║  • Signup QR codes          ║
║  • Feedback QR code          ║                             ║
║  • Chairs: 5 or 7+           ║  👥 General Seating         ║
║                              ║  • People eating            ║
║  📍 Table 2                  ║  • Socializing              ║
║  • Numbered flag             ║  • Traditional potluck      ║
║  • Feedback QR code          ║    activities continue      ║
║  • Chairs: 5 or 7+           ║                             ║
║                              ║                             ║
║  📍 Table 3                  ║                             ║
║  • Numbered flag             ║                             ║
║  • Feedback QR code          ║                             ║
║  • Chairs: 5 or 7+           ║                             ║
║                              ║                             ║
║  📍 Table 4 (NO NUMBER)      ║                             ║
║  • "Not Participating /      ║                             ║
║    Finished Early"           ║                             ║
║  • Feedback QR code only     ║                             ║
║  • Flexible seating          ║                             ║
║                              ║                             ║
╚══════════════════════════════╩═════════════════════════════╝

📚 Door Greeter / Front Desk Station (near entrance)
   • Demo materials (brochure, sample scorecard)
   • Optional: game samples for display

Setup Guidelines: General Rules

Table Specifications

Zone Separation Strategy

The two-zone system serves multiple purposes:

• Maintains potluck normalcy: People who don't sign up have an uninterrupted traditional experience
• Reduces pressure: Participation is clearly optional when zones are visually separated
• Enables parallel setup: SociBubble preparation happens without disrupting the potluck
• Creates focus: During the activity, participants aren't distracted by potluck activity
• Supports boundary monitoring: Easy to gently redirect people who cross zones

4.0 Host Roles & Responsibilities

Role Overview: Team Structure

Minimum Viable Team (3 People):

• Person A: Door Greeter → Boundary Monitor → Table Helper
• Person B: Announcer + Algorithm Coordinator (if tech-comfortable)
• Person C: Score Card Coordinator → Table Setup → QA Facilitator

Ideal Team (4 People):

• Person A: Door Greeter / Front Desk → Boundary Monitor
• Person B: Announcer
• Person C: Algorithm Coordinator
• Person D: Score Card Coordinator + Table Setup → QA Facilitator

4.1 Door Greeter / Front Desk

Primary Responsibilities

Phase 1: Greeting & Pitching (7:00-7:45 PM)

• Welcome guests at entrance
• Show demo materials: brochure + sample scorecard
• Explain SociBubble concept briefly
• Optional: Display sample games to excite guests
• Direct guests to scan QR code on food tables to sign up
• Answer questions about the activity

Phase 2: Transition (7:45-8:15 PM)

• Take break while algorithm runs
• Assist with table setup if needed

Phase 3: Guest Return & Activity (8:15-9:00 PM)

• Help returning guests find wall display
• Direct people to their assigned tables
• Monitor activity from distance
• Boundary monitoring: Keep left/right sides separate during activity
• Mention Table 4 option for early finishers
• Assist with feedback collection

Key Skills Needed

• Friendly, welcoming demeanor
• Comfortable explaining new concepts
• Ability to answer questions on the fly

Materials Needed

• Demo brochure (laminated sample)
• Sample scorecard (example of what participants receive)
• Optional: Sample games for display

4.2 Announcer

Primary Responsibilities

Phase 1: Announcements (7:15-7:45 PM)

• Make initial stage announcement (7:15-7:20 PM)
• Give "5 minutes until signup closes" warning
• Announce signup closure

Phase 2: Transition (7:45-8:20 PM)

• Standby / assist with setup if needed

Phase 3: Activity Launch (8:20-9:00 PM)

• Wait for guests to return and be seated
• Make official start announcement
• Give activity instructions (conversation/game directions)
• Announce 5-minute warning (8:50 PM)
• Wrap up activity, direct to feedback QR codes
• Thank participants and close event

Key Skills Needed

• Clear, confident speaking voice
• Comfortable on stage/microphone
• Good timing sense
• Ability to read the room

Materials Needed

• Microphone (if venue has PA system)
• Script reference card (see Chapter 6)

4.3 Algorithm Coordinator

Primary Responsibilities

Phase 1: Monitoring (7:15-7:45 PM)

• Monitor signup count in real-time
• Visual scan for duplicate entries (duplicate emails, identical data)
• Remove or flag duplicates before processing
• Decision point: Evaluate if enough people signed up
  • <5 people: Prepare to cancel or accommodate informally
  • 5-6 people: Marginal, proceed with caution (single table of 5)
  • 7+ people: Good to go
• Signal Announcer when to close signups

Phase 2: Processing (7:45-8:15 PM)

• Load verified data into local algorithm software (15-20 min)
• Run archetype mapping and compatibility calculations
• Generate groupings (groups of 5 or 7+ people)
• Export data for printing:
  • Simple view: Wall display (names + table numbers)
  • Advanced view: For table team (includes chair counts, archetypes)
  • Scorecards: Individual participant cards
• Communicate table assignments to Table Coordinators

Phase 3: Standby (8:15-9:00 PM)

• Available for troubleshooting
• Observe activity dynamics
• Take notes for improvement

Post-Event:

• Complete host feedback survey

Key Skills Needed

• Technical comfort with software
• Attention to detail (duplicate detection)
• Quick decision-making under time pressure
• Clear communication with team

Materials Needed

• Laptop with algorithm software installed
• Access to signup data (QR code survey responses)
• Printer access for generating outputs

4.4 Score Card Coordinator

Primary Responsibilities

Phase 2: Production (7:55-8:15 PM)

• Receive processed data from Algorithm Coordinator
• Print scorecards (5-10 min)
  • Each scorecard includes: Full name + Interest selections + Group size (if +1) + Table number
• Cut cards to size with graph blade slider (10-20 min)
• Organize cards by table number for easy distribution
• Hand off organized scorecards to Table Coordinators

Phase 3: Standby (8:15-9:00 PM)

• Observe activity
• Available for support

Post-Event:

• Complete host feedback survey

Key Skills Needed

• Precision cutting (graph blade slider)
• Organization (sorting cards by table)
• Time management (tight 20-minute window)

Materials Needed

• Printer + paper
• Graph blade slider (for cutting cards)
• Cutting mat
• Scorecards organized by table in advance

4.5 Table Coordinators

Primary Responsibilities

Phase 2: Table Setup (8:00-8:15 PM)

• Receive advanced view printout from Algorithm Coordinator
• Calculate how many chairs each table needs (groups of 5 or 7+)
• Adjust chairs at Tables 1, 2, 3 as needed
• Place corresponding scorecards on each table (pre-allocated spots)
• Place archetype brochures at each seat (1 per person)
• Hang simple view wall display for guests to reference
• Print extra copy of table assignments, leave on each table
• Set up Table 4 ("Not Participating / Finished Early") with sign and QR code

Phase 3: Activity (8:20-9:00 PM)

• Shared boundary monitoring (keep sides separate)
• Available for questions or support

Post-Event: Cleanup (8:55-9:05 PM)

• Collect archetype brochures (if reusable)
• Remove table number flags
• Remove QR code flags
• Collect extra materials
• Complete host feedback survey

Key Skills Needed

• Quick mental math (chair calculations)
• Organization (matching scorecards to tables)
• Physical setup ability

Materials Needed

• Table number flags (3 numbered, 1 unnumbered)
• Feedback QR code flags (4 total)
• Archetype brochures (50-60 pre-printed)
• Scorecards (organized by table)
• Extra printouts (table assignments reference)

4.6 QA Facilitator

Primary Responsibilities

Phase 3: Activity Monitoring (8:25-8:55 PM)

• Circulate between tables during 15-20 min activity
• Observe group dynamics
• Answer questions about archetypes or process
• Help facilitate if conversation stalls (offer prompts)
• Troubleshoot issues:
  • Wrong table
  • Confusion about activity
  • No-show participants (reassure table)
• Take mental notes for post-event debrief
• Direct early finishers to Table 4 if needed

Post-Event:

• Complete host feedback survey

Key Skills Needed

• Social awareness (reading group dynamics)
• Light facilitation skills
• Approachable demeanor
• Problem-solving on the fly

Materials Needed

• Conversation prompt cards (optional backup)
• Familiarity with archetype descriptions

4.7 Boundary Monitor

Primary Responsibilities

Goal: Keep right side (potluck) separate from left side (SociBubble) during activity

Who Does It:

• Usually Front Desk person after guests are seated
• Can be rotated among available team members
• Not strict enforcement—just gentle guidance

What to Do:

• Stand near the dividing line between zones
• If someone from right side crosses over:
  • Polite redirect: "Hey! The SociBubble activity is happening on the left side—are you looking for something?"
  • If they're just passing through: no problem
  • If they're disruptive: gently guide back to right side
• Maintain separation to keep activity focused

Key Skills Needed

• Friendly but firm presence
• Situational awareness

5.0 Complete Event Timeline

5.1 Setup Phase (Pre-7:00 PM)

All Team Members:

• Arrive 30 minutes early
• Place numbered flags on Tables 1, 2, 3
• Place "Not Participating / Finished Early" sign on Table 4
• Set feedback QR code flags on all 4 tables
• Set signup QR codes on right-side food tables
• Front Desk: Arrange demo materials near entrance
• Algorithm Coordinator: Test software and printer
• Score Card Coordinator: Prepare cutting station
• Quick team huddle: confirm roles and timing

5.2 Phase 1: Potluck & Signup (7:00-8:00 PM)

5.3 Phase 2: Processing & Setup (7:45-8:20 PM)

5.4 Phase 3: Activity (8:15-9:00 PM)

5.5 Post-Event (9:00-9:10 PM)

6.0 Scripts & Announcements

6.1 Front Desk Pitch Scripts

Setting: Guest enters, Door Greeter approaches warmly

Version 1: Full Pitch

Version 2: Quick Pitch (for rushed guests)

Common Questions & Responses

Q: "What if I don't want to do it?"

"Totally fine! The regular potluck happens as usual. This is just an optional add-on for people who want to try something new."

Q: "How does the algorithm work?"

"You pick 5-7 interests from a list—things like 'meditation,' 'coding,' 'nature,' whatever catches your eye. The algorithm maps those to personality archetypes and matches you with people who share similar ways of thinking. It's open-source, so it's all transparent if you're curious about the details."

Q: "What if I'm shy / introverted?"

"Honestly, people say it's actually easier than random mingling because you're already starting with common ground. Small groups feel less overwhelming, and everyone's in the same boat—trying something new together."

Q: "Do I need to prepare anything?"

"Nope! Just show up. We'll call your name later, hand you a scorecard, and you'll join your table. Everything's handled for you."

6.2 Announcer Scripts

Script 1: Initial Announcement (7:15-7:20 PM)

Setting: Stage/microphone, guests are eating and socializing

Script 2: 5-Minute Warning (7:30 PM)

Setting: Stage/microphone, guests still eating

Script 3: Signup Closure (7:35-7:45 PM)

Setting: Stage/microphone, closing the window

Script 4: Official Start Announcement (8:20 PM)

Setting: Guests have returned from other activity, most are present

Script 5: Activity Instructions (8:25 PM)

Setting: Everyone seated at tables, ready to begin

Script 6: 5-Minute Warning (8:50 PM)

Setting: Activity has been running for 20-25 minutes

Script 7: Wrap Up & Feedback (8:55 PM)

Setting: Activity concluding

6.3 Cancellation / Low Turnout Scripts

Setting: Less than 5 people signed up, activity needs to be canceled or modified

Option A: Cancellation (if <5 signups)

Option B: Informal Accommodation (if exactly 5 signups)

7.0 Materials & Equipment

Pre-Event Materials Checklist

Printed Materials

Signage & Flags

Technology & Equipment

Optional Materials

Setup Timeline for Materials

Equipment Details: Graph Blade Slider

The graph blade slider is essential for creating professional-looking scorecards. Here's the process:

1. Print scorecards on cardstock
2. Align paper on cutting mat
3. Use blade slider to cut individual cards
4. Organize by table number

8.0 Troubleshooting Guide

Issue 1: Low Signup Count (<5 people)

Problem: Not enough participants signed up to run full activity

Decision Tree:

• 0-4 signups: Cancel activity or offer informal table gathering
• 5 signups: Proceed with single table, keep it casual
• 6 signups: Marginal—consider combining into one group of 6 (unusual but workable)
• 7+ signups: Good to go

Solutions:

Prevention for Next Time:

• More aggressive Front Desk pitch
• Earlier announcement (7:10 PM instead of 7:15 PM)
• Incentivize signups (e.g., raffle, free refreshments)

Issue 2: Duplicate Signups

Problem: Person signed up multiple times (accidentally or intentionally)

Detection:

• Algorithm Coordinator does visual scan before processing
• Look for: duplicate emails, identical interest selections, same name with slight variations

Solutions:

• Remove duplicate entries before running algorithm
• Keep only one entry per person (most recent or most complete)
• If unsure, ask person directly during event

Issue 3: No-Show Participants

Problem: Someone signed up but didn't show up at their table

Impact: Table has empty seat, group feels incomplete

Solutions:

Prevention for Next Time:

• Send reminder announcement at 8:15 PM: "If you signed up, please head to your table now!"
• Have Front Desk person actively guide people to wall display

Issue 4: Person Can't Find Their Name on Wall Display

Problem: Participant claims they signed up but their name isn't on the list

Possible Causes:

• Didn't actually complete signup (closed form before submitting)
• Duplicate entry was removed
• Technical glitch

Solutions:

Issue 5: Person Goes to Wrong Table

Problem: Participant sits at table that isn't theirs

Detection:

• Scorecards don't match
• Person realizes mistake
• QA Facilitator notices during rounds

Solutions:

• Politely redirect: "Hey! Looks like you're at the wrong table. Check the wall display for your name—it'll show your table number."
• Help them find correct table quickly
• Keep it lighthearted to avoid embarrassment

Issue 6: Table Conversation Stalls

Problem: Group runs out of things to talk about or feels awkward

Detection:

• QA Facilitator notices long silences
• People looking at phones
• Uncomfortable body language

Solutions:

Prevention for Next Time:

• Provide printed conversation starter cards at each table
• Include more explicit icebreaker instructions in announcements

Issue 7: Boundary Violations (Right Side Enters Left Side)

Problem: People from potluck side wander into SociBubble zone during activity

Causes:

• Curious about what's happening
• Looking for someone
• Don't realize zones are separate

Solutions:

Prevention:

• Clearer physical boundary (rope, cones, or tape line)
• Announcer mentions separation during instructions

Issue 8: Technical Failure (Printer, Software, etc.)

Problem: Algorithm software crashes, printer jams, or other technical issue

Backup Plan:

Issue 9: Time Runs Over

Problem: Activity goes longer than planned (past 9:00 PM)

Causes:

• Setup took longer than expected
• Guests arrived late
• Conversations are really engaging

Solutions:

Prevention for Next Time:

• Tighter adherence to timeline
• Set phone alarms for key milestones
• Build in 5-minute buffer

Issue 10: Participant Complaint About Matching

Problem: Someone unhappy with their table assignment or compatibility

Possible Complaints:

• "I don't fit with this group"
• "My archetype doesn't match me"
• "We have nothing in common"

Solutions:

9.0 Post-Event Procedures

Immediate Post-Event (9:00-9:10 PM)

1. Host Feedback Survey

Who: All team members

What: Complete host feedback survey immediately while event is fresh

Survey Includes:

• Role selection (dropdown)
• Timeline adherence (did we stick to schedule?)
• Material sufficiency (did we have everything we needed?)
• Technical issues (any software/printer problems?)
• Team communication (how well did we coordinate?)
• Suggestions for improvement

Why: Captures real-time insights before memory fades

2. Quick Verbal Debrief

Who: All team members

What: 3-5 minute huddle

Discussion Points:

• What went well?
• What was challenging?
• Any surprises or unexpected issues?
• Should we change anything for next time?

Keep it brief: Formal retrospective can happen later

3. Cleanup & Material Collection

Who: Primarily Table Coordinators, but all team helps

Tasks:

• Collect archetype brochures (if reusable)
• Remove and store table flags
• Remove and store QR code flags
• Collect extra printed materials
• Pack up cutting station
• Store equipment (laptop, printer, etc.)

Storage: Organize materials in clearly labeled containers for next event

Within 48 Hours Post-Event

1. Participant Feedback Analysis

Who: Algorithm Coordinator or designated data analyst

Tasks:

• Download all participant feedback responses
• Identify trends:
  • Average connection quality rating
  • Most common positive feedback
  • Most common complaints or suggestions
• Flag any serious issues for immediate attention

Deliverable: Summary report for board

2. Host Feedback Analysis

Who: Event organizer or board member

Tasks:

• Review all host feedback surveys
• Identify operational bottlenecks
• Note team suggestions
• Assess timeline adherence

Deliverable: Summary report with recommendations

3. Algorithm Performance Review

Who: Algorithm Coordinator

Tasks:

• Evaluate matching accuracy based on feedback
• Identify any systematic errors (e.g., consistently poor matches for certain archetypes)
• Document technical issues
• Propose algorithm adjustments if needed

Deliverable: Technical notes for improvement

Within 1 Week Post-Event

1. Full Team Retrospective (Optional but Recommended)

Who: All team members, board members (optional)

Format: 30-45 minute meeting

Agenda:

1. Review participant feedback summary
2. Review host feedback summary
3. Discuss what worked well
4. Discuss what to change
5. Assign action items for next event

2. Update Operations Manual

Who: Event organizer

Tasks:

• Incorporate lessons learned
• Update scripts if needed
• Revise timeline if adjustments necessary
• Add new troubleshooting scenarios encountered

Goal: Continuously improve this document

3. Material Restocking

Who: Event organizer or logistics coordinator

Tasks:

• Reprint archetype brochures if depleted
• Replenish scorecard paper
• Replace any damaged equipment
• Order new materials as needed

Goal: Be ready for next event with minimal scramble

Long-Term Post-Event

1. Trend Analysis (After 3-5 Events)

Who: Algorithm Coordinator + Board

Tasks:

• Aggregate feedback across multiple events
• Identify consistent patterns (what always works? what never works?)
• Measure improvement over time
• Assess whether SociBubble is achieving its goals

Questions to Answer:

• Are connection quality ratings improving?
• Is signup rate increasing?
• Are hosts getting more comfortable with execution?
• Should we make major changes to format or algorithm?

2. Community Outreach

Who: Event organizer or marketing lead

Tasks:

• Share success stories (with permission)
• Post photos or highlights on social media
• Encourage word-of-mouth
• Build excitement for next event

Goal: Increase awareness and participation

10.0 Appendices

Appendix A: Table Assignment Examples

Example Wall Display (Simple View)

This is what participants see when they return at 8:20 PM:

┌─────────────────────────────────────┐
│     SOCIBUBBLE GROUPINGS            │
│        January 12, 2026             │
├─────────────────────────────────────┤
│                                     │
│  TABLE 1                            │
│  • Alice Johnson                    │
│  • Bob Martinez                     │
│  • Carol Wang                       │
│  • David Kim                        │
│  • Emma Thompson                    │
│                                     │
│  TABLE 2                            │
│  • Frank Rodriguez                  │
│  • Grace Lee                        │
│  • Henry Patel                      │
│  • Iris Chen                        │
│  • Jack O'Brien                     │
│  • Kelly Singh                      │
│  • Leo Martinez                     │
│                                     │
│  TABLE 3                            │
│  • Maya Washington                  │
│  • Nathan Foster                    │
│  • Olivia Jones                     │
│  • Paul Hernandez                   │
│  • Quinn Taylor                     │
│                                     │
└─────────────────────────────────────┘

Key Features:

• Simple, clean layout
• Just names and table numbers
• Easy to scan quickly

Example Advanced View (For Table Coordinators)

This is what Table Coordinators receive for setup:

┌─────────────────────────────────────────────────────────┐
│          SOCIBUBBLE SETUP GUIDE                         │
│             January 12, 2026                            │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  TABLE 1 - 5 People (5 chairs needed)                  │
│  Primary Archetype: Creator/Explorer Mix               │
│  ────────────────────────────────────────               │
│  • Alice Johnson (Creator)                              │
│  • Bob Martinez (Creator)                               │
│  • Carol Wang (Explorer)                                │
│  • David Kim (Explorer)                                 │
│  • Emma Thompson (Creator)                              │
│                                                         │
│  TABLE 2 - 7 People (7 chairs needed)                  │
│  Primary Archetype: Connector/Caregiver Mix            │
│  ────────────────────────────────────────               │
│  • Frank Rodriguez (Connector)                          │
│  • Grace Lee (Connector)                                │
│  • Henry Patel (Caregiver)                              │
│  • Iris Chen (Connector)                                │
│  • Jack O'Brien (Caregiver)                             │
│  • Kelly Singh (Connector)                              │
│  • Leo Martinez (Caregiver)                             │
│                                                         │
│  TABLE 3 - 5 People (5 chairs needed)                  │
│  Primary Archetype: Thinker/Achiever Mix               │
│  ────────────────────────────────────────               │
│  • Maya Washington (Thinker)                            │
│  • Nathan Foster (Achiever)                             │
│  • Olivia Jones (Thinker)                               │
│  • Paul Hernandez (Achiever)                            │
│  • Quinn Taylor (Thinker)                               │
│                                                         │
└─────────────────────────────────────────────────────────┘

Key Features:

• Shows chair counts explicitly
• Includes archetype info for context
• Helps Table Coordinators understand groupings
• Not shown to participants

Appendix B: Algorithm Overview

For board understanding—not essential for host execution

How Matching Works

Step 1: Interest Selection

• Participant selects 5-7 interests from curated list
• Examples: meditation, coding, nature, art, fitness, cooking, etc.

Step 2: Archetype Mapping

• Algorithm maps interests to personality archetypes
• Archetypes include: Creator, Explorer, Connector, Caregiver, Thinker, Achiever, etc.
• Each interest has weighted associations with multiple archetypes

Step 3: Compatibility Calculation

• Algorithm calculates compatibility scores between all pairs of participants
• Compatibility based on archetype alignment (not identical interests)
• Goal: Group people who think similarly, not who do identical activities

Step 4: Grouping

• Algorithm forms groups of 5 or 7+ people
• Maximizes average compatibility within each group
• Ensures even distribution

Step 5: Output Generation

• Exports simple view (names + table numbers)
• Exports advanced view (includes archetypes + chair counts)
• Generates individual scorecards

Why Open Source?

• Transparency: Anyone can inspect the matching logic
• Trust: Participants can verify the algorithm isn't biased
• Improvement: Community can contribute enhancements
• Education: People can learn how personality mapping works

Appendix C: Emergency Contact List

To be filled in by event organizer

Emergency Scenarios

• Host No-Show: Call backup person listed above
• Technical Failure: Contact Tech Support immediately
• Venue Issue: Contact Venue Contact for resolution
• Medical Emergency: Call 911, then notify Event Organizer

Document Version History

Acknowledgments

This operations manual was developed through collaborative input from:

• SociBubble development team
• Event hosts and facilitators
• Community feedback
• Iterative testing and refinement
• Architectural planning discussions emphasizing step-by-step coordination and systemization

For Questions or Suggestions:

Contact: [EVENT ORGANIZER EMAIL]