Overview

One new funding source is being added and two funding sources are being retired.

For the retired funding sources, ClientTrack has taken a new approach to ensure retired funding sources remain for historical purposes. When a funding source is retired, it will be retitled with (RETIRED) at the end of the component. Additionally, that funding source will be available to see for existing funding source records, but it will not be available for selection moving forward. Please see images below for what these funding sources will look like. 

Updates Made in ClientTrack

New: HUD: CoC - CoC Builds

Retired: HUD: HOPWA-CV

Retired: HUD: ESG-CV

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

The label for the Hispanic/Latina/o list option has been updated from Hispanic/Latina/e/o to Hispanic/Latina/o. 

Updates Made in ClientTrack

The label for Hispanic/Latina/o will be updated in the baseline Race & Ethnicity drop-down list (ListID 2591) and within the HMIS 2026 Race Compliance Crosswalk. Additionally, the label for Hispanic/Latina/o will be updated in the FY2026 APR/CAPER (Questions 12, 22f, 22g, and 23e), the FY2026 PATH Annual Report (Q26c), and the column header in the Client.csv of the FY2026 HMIS CSV Export. 

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

HUD has announced the retiring of the Gender and Sexual Orientation from the Data Dictionary. Communities may continue to collect this information at a local level, but all HMIS forms will have the required elements made visible and available, but not required. 

Updates Made in ClientTrack

3.06 / Gender - Historical data will remain available for end users to review and access. The HMIS Intake form (FormID 5046) will be updated to make Gender available but not required. Other impacted forms include the Family Members form (FormID 5088), HMIS family Enrollment sub-form (FormID 5063), and the Add Family Member form (FormID 4622).

FormID 5330 / Basic Client Information

FormID 5088 / Family Members

R3 / Sexual Orientation - Historical data will remain available for end users to review and access. The RHY Entry Assessment form (FormID 5050) has been updated to make Sexual Orientation available, but not required.

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

The FY2026 Data Dictionary clarifies that Date of Engagement is also necessary for Street Outreach projects funded by HUD: CoC - YHDP to collect. 

Applicable Funding Sources & Project Types for the Date of Engagement element:

Updates Made in ClientTrack

There was no change necessary to the existing enrollment form (FormID 5063), as it already makes Date of Engagement visible and required for all Street Outreach projects. Please see an example of our testing below.

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

HUD has introduced a new element, 4.21 / Sex. This new element will be collected for all clients at record creation for the funding sources outlined below. HUD has also been very clear in their direction that this element is distinctly different from the retired Gender element and no mapping will be done as part of the Data Standards Update. The allowable response options for this element are:

• 0 / Female
• 1 / Male
• 8 / Client doesn't know
• 9 / Client prefers not to answer
• 99 / Data not collected

Applicable Funding Sources & Project Types for the Sex data element:

Updates Made in ClientTrack

Because this new element is required based on program and funding source combination, it will need to be available for collection in multiple locations. The new element, Sex, will be added to the Client Intake (FormID 5046), HMIS Family Member form (FormID 5088), HMIS Family Enrollment sub-form (FormID 5063) and Add Family Member form (FormID 4622). The element will be stored in a new column of the cmClient table called SexAtBirth. A new drop-down list will be created to allow end users to select from one of the 5 defined list options.

Users will see the Sex data element as visible and available on the Client Intake form and HMIS Family Member forms, but not required. This element won't be required on these forms because there is no direct tie to a program and funding source to make the element required.

Users will see the Sex data element as visible and conditionally required on the HMIS Family Enrollment sub-form (FormID 5063). At this step of the HMIS Intake, the user will have selected the Program to enroll the client and family into, so that project type and funding source will be used to determine if the element if just visible and available, or required. 

Please Note: Screenshots will be added when the updates in ClientTrack have been tested and completed.

FormID 5088 / Family Members

FormID 5333 / HUD Program Enrollment & FormID 5331 / Family Enrollment sub-form

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

