Section 2b: Guest Intake Profile | USER STORY | Other Guests/Pets

## 🧩 Overview
We’re adding functionality in the guest intake flow that allows guests to specify if they’ll be accompanied by other people or pets. This ensures hosts are fully informed and prepared for any additional household members during the stay.

## 🧠 Problem Statement
Guests currently can't share details about additional people or pets.
This can lead to misunderstandings, surprise guests, or hosts being unprepared, impacting safety and host experience.

## 🙋‍♀️ User Story
As a Guest,
I want to indicate whether others (people or pets) will stay with me and provide their details,
So that the host is aware and can prepare accordingly.

## 🎯 Acceptance Criteria (Definition of Done)

- [ ] Guest is asked “Will others join you?” (Yes/No).
- [ ] If “No”: user proceeds straight through intake.
- [ ] If “Yes”: prompt guest to enter Full Name, Relationship, Date of Birth for each added person; allow adding multiple entries.
- [ ] Guest is asked “Do you have pets coming?” (Yes/No).
- [ ] If “No”: user proceeds.
- [ ] If “Yes”: prompt guest to select Pet Type (Cat, Dog, Other) and provide breed/type details; allow multiple entries.
- [ ] Validation: if “Yes” selected and required fields are missing, show clear error and block submission.
- [ ] All related components are coded, tested, reviewed, and deployed.
- [ ] Documentation and mockups included, and feature deployed to target environment.

## 🔍 Context / Background

- The host homes initiative involves intentional matching of guests with proper context (e.g., roommates, pets).
- Guest Wireframe – Other Guests/Pets (attached in original issue)
- Tied to host homes pilot for improved coordination and safety.

## 🖼️ Design Notes (Preliminary)

- Is this ready for design? ✅Yes
- Use existing form patterns from the Guest Intake Form.
- Add expandable sections for additional guest and pet entries.

## 📌 Scope Considerations (In/Out Scope)

- #### In Scope:
- Intake form questions regarding additional people/pets.
- Local storage and transmission of supplied data.

- #### Out of Scope:
- Matching algorithm or advanced host preferences
- Admin dashboard enhancements

## 🛑 Constraints / Risks / Workflow Dependency

- Validation and UX: Ensure users can't submit incomplete data.
- Data privacy: Dates of birth and relationship details need secure handling.
- Form efficiency: Shouldn’t overwhelm guest flow.

## ✅ Action Items

- #### Assign and Prep
- [ ] PM: draft this formatted issue, self-assign
- [ ] PM: clarify any questions with team
- [ ] PM: work with Product Lead on sizing
- [ ] PM/Lead: determine if split into sub-stories

- #### Draft and Review
- [ ] PM: mark issue “In Progress”
- [ ] PM: draft user story (above)
- [ ] PM: change status to “For Review/Feedback Needed”, label "Ready for: Design Peer Review"
- [ ] Peer Review: assess completeness and comment/tag
- [ ] Peer Reviewer: label "Questions/Clarification" if needed
- [ ] PM: address feedback
- [ ] Repeat until approval
- [ ] Final Review: label “Ready for Product Lead”
- [ ] Product Lead Review & feedback
- [ ] Repeat until fully approved

## 🔗 Related Tickets

- Design Ticket: [link to design issue]
- Engineering Ticket: [link to backend/frontend issues]
- QA Test Plan: [link]

## 📎 Resources & References

- Host Homes Pilot Docs: [link]
- Mockups/Designs: [Guest Wireframe - Other Guests/Pets](https://www.figma.com/design/BNWqZk8SHKbtN1nw8BB7VM/HUU-Main-File---11%2F2024?node-id=16750-1212&t=MT6iDoPNwPGd8Y86-4)