Section 2b: Guest Intake Profile | USER STORY | Education

## 🧩 Overview
We need to **add fields for Guests to share their current educational status and/or future educational goals** in the Guest Profile form.
This will allow Coordinators to **better understand each guest’s academic background or aspirations**, helping them make more informed and supportive host-guest matches.

---

## 🧠 Problem Statement
Guests currently have no way to share information about their **educational background or future goals** in the system.
Without this information, Coordinators cannot consider educational compatibility or support needs during the matching process, which may lead to less effective pairings between hosts and guests.

---

## 🙋‍♀️ User Story
**As a** Guest,
**I want** to provide information about my current educational status and/or future educational goals,
**So that** I can be matched with a host who understands and supports my academic journey.

---

## 🎯 Acceptance Criteria (Definition of Done)
- [ ] **Education Status Selection:** The guest must be able to select whether they are currently enrolled in an educational program (Yes/No).
- [ ] If “Yes” is selected, a text field appears for the guest to describe their current educational program.
- [ ] If “No” is selected, a text field appears for the guest to describe their interest or plans for future educational enrollment.
- [ ] **Validation:** The system validates that all required fields are completed before submission.
- [ ] **Data Storage:** All responses are stored securely in the backend database and linked to the guest profile.
- [ ] **Review Access:** Coordinators can view this educational information as part of the guest’s profile in their dashboard.
- [ ] **Design Consistency:** Input fields use existing form and validation patterns from the design system.

---

## 🔍 Context / Background
- This feature enhances the **Guest Profile Form** to capture additional guest information for better host-guest matching.
- The goal is to improve match quality by including educational context.
- **Relevant Links:**
- Mockup: [Guest Wireframe - Education](https://www.figma.com/design/BNWqZk8SHKbtN1nw8BB7VM/HUU-Main-File---11%2F2024?node-id=17325-8835&t=9HUcBpMOpOt8fCAD-4)
- Stable Site: [homeunite.us](https://homeunite.us/)
- Beta Site: [dev.homeunite.us](https://dev.homeunite.us/)

---

## 🖼️ Design Notes (Preliminary)
- **Ready for Design:** ✅ Yes
- Follow existing **Guest Intake Form** style and interaction patterns (conditional questions and validation).
- Use **Material UI form components** and maintain consistency with current Guest Profile UI.
- Reference the linked Figma mockup for visual and interaction guidance.

---

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

**In Scope:**
- Adding educational status and goal questions to the Guest Profile form.
- Capturing and storing responses in the backend database.
- Displaying this data in the Coordinator dashboard.

**Out of Scope:**
- Automated matching based on education fields.
- Host-side educational information.
- Data analytics or reporting related to education.

---

## 🛑 Constraints / Risks / Workflow Dependency
- Must comply with data privacy and collection standards.
- Must remain **accessible and mobile-friendly**.
- Dependent on **backend schema update** to store educational data.
- Requires **API adjustments** before frontend integration.

---

### ✅ Action Items

**Assign and Prep**
- [x] Product Manager: Draft User Story and self-assign
- [ ] Product Manager: Confirm database support with Engineering
- [ ] Product Manager: Conduct research on existing Guest Profile structure
- [x] Product Team Lead: Review story size & complexity
- [ ] Create linked Engineering and Design tickets if necessary

**Draft and Review**
- [x] Product Manager: Change Issue Status to “In Progress”
- [x] Product Manager: Submit for Peer Review — add label `Ready for: Design Peer Review`
- [ ] Product Lead: Final review and approval before handoff
- [ ] Once approved, assign linked tickets to Design and Engineering

---

### 🔗 Related Tickets
- **Design Ticket:** _[to be added]_
- **Engineering Ticket:** _[to be added]_
- **QA Test Plan:** _[to be added]_

---

### 📎 Resources & References
- **Mockup:** [Guest Wireframe - Education](https://www.figma.com/design/BNWqZk8SHKbtN1nw8BB7VM/HUU-Main-File---11%2F2024?node-id=17325-8835&t=9HUcBpMOpOt8fCAD-4)
- **Design System / Brand Guidelines:** _[link]_
- **Related Work:** Guest Intake Form feature
- **Research Summary:** _[link if available]_

---