A new service type, 10 / Healthcare Navigation, has been added to the allowable SSVF Type of Service.

Updates Made in ClientTrack

The new service type, Healthcare Navigation, has been added to the report mappings drop-down list (ListID 3070) on the baseline Service Setup (FormID 1188). Users will be able to map any service to Healthcare Navigation to begin collecting the relevant information. 

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

HUD has added an additional date field, Information Date, to be collected when collecting services mapped to SSVF Financial Assistance. 

Updates Made in ClientTrack

A new table that joins to the Services table is being created to capture the Information Date when the service selected is mapped to an SSVF Financial Assistance service type. This field will be present on the baseline services forms, FormID 4338 - Quick Service, FormID 4337 - Services, FormID 4339 - Quick Services for Multiple Clients.

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

Two dependent questions (Dependencies P & Q) of the V7 / HP Targeting Criteria element have had text updates.

Updates Made in ClientTrack

FormID 5080 / 2024 HMIS HP Target Criteria is being copied to create a 2026 version that will display the updated language. 

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

A new element, Mental Health Consultation, has been added for VA funded projects to be collected at start for heads of households and veterans. This element offers four response options to the primary question of Mental Health Consultation Status. The four allowable response options are:

• 1 / Mental health consultation completed
• 2 / Mental health consultation being coordinated/arranged with VA provider
• 3 / Mental health consultation being coordinated/arranged with other provider
• 4 / Offer declined

Updates Made in ClientTrack

Additional details will be added soon.

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

HUD updated the allowable response options for this element to include 8/Client doesn't know, 9/Client prefers not to answer, and 99/Data not collected.

Updates Made in ClientTrack

The update has been made to change the drop-down list to ListID 2040. Changes can be viewed on FormID 3756 / Critical Issues which is a sub-form of the RHY Entry Assessment form.

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

The Data Quality Report has two changes made for the FY2026 version. The row for Gender in DQ2 - Personally Identifiable Information (PII) has been retired to align with the retiring of the Gender data element in the Data Dictionary. Additionally, DQ7 - Inactive Records: Street Outreach and Emergency Shelter has update which project types should be considered for each row.

• Remove project type 1 from active/inactive in row 2
• Add project type 6 if PATH-funded to active/inactive in row 2

Updates Made in ClientTrack

The row for Gender will be removed from the viewer and drill-down values in the HUD DQR in ClientTrack. Additionally, the logic for DQ7 will be updated to align with the Reporting Glossary specifications for which project types to consider in each row.

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

The CoC APR & ESG CAPER has a few changes made for the FY2026 version changes. First, to align with the Data Quality Report updates, the row for Gender in DQ2/Q6a - Personally Identifiable Information (PII) has been retired to align with the retiring of the Gender data element in the Data Dictionary. Additionally, DQ7/Q6f - Inactive Records: Street Outreach and Emergency Shelter has update which project types should be considered for each row.

• Remove project type 1 from active/inactive in row 2
• Add project type 6 if PATH-funded to active/inactive in row 2

The following questions, referencing Gender, have been retired:

• Q10a
• Q10d
• Q24c
• Q25c
• Q26c
• Q27c

The following questions will be updated with the new label for Hispanic/Latina/o:

• Q12
• Q22f
• Q22g
• Q23e

Updates Made in ClientTrack

The retired questions will be removed and the new question will be added to the APR/CAPER CSV Export, APR/CAPER Viewer, APR/CAPER Drill-Downs, and Detail/Validation files. 

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview

The Coordinated Entry APR (CE APR) has a few changes made for the FY2026 version changes. First, to align with the Data Quality Report updates, the row for Gender in DQ2/Q6a - Personally Identifiable Information (PII) has been retired to align with the retiring of the Gender data element in the Data Dictionary. 

Updates Made in ClientTrack

The updated questions will be updated in the CE APR CSV Export, CE APR Viewer, CE APR Drill-Downs, and Detail/Validation files. 

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview & Updates Made in ClientTrack

