What changed in the FY2026 data standards

The FY2026 HMIS Data Standards took effect on October 1, 2025. Nearly everything written about them was published before that date, as a warning about what was coming.

This is the version for afterward. What actually changed, which parts apply to a CoC funded organization, and how to tell whether your system and your intake process really made the change or only appeared to.

Start with what you can ignore

The revision list runs to about twenty items and it reads as though the whole standard moved. It did not. A large share of it is specific to Veterans Affairs and SSVF programs, and if you do not run one, none of it touches you.

Not your problem, unless you run VA or SSVF programs V10 Mental Health Consultation, a new element for VA funded projectsV2 Services Provided, with Healthcare Navigation added as a service typeV3 Financial Assistance, with a new date fieldElements 4.05 through 4.10, the specific disabling conditions, retired for VA funded programsR4, R6 and R7, corrected HUD VASH program namesR13 Family Critical Issues, an RHY element with expanded response optionsV7 HP Targeting Criteria, updated dependency language

That leaves a much shorter list, and one item on it is genuinely significant.

Gender was retired and Sex was added

Element 3.06 Gender was retired. So was R3 Sexual Orientation. In their place, HUD added element 4.21 Sex, with responses of female, male, client doesn't know, client prefers not to answer, and data not collected.

Two things about this are easy to miss, and both have operational consequences.

It moved category. Gender was a Universal Data Element, collected by everyone. Sex is a Common Program Specific Data Element. That sounds like a demotion and is not one: per the CoC Program HMIS Manual, 4.21 Sex is required for CoC funded projects, listed across homelessness prevention, permanent supportive housing, rapid rehousing and transitional housing components. Confirm your own components with your HMIS Lead, because program specific elements vary by component in a way universal ones never did.

It is not only new intakes. The requirement covers clients served on or after October 1, 2025, which includes people who were already enrolled on that date. If you started collecting it only at new intakes, you have a gap in the middle of your caseload and it has been growing since last October.

Do not derive it from the old field

The tempting shortcut is to populate Sex from whatever is sitting in the retired Gender field. Do not. They are different questions, the old answers were given to a different question, and a bulk copy produces records that are wrong about real people while looking complete in a data quality report.

Ask directly. Your staff will need a sentence they are comfortable saying, and giving them one is a supervision task rather than a database task.

Historical Gender data does not disappear. It stays in the record, and communities that want to keep collecting it locally can. It is simply no longer part of what HUD requires or what the federal reports read.

The smaller changes that do apply

Element	What changed
3.04	Race and Ethnicity. The additional detail field is now clarified as optional, and the label changed from Hispanic/Latina/e/o to Hispanic/Latina/o. Small, visible on your intake form, and worth checking that your form matches.
2.06	Funding Sources. HUD CoC Builds added as option 56. HUD ESG-CV, option 47, and HUD HOPWA-CV, option 48, both retired. If your project setup still points at a pandemic era source, this is where it surfaces.
C4	Translation Assistance Needed, retired. If your intake still asks it, that is now a local choice rather than a HUD requirement. Many organizations will want to keep asking it anyway, for reasons that have nothing to do with reporting.
4.02, 4.03, 4.04	Income, non-cash benefits, health insurance. CoC YHDP and CoC Builds added as relevant funding sources. Relevant if you run either.
4.13	Date of Engagement. Now applies to street outreach funded through CoC YHDP.
2.09	CE Participation Status. A field name correction to CE Participation Status End Date. Nothing to do unless your system carried the error.
5.04	Information Date. Clarified that end users cannot set a different date for data collected only at project start or exit. A guardrail against backdating, and some systems allowed it before.

What it did to your APR

Six questions came out of the CoC APR and ESG CAPER: Q10a, Q10d, Q24c, Q25c, Q26c and Q27c, all of them gender questions. One went in, Q24e, capturing sex across household types.

Two practical consequences. Year over year comparison against last cycle's report will not line up on those rows, and that is the change rather than a problem with your data. And the FY2026 APR CSV format is mandatory: Sage rejects older formats outright rather than partially processing them.

How to check your system actually did it

A vendor announcing an update and a change landing correctly in your workflow are different events. Six checks, none of which need your HMIS Lead.

Open a new intake and look for the Sex fieldIt should be there, with five response options. If your form still shows Gender in its place rather than alongside it, the update did not reach your form even if it reached your database.

Count how many active clients have it recordedThis is the number that matters, and it is usually worse than expected. Anyone enrolled before October 2025 and still served after it needs the field, and those are exactly the records nobody reopened.

Generate an APR CSV and check the formatYou do not have to submit it. Generating one and confirming it produces the FY2026 format is a ten minute check that saves a rejected upload later.

Look at your project funding sourceIf it still reads ESG-CV or HOPWA-CV, both retired, that is a stale project record and it will cause trouble in more places than this one.

Read your own intake form as a client wouldCheck the race and ethnicity labels, and check that the additional detail field is not still marked required when it is optional. Small, and it is the sort of thing that quietly frustrates people at the desk.

Ask what your staff are actually sayingThe field exists, but does anyone know how to ask about it? A required field with no agreed script gets skipped, guessed at, or asked badly. This is the check most organizations never run and the one that determines your data quality.

If you find a gap, the fix is a pass through active records asking the question properly, not a bulk update. It is slower and it is the only version that produces true data.

About COMPASS

We make case management software for organizations doing this work. It exports the HUD HMIS CSV set against the FY2026 specification, and names the required fields missing from each client record before anything is generated, which covers the second check on the list above without the manual pass.

That is the only pitch in this guide. The rest is true whatever system you run.

Not sure whether a change applies to your components?

Write to us. A person answers, and we will tell you when the honest answer is to ask your HMIS Lead.

hello@illumipath.io

Sources

Program specific elements vary by component, and several third party summaries of this change describe the applicability of 4.21 Sex differently from HUD's own CoC Program manual. Where it matters to you, your HMIS Lead and the manual for your component are the authority. This page reflects HUD's published standards as of August 2026 and we update it in place.