Product: Section 2b: Guest Intake Profile | USER STORY | Substance Use

## 🧩 Overview
We need to **capture Guest lifestyle preferences** regarding **smoking, alcohol, and substance use** so that **Coordinators can make more compatible and supportive Host-Guest matches**.
This feature enables Guests to self-report these habits through the intake form, improving comfort, safety, and understanding during the Host matching process.

---

## 🧠 Problem Statement
Currently, the Guest intake form does not collect information about lifestyle factors such as smoking, alcohol, or substance use.
Without this information, Coordinators risk matching Guests and Hosts with incompatible lifestyles, potentially leading to discomfort or early match termination.
Collecting this data upfront helps improve matching quality and ensures a safer, more supportive environment for both Guests and Hosts.

---

## 🙋 User Story
**As a** Guest,
**I want** to provide information about my lifestyle preferences (smoking, alcohol, and substance use habits),
**So that** I can be matched with a Host that understands my lifestyle and can provide a comfortable and supportive environment.

---

## 🎯 Acceptance Criteria (Definition of Done)
- [ ] **Smoking Status Selection:** The Guest must be able to select whether they smoke cigarettes (Yes/No).
- [ ] **Alcohol Use Selection:** The Guest must be able to select whether they drink alcohol (Yes/No).
- [ ] If "Yes" is selected, the system prompts the Guest to indicate if they have concerns about their drinking (Yes/No).
- [ ] If "Yes," a text field appears for the Guest to explain their concerns.
- [ ] **Substance Use Selection:** The Guest must be able to select whether they use any other substances (Yes/No).
- [ ] If "Yes" is selected, the system prompts the Guest to indicate if they have concerns about their substance use (Yes/No).
- [ ] If "Yes," a text field appears for the Guest to explain their concerns.
- [ ] **Validation:** The system must validate that all required fields are completed before submission.
- [ ] **Data Storage:** The collected data must be stored securely in the backend and associated with the Guest’s profile.
- [ ] **UI Consistency:** The form should align with the existing Guest intake form design system.

---

## 🔍 Context / Background
Collecting lifestyle-related information helps Coordinators ensure that Host-Guest matches are comfortable and aligned in expectations. This section of the intake form complements other personal preference and compatibility questions.

- Research Summary: [_TBD – Add once created_]
- Previous Discovery Work: [_TBD – Add once created_]
- Related Epics or Projects: [_TBD – Add once created_]

---

## 🖼️ Design Notes (Preliminary)
- **Design readiness:** Yes — ready for design handoff.
- **Considerations:**
- Use consistent form components from the existing Guest Intake Form.
- Conditional question logic should mirror other multi-step conditional forms in the intake flow.
- Style should align with the [Material UI] design system used throughout the app.

---

## 📌 Scope Considerations (In/Out Scope)
- [Feature List](https://docs.google.com/spreadsheets/d/1uM287TOz20jnXPS4kRe0Dt5GlhnPbNRYBHHOxcamCJ0/edit?gid=343529642#gid=343529642) *Add/Update Feature List*
- [x] Added to [Feature List](https://docs.google.com/spreadsheets/d/1uM287TOz20jnXPS4kRe0Dt5GlhnPbNRYBHHOxcamCJ0/edit?gid=343529642#gid=343529642) and completed information accordingly.

**In Scope:**
- New intake form fields for smoking, alcohol, and substance use.
- Conditional question logic (nested Yes/No and text inputs).
- Frontend validation and backend data persistence.

**Out of Scope (future or separate stories):**
- Host-side preference collection.
- Admin/Coordinator review dashboard enhancements.

---

## 🛑 Constraints / Risks / Workflow Dependency
- Sensitive nature of questions — ensure respectful language and optional explanations.
- Data privacy — must comply with applicable privacy laws (e.g., anonymization and secure storage of sensitive lifestyle data).
- Dependent on existing Guest intake form architecture and backend schema updates.

---

### Action Items
- Assign and Prep
- [x] Product Manager: Understand, draft User Story and self-assign
- [x] Product Manager: Conduct necessary research (if applicable), clarify any questions
- [x] Product Manager: Collaborate with PM team/lead for scope and sizing
- [ ] Product Lead: Determine if work should be split into sub-issues and link accordingly

- Draft and Review
- [x] Product Manager: Change Issue Status to “In Progress”
- [x] Product Manager: Draft User Story and Acceptance Criteria
- [x] Product Manager: Change Issue Status to “For Review/Feedback Needed” and add label “Ready for: Design Peer Review”
- [ ] Product Peer Review: Validate that story captures objective/goal and supports Design & Dev handoff
- [ ] Iterate until comments are resolved
- [ ] Product Lead: Final review and label as “Ready for Product Lead”

---

### 🔗 Related Tickets
- Design Ticket: [_TBD – Add once created_]
- Engineering Ticket: [_TBD – Add once created_]
- QA Test Plan: [_TBD – Add once created_]

---

### 📎 Resources & References
- Existing Research: [_TBD – Add once created_]
- Brand Guidelines / Design System: [_TBD – Add once created_]
- Previous or Related Designs: [_TBD – Add once created_]