Updated Q26a to remove Gender related questions, added a new sub-question, Q26l, to capture the Sex related information, and updated the label for Hispanic/Latina/o in Q26c. These updates will be made in the Formatted Report, the PATH Annual CSV Export, the Drill-Downs, and Detail/Validation files.

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview & Updates Made in ClientTrack

Export.csv - 

The Export.csv is being updated to allow for multiple CoC codes to be selected & passed through to the SourceID column. This change will involve updating the CSV Export procedure and creating a new version of the report launch form to make the CoC filter a multi-select field.

Client.csv - 

The Client.csv is being updated to remove the columns relating to Gender, adding in a new column for the new Sex data element, relabeling the column header for Hispanic/Latina/o to align with the FY2026 Data Dictionary, and ensuring that all veteran related elements are null for non-veterans. Please see the updates above for front-end ClientTrack changes being made to accommodate these changes.

Enrollment.csv - 

The Enrollment.csv is being updated to remove columns relating to Sexual Orientation, adding in a new column for the new Mental Health Consultation element, and ensuring that the updated values for R13 can accept the expanded list values of 8/Client doesn't know, 9/Client prefers not to answer, and 99/Data Not Collected. Please see the updates above for front-end ClientTrack changes being made to accommodate these changes.

Services.csv - 

The Services.csv is being updated to add additional logic for the Date Provided field when the record is an SSVF Financial Assistance service type. Please see the updates above for front-end ClientTrack changes being made to accommodate these changes.

CurrentLivingSituation.csv - 

The CurrentLivingSituation.csv is being updated to allow for 200 characters, an increase from the previous 100 allowable characters, in the Verified By column. There will be no front-end change in ClientTrack for this change.

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Overview & Updates Made in ClientTrack

Measure 3 -

Measure 3 is being updated to use Active Client Method 5: 1+ Nights Active. Previously, the SPM was using Method 3. The primary difference between Method 3 and Method 5 is that housing projects do not require a housing move in date before the report end date to be included.

Measure 4 -

Measure 4 is being updated to also include clients with enrollments into projects funded by 6/HUD: CoC - Safe Haven and 56/HUD: CoC Builds funding sources. 

Measure 7 -

Measure 7 is being updated for the table shell, row 3 of Measure 7a1. 
The previous language read: “Of persons above, those who exited to temporary and some institutional destinations”. 
The updated language reads: “Of persons above, those who exited to specific homeless, temporary, and institutional destinations”.

SPM Data Quality -

The Data Quality section of the System Performance Measures was clarified via community AAQ after final submission for the SPM due in early 2025. The DQ section is being updated to deduplicate enrollments by each project type, not across all project types. 
A quick example: If a client is enrolled in both an Emergency Shelter and a Rapid Re-Housing project, in previous SPMs, the client would have been included in only one of those project types for the Data Quality portion. With the updated clarification, the client would be included in both of those project type counts.

These updates have not yet been deployed to customer environments. Screenshots are included to orient end users to where the updates will be seen upon deployment.

Impact Reports

Q: Will impact reports be sent by CaseWorthy and if so when should we expect them?
A: The Form & Workflow Comparison Tools are taking the place of the Impact reports this year and were deployed to customer environments on July 15, 2025. No impact reports will be shared out for this year. Please see the Form & Workflow Comparison Tools article for more information on how these tools work. 

Q: Where are the Impact Comparison tools in the system?
A: The comparison tools can be found by navigating to: Home Workspace > Global Administration > Data Management Tools > Comparison Tools

MH Consultation

Q: Did you say MH consultation is for SSVF only?
A:  MH Consultation is required for SSVF funded projects and VA: GPD funded Case Management/Housing Retention project types. Please see above for more details on the new Mental Health Consultation element. 

Gender & Sex

Gender & Sex - Data Collection Updates

