Product: Section 2b: Guest Intake Profile | USER STORY | Language Proficiency

## 🧩 Overview
We need to enable **Guests** to provide information about the **languages they speak** and their **proficiency levels**.
This feature ensures that Guests can be **matched with Hosts who can communicate effectively**, helping to create a more comfortable and supportive environment during their stay.

---

## 🧠 Problem Statement
Guests currently do not have a way to share their language preferences and proficiency levels.
This makes it difficult for coordinators to ensure language compatibility between Guests and Hosts, which can negatively impact communication, comfort, and safety during placements.

---

## 🙋‍♀️ User Story
**As a** Guest,
**I want** to provide information about the languages I speak and my proficiency levels,
**So that** I can be matched with a Host who can communicate with me effectively and make me feel more comfortable.

---

## 🎯 Acceptance Criteria (Definition of Done)
*Transfer information to Design to Engineering Issue to be checked off*
*These high-level criteria will be detailed further in Design and Engineering handoff templates*

- [ ] **Bilingual/Multilingual Status Selection:** Guest can indicate if they are bilingual or multilingual (Yes/No).
- [ ] **Language Selection:** If "Yes" is selected, Guest can list one or more languages they speak.
- [ ] **Proficiency Level Selection:** Guest can choose a proficiency level for each selected language from a predefined list (e.g., Basic, Intermediate, Fluent, Native).
- [ ] **Validation:** System validates that both language and proficiency level are selected before allowing submission.
- [ ] **Data Storage:** All language and proficiency data is saved correctly in the Guest profile.
- [ ] **Accessibility:** Form elements meet accessibility standards (e.g., label associations, screen reader compatibility).

---

## 🔍 Context / Background
Capturing language preferences helps create safer, more inclusive matching experiences for both Guests and Hosts.

- Research Summary: [link placeholder]
- Previous Discovery Work: [link placeholder]
- Related Epics or Projects: [Home Unite Us Guest Profile Epic – link placeholder]

---

## 🖼️ Design Notes (Preliminary)
- **Is this feature ready for design work?** Yes
- **Design Guidance:**
Use form components consistent with the existing Guest Intake Form and Material UI design system.
Input fields should follow the same layout patterns as other profile sections.

---

## 📌 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:**
- Addition of new “Language and Proficiency” section to Guest profile form.
- Data storage and retrieval for this information in backend.
- Validation logic for form submission.

**Out of Scope (future or separate stories):**
- Display of Guest language data in the Host or Coordinator matching interface.
- Updates to matching algorithm logic based on language compatibility.

---

## 🛑 Constraints / Risks / Workflow Dependency
- **Dependency:** Requires backend support for new language/proficiency fields in the Guest profile schema.
- **Risk:** Inconsistent data format if predefined proficiency levels are not standardized.
- **Consideration:** Must comply with data privacy and accessibility standards.

---

### Action Items

- **Assign and Prep**
- [x] Product Manager: Understand, draft User Story and self-assign
- [x] Product Manager: Conduct research (if applicable), clarify questions
- [x] Product Manager: Collaborate with PM Lead to size & scope
- [ ] Product Manager/Lead: Determine if multiple issues are needed and link them

- **Draft and Review**
- [x] Product Manager: Change Issue Status to "In Progress"
- [x] Product Manager: Draft User Story
- [x] Product Manager: Change Issue Status to "For Review/Feedback Needed"
- [x] Product Manager: Add Label "Ready for: Design Peer Review"
- [ ] Peer Reviewer: Review for completeness and tag assignee
- [ ] Product Lead: Final review and approval

---

### 🔗 Related Tickets
- Design Ticket: [link placeholder]
- Engineering Ticket: [link placeholder]
- QA Test Plan: [link placeholder]

---

### 📎 Resources & References
- Existing Research: [link placeholder]
- Brand Guidelines / Design System: [Material UI / HUU Design System – link placeholder]
- Previous or Related Designs: [Guest Intake Form Wireframe – link placeholder]