Product: Section 2b: Guest Intake Profile MVP | EPIC

## 🧩 Overview
The **Guest Intake Profile** feature enables at-risk youth (Guests) to submit essential personal and background information through a structured, editable online form. This form is a critical step in facilitating safe and efficient matching between Guests and potential Hosts within the Home Unite Us (HUU) platform.

The outcome of this initiative is to deliver a complete, validated, and user-friendly intake experience — allowing Guests to provide necessary details while Coordinators efficiently review submissions for host matching.

---

## 🎯 Objective
To design, implement, and validate a **comprehensive Guest Intake Profile** that captures key information needed for host matching — ensuring data accuracy, user accessibility, and coordinator efficiency.

This effort contributes to HUU’s goal of creating a **scalable and secure intake process** for homeless youth seeking temporary housing.

---

## 🔍 Background / Context
The Guest Intake Profile is a central component of the onboarding flow for Guests within the HUU ecosystem. It aligns with HUU’s broader mission to create a scalable housing-matching platform for at-risk youth.

- The existing intake sections include: Contact Information, Basic Info, Upload Photos/Videos, Other Guests/Pets, Education, Employment, Language Proficiency, Substance Use, Mental Health, Interest in Being a Guest, About Me, and Digital Signature.
- Each section corresponds to a separate ticket linked under this Epic (see below).
- Guest wireframes and experience flows have been developed to guide design and development.

**References:**
- [Guest Wireframes (Section 1–3)](https://www.figma.com/design/BNWqZk8SHKbtN1nw8BB7VM/HUU-Main-File---11%2F2024?node-id=1982-17008&p=f&t=JIaxzrhvLRnXiUk7-0)
- [Guest Experience Workflow](https://www.figma.com/board/5umaDiU1AM4oygqiLs7f33/Guest-Experience-Flow?node-id=0-1&p=f&t=PWnnOSSa7j4bGG7X-0)

---

## 📝 Scope of Work
Deliver a complete Guest Intake Profile experience with the following components and behavior:

- [ ] Implement and connect the following sections:
- Contact Information (#865)
- Basic Information (#877)
- Upload Photos/Videos (#767)
- Other Guests/Pets (#879)
- Education (#880)
- Employment Information (#882)
- Language Proficiency (#884)
- Substance Use (#885)
- Mental Health (#886)
- Interest in Being a Guest (#887)
- About Me (#888)
- Digital Signature (#611)
- [ ] Enable save, edit, and validation capabilities across all form sections
- [ ] Ensure the guest can view submission status (“In Progress,” “Submitted,” or “Needs More Info”)
- [ ] Implement a “Needs More Info” feedback flow: (Future considerations - need to be discussed)
- Guest sees a **Needs More Info** status when a coordinator requests additional details
- Clicking the profile directs the guest to the first required edit (to be discussed with UI)
- Non-edit-required fields are locked
- Guest must complete all requested edits and re-sign before resubmission
- [ ] Ensure ADA-compliant accessibility and responsive UI

---

## 📎 Deliverables
- Functional Guest Intake Profile integrated within the HUU Guest Dashboard
- Validation logic and editable form components for all required sections
- Documented workflow for the “Needs More Info” feedback and resubmission process
- Updated Figma design annotations and Github links reflecting implemented sections

---

## 🧭 Success Criteria
- [ ] Guests can successfully complete, save, edit, and submit intake forms
- [ ] Coordinators can request additional information via the platform
- [ ] Guests can re-access, edit, and re-submit requested information seamlessly
- [ ] All intake data is validated and stored securely in the backend
- [ ] UX aligns with approved wireframes and accessibility standards
- [ ] Positive feedback from at least one pilot organization testing the flow

---

## 🛑 Risks / Dependencies
- Dependencies on backend API endpoints for Guest profile creation and update
- Coordination with Design for final form layouts and error states
- Dependency on Authentication flow (AWS Cognito) for Guest user sessions
- Risk of data loss or validation errors if form state handling is incomplete
- Timing dependency with other Epic sections (e.g., Guest Dashboard integration)

---

## ✅ Action Items
- [x] **Assignee:** Assign yourself to this issue.
- [x] **Assignee:** Move the issue from **Prioritized Backlog** to **In Progress**.
- [x] **Product Manager (Assignee):** Clarify open questions with Product Team Lead.
- [x] **Product Manager (Assignee):** Verify alignment with related Epic and sub-issues.
- [x] **Product Manager (Assignee):** Draft and submit for review.
- [ ] **Peer Review:** Validate scope and objectives.
- [ ] **Product Lead:** Approve or request revisions.
- [ ] **Finalize** issue for Design and Engineering handoff.

---

## 🔗 Related Tickets / Resources
**Epic:** Guest Intake Profile

**Sub-Issues:**
- Contact Information (#865)
- Basic Information (#877)
- Upload Photos/Videos (#767)
- Other Guests/Pets (#879)
- Education (#880)
- Employment Information (#882)
- Language Proficiency (#884)
- Substance Use (#885)
- Mental Health (#886)
- Interest in Being a Guest (#887)
- About Me (#888)
- Digital Signature (#611)

**Design Resources:**
- [Guest Wireframes](https://www.figma.com/design/BNWqZk8SHKbtN1nw8BB7VM/HUU-Main-File---11%2F2024?node-id=1982-17008&p=f&t=JIaxzrhvLRnXiUk7-0)
- [Guest Experience Workflow](https://www.figma.com/board/5umaDiU1AM4oygqiLs7f33/Guest-Experience-Flow?node-id=0-1&p=f&t=PWnnOSSa7j4bGG7X-0)