Q: Will Gender still be available to use?
A: Gender will still be available in the system with all historical data, but will not required in the system as of 10/1/2025.

Q: Is HUD not looking to collect gendered data?
A: HUD has retired the Gender data element at this time. 

Q: Is Sex going to be in recorded on the client level or on a enrollment/assessment level?
A: Sex is a client level element and will be stored on the cmClient table.

Q: Why did Eccovia/CaseWorthy decide to add the Sex field to the Edit Client form, since it is going to be program/funding specific?
A: Because Sex is a client level element and it's added to the cmClient table, we wanted to ensure Sex was available to collect on the demographics form alongside the other demographics. Because the field requirement depends on program & funding source combinations however, the compliance enforcement has to occur later in the workflow. To accommodate the requirement & compliance enforcement, Sex is also being added to the HUD Program Enrollment form.

Q: Will Gender be available but not required on the HMIS Client Info form?
A: Yes, Gender will be available but unrequired on the HMIS Client Information form. 

Q: If we make Sex universally required on the client intake, can we remove it from the enrollment screen?
A: Yes, if your community chooses to customize the Client Intake form and makes Sex required for all clients, you could choose to remove it from the Enrollment screen. If your community is pursuing this customization, also ensure the Sex field is set to required on the Family Members form, otherwise it will only be collected & required for heads of households.

Q: Is Sex always blank, or does it prepopulate with the last data entry answer
A: Sex should prepopulate with the last data entry answer as this is a client level element, not an enrollment based element. 

Q: Knowing HUD has instructed vendors to not map Gender to Sex, can customers request mapping or conversion to reduce data-entry burden?
A: This has been asked to HUD TA and we have no received a clear answer or direction. This can be a conversation, but we will need to involved HUD TA to get a final sign-off.

Gender & Sex - Reporting Updates

Q: Will Sex be included in the Data Quality portion of the HUD DQR, CoC-APR & ESG-CAPER?
A: No. Sex will not be included in the Data Quality report at all. 

Q: If we answer "does no know" or "refuses" to the sex will it give us an error on the DQR?
A: No, there will be no inclusion of Sex to the Data Quality Report.

Q: Where does Sex replace Gender in the APR, etc.?
A:  Gender and Sex are different elements, so there is no replacing Gender with Sex. Sex will be added as it's own, new question on the APR/CAPER (Q24e). As of July 2025, Sex will not be included in the APR/CAPER for FY2026. Please see the APR/CAPER Reporting updates above for more details. 

Q: How will clients who are already in the system be reported on the CAPER?  For example, if there is a client already in the system with a gender that is neither M or F, how will their sex be reported?
A: There is no mapping between Gender & Sex. So if a client has any gender, that will not be included in the APR/CAPER. Sex is a new element that will have a fresh start to begin collecting on October 1, 2025.

Q: Can you please talk through how gender and sex will work in the housing workspace? Right now you can limit who can stay by gender, will we also be able to limit by sex?
A: As it stands, Sex is not being added to the Housing Workspace. Because the Gender requirement is only updated for federally funded projects, ClientTrack still needs to maintain Gender links to baseline functionality for non-federally funded customers. The ClientTrack Product Team will be looking to collaborate with communities in DSU Office Hours on how to update the housing workspace to accommodate the new Sex element.

Q: Will non-official HUD reports (like HMIS Active client list) still have gender? 
A: Yes, gender will still be available on all baseline reports that it is currently included on. 

Gender Toggle 

Q: For the gender security organization button, would it be possible to create a form like form ID 3463 (Manage Transaction Restriction Options and Default Setting) to manage it by organization?
A: This is a great question and one that the product team will begin exploring.

Q: Could an organization attract negative additional administrative oversight by making use of the Gender capture options which ClientTrack will make available?
A: At this time, there is no documentation or evidence to suggest a negative impact to communities who choose to continue collecting Gender on a local level. While Gender is being retired as a federally required data element, guidance does not state that Gender cannot be collected at all. Communities are encouraged to work with their local and state agencies to determine the most appropriate next steps for your community.

