Section 2b: Guest Intake Profile | USER STORY | Basic Information

## 🧩 Overview
We need to allow guests to provide their date of birth, gender identity, and optionally, their pronouns, to help program coordinators match them with hosts who can best support their needs and create a safe, respectful environment.

## 🧠 Problem Statement
Currently, guests do not have a way to share their gender identity, pronouns, or verify their age. These are critical inputs for making safe and appropriate host matches. Without this data, coordinators may struggle to ensure guests are placed in supportive environments that respect their identities.

## 🙋‍♀️ User Story
As a Guest,
I want to specify my date of birth and gender identity,
So that I can be matched with a host who can best meet my needs and provide a safe and comfortable environment.

## 🎯 Acceptance Criteria (Definition of Done)

- [ ] Guest can enter their date of birth in the format MM/DD/YYYY.
- [ ] System validates that guest is between 18 and 25 years old at time of submission.
- [ ] If outside range, a clear error message is shown and submission is blocked.
- [ ] Guest can select their gender identity from a predefined list.
- [ ] List includes an "Other" option for self-identification.
- [ ] List includes "Prefer not to say" option.
- [ ] Guest can optionally provide preferred pronouns in a free text input field.
- [ ] All inputs are stored in the backend database.
- [ ] Form validation prevents progression until required fields are correctly completed.

## 🔍 Context / Background

- Guest Wireframe – Basic Information
- Inclusive Language Resources:
- [Inclusive Language Guide 1](https://github.com/hackforla/HomeUniteUs/issues/877#)
- [Inclusive Language Guide 2](https://github.com/hackforla/HomeUniteUs/issues/877#)
- Design aligns with trauma-informed best practices and supports safety and identity validation in youth services.
- Addresses needs from stakeholder feedback around guest identity representation.

## 🖼️ Design Notes (Preliminary)

- Is this feature ready for design work? ✅Yes
- Design should follow accessibility standards and leverage existing form patterns used in the Guest Intake Form.
- Consider separating Date of Birth and Gender Identity into two screens or sections for clarity.

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

- #### In Scope:

- Inputs for date of birth, gender identity, and preferred pronouns
- Frontend and backend validation for age range
- Optionality in gender identity and pronoun responses

- #### Out of Scope (future or separate stories):

- Display of guest identity information to hosts
- Reporting or analytics related to demographics

## 🛑 Constraints / Risks / Workflow Dependency

- Must handle sensitive data respectfully and securely.
- Age validation logic must be robust and timezone-aware.
- Pronoun field must be optional and clearly labeled as such to avoid discomfort.
- Ensure this feature complies with data privacy regulations and internal data handling policies.

## ✅ Action Items

- #### Assign and Prep

- [ ] Product Manager: Understand, draft User Story and self-assign
- [ ] Product Manager: Conduct the necessary research (if applicable), clarify any questions
- [ ] Product Manager: Work with PM team/lead to clarify any questions about the User Story
- [ ] Product Manager: Work with Product Team Lead to assign the appropriate size & complexity
- [ ] Product Manager/Lead: determine if work should be split into multiple issues, if so, create issue(s) and link them in this issue (if applicable) or create as standalone

- #### Draft and Review:

- [ ] Product Manager: Change Issue Status to "In Progress"
- [ ] Product Manager: Draft User Story
- [ ] Product Manager: Change Issue Status to "For Review/Feedback Needed"
- [ ] Product Manager: Add Label "Ready for: Design Peer Review"
- [ ] Product 1st Level/Peer Review: Review and provide comment(s); tag assignee
- [ ] Product 1st Level/Peer Reviewer: Update status to "Questions/Clarification" if needed
- [ ] Product Manager (Assignee): Update status to "In Progress" and resolve comments
- [ ] Repeat steps as needed
- [ ] Product 1st Level/Peer Reviewer: Update to "For Review/Feedback Needed" and label "Ready for: Product Lead"
- [ ] 2nd final/Product Lead: Review and provide final feedback
- [ ] Resolve remaining comments

## 🔗 Related Tickets

- Design Ticket: [link]
- Engineering Ticket: [link]
- QA Test Plan: [link]

## 📎 Resources & References

- Guest Wireframe – Basic Information
- [Inclusive Language Resource 1](https://github.com/hackforla/HomeUniteUs/issues/877#)
- [Inclusive Language Resource 2](https://github.com/hackforla/HomeUniteUs/issues/877#)
- Mockups/Designs: [Guest Wireframe - Basic Information](https://www.figma.com/design/BNWqZk8SHKbtN1nw8BB7VM/HUU-Main-File---11%2F2024?node-id=17522-8504&t=9HUcBpMOpOt8fCAD-4)