Q: Since the gender toggle functionality is a secondary priority to the compliance based updates, do you anticipate the "toggle off" option to be ready for go-live?
A: We are aiming to have the gender toggle option available for the 10/1 production go-live date. 

Q: Will the toggle for the sex question affect custom forms?
A: Not on a baseline level. The Gender Toggle will require rules to be added to the forms, so baseline forms will be updated. We will identify how this was implemented for Baseline and share that information with communities so that you can update your own customizations to align with the gender toggle functionality.

System Performance Measures

Q: Which measure was the System Performance Measures - Measure 7 table shell update on?
A: Measure 7a1 - row 2 has additional language added.

Administrative

Q: Is there a link to enroll in ClientTrack Office Hours?
A: Communities can use the link here for Office Hours: ClientTrack Data Standard Update Office Hours - Wednesdays @3pm ET (join here)

Q: Hi Jessica, can you please put the link in the chat to join future zoom meetings? Thank you. 
A: Hello, please reach out to your Account Manager or email msnedecor@caseworthy.com to ensure you are on our email list.  Future webinars will also be linked in the Knowledge Base.

Q: Apologies if I missed this, will an automatic sync occur on 10/1/25? I don't see that sync request link you just mentioned on the knowledge based article. Is it to be released?
A: An automatic sync will not occur on 10/1/2025. Communities will need to use the Sync Request link (linked at the top of this article) to request a sync for their environments. The sync request link was added on Wednesday, July 23, 2025. 

Q: Does ClientTrack anticipate any additions to the FY2026 DSU?
A: No, we do not anticipate any additions or modifications to the 2026 Data Standard Update documents. We have not see many changes or modifications to the specifications since May 2025. If unexpected changes do occur, we will make the appropriate updates as quickly as possible. 

Q:I know this is a smaller DSU relative to past DSUs but there is a lot of reporting changes. Is ClientTrack anticipating issues with report functionality due to complications, like we've seen in past DSUs? Or do we think this should be a smoother year?
A: No, we are well underway with development and testing of updates for the FY2026 updates. We anticipate all reports, forms, drop-down lists, workflows, etc. to be available for testing on August 28, 2025. One caveat to this is updates to the LSA, as vendors have not yet received 2026 updates to the LSA specifications. Once we receive updated LSA specs, we will begin working on those updates ahead of LSA reporting season.

Q: When they are known, would it be possible to add the tables and fields impacted by the update to the knowledge base? (e.g., cmClient.Gender)
A: Yes, absolutely. We will be updating the article above with form IDs, drop-down list IDs, and table updates impacted by the Data Standards Updates.

Q: With the 2026 DSU elements going into our production environment and then a later sync to bring our custom forms; is there a chance that the DSU update might break one of our custom forms in that short time between DSU change and our custom element update?
A: Our goal with the production deployment is to deploy early on September 30, 2025 and immediately begin customer requested syncs to avoid large gaps between baseline deployments and custom elements being deployed. The baseline production deployment would work the same as all baseline deployments, so it should not break any custom forms before a sync. 

Sexual Orientation

Q: Does the sexual orientation form still appear on PSH enrollment workflows?
A: Yes, it will still appear on the PSH enrollment workflows but will not be required. If communities feel strongly about this decision, we can discuss alternative options in the DSU Office Hours. 

Q: Would something similar to the toggle on/off for Gender be available for Sexual Orientation?
A: At this time, no. There is not a similar option for Sexual Orientation as there is for Gender. But we can explore collaborations with customers to ideate around this request.

DSU Webinar (Hosted on July 23, 2025)

Form & Workflow Comparison Tools (2026 Impact Reports)

Office Hours Recordings (Coming Soon)

• Need to join the Office Hours? Use the link here to join the ClientTrack Data Standards Office Hours - Wednesdays @3pm ET (join here)