11 minutes
What the categories were built for Every field in a record was defined by someone, for a reason, and the reason was usually operational. Trouble starts when a category built for payment or eligibility is asked a question about people's lives.
What you’ll be able to do Trace one category in a report back to the form or rule that created it, and state what it records, what it groups together and what it cannot show. Compare the responses to this question and explain your choice: What should the analyst deliver? Document a next step for What the categories were built for: Pick one category you use in reporting, find the form or rule that defines it, and write one sentence naming what it records and one naming what it cannot. A category is a decision with a purpose attached Every field in a record started as somebody's decision. A form designer picked the options. A rule writer defined who belongs in a payment category. A system had space for one value where a person might have offered three. None of those people were careless. They were answering the question in front of them, and that question was almost always operational: how do we pay for this, how do we route it, how do we know which rule applies.
The trouble begins when a category built for one purpose is asked a question it was never built for. An eligibility category tells you which set of rules governs a person's services. It does not tell you how that person experiences disability, which supports they actually use, or how they would describe themselves. A race field with six options tells you which of six boxes was available when the record was made, and often tells you who chose it: a person describing themselves, a worker guessing under time pressure, or a system carrying a value forward from an older record.
None of this makes a field useless. It makes the field specific. The discipline is to say out loud, every single time, what a category records and what it was built to decide, so that whoever reads the chart knows which question they are looking at the answer to.
What the field actually records Race or ethnicity, as one field with a short list
Which of a fixed set of boxes was available when the record was made, and often who chose it. Most systems cannot hold more than one identity at a time, and a value carried forward from an old record can outlive several conversations with the person.
Preferred language
Usually the language someone recorded at one moment, for one purpose. It rarely separates speaking from reading, seldom says whether the person prefers written or spoken material, and does not record whether an interpreter was actually provided.
Disability category
In most administrative systems this is an eligibility or payment category, written to decide which rules apply. It is not a diagnosis, not a description of support needs, and not how the person would describe their own life.
County
The county attached to a record, which may be where a person lives, where a lead agency sits, or where a case happened to be opened. Three different things reported as one, and the difference matters most for people who move or who cross a county line to reach a service.
Case closure reason
A code selected by a worker from a short list, usually in a hurry. Closure reasons are among the most consequential and least examined fields in any system: declined, no response and moved can each describe a process that stopped working rather than a person who stopped trying.
A blank
Information about the conversation, not about the person. A field blank in a third of records is telling you the question was not asked, could not be asked, or had no answer that fit the list. What the report does with a blank is a decision somebody should be able to point to.
Four ways a category goes quiet Collapsing One value standing in for many communities reports smoothly and hides the most. Communities grouped inside a single box can have entirely different histories with public systems, different languages, different arrival stories and completely different experiences of the same process. The chart shows one bar, and the bar is an average of things that are not alike.
The residual box A category named for what it is not, holding everyone the list did not anticipate, is not a group and cannot support a finding about a group. When the residual box is large, that is a finding about the list. The useful next step is to find out what is inside it, not to report it as though it were a population.
Borrowed categories A field built for payment, routing or rule selection gets used for an equity question because it is the only field available. That is often reasonable, and it has to be said out loud every time, because the alternative is a report that appears to describe people and actually describes a billing structure.
Missing treated as normal Blank read as English. Blank read as no accommodation needed. Blank read as no. Each of these is a choice made once inside a report template and then inherited for years by people who never saw it made. Find out which of these your own reports make, and write it where readers will see it.
Disaggregation pulls two ways Why to push for it Where it stops The trade you are making Instead of guessing
Averages hide the people a system serves worst. A measure that looks steady overall can contain a group for whom the process almost never works. A division that never breaks a number apart cannot see that, and it will keep improving the parts that were already fine.
Small numbers are real people. A cell holding a handful of records in one county can identify someone, particularly once a service type or an age band is alongside it. Suppression rules exist for that reason and are not obstruction. State data practices requirements govern what may be published and released, and those decisions belong to the offices that hold them.
Visibility and protection genuinely pull against each other, and choosing between them is a judgment call rather than a calculation. What responsible practice requires is that the choice be visible: say which one you chose, at what threshold, and what you did instead for the groups you had to suppress.
When the fields cannot answer the question, the answer is to ask people rather than to assume. Compensated community advisors, people with disabilities and family partners can tell you what a category is flattening and how a question ought to be worded. That is a piece of work with a real cost, and naming the cost is how it gets funded instead of deferred.
Name what the field records, every time it travels What you can change You control whether the sentence describing what a category actually records is attached to the chart, or sits in a paragraph at the end that nobody carries forward.
What to watch for Do not let a limitation live only in a footnote. A slide separates from its deck within a week, and whatever is printed on the slide becomes what the division believes.
Your next step Put one plain sentence on the chart itself: what this field records, who filled it in, and how much of it is blank.
A private reflection, for you only and never collected: one category I use without thinking is... what it was originally built to decide is... and the thing it flattens that matters most in my work is... If you cannot answer the middle line, the form or the rule that defines it is usually a ten-minute search.
Carry this forward A category is a decision with a purpose attached. Eligibility categories were built to decide payment and which rules apply. They are not descriptions of a person, a diagnosis or a culture, and they behave badly when used as one.
Collapsing hides the most. A single value covering many communities, a residual box named for what it is not, or a language field that allows one answer per person will all report smoothly and conceal the differences that matter.
A blank field is information. A preferred-language value missing from a third of records tells you something true about the intake conversation, and a report that reads blank as English has made a decision nobody wrote down.
Disaggregation has a floor. Making small communities visible and protecting individuals from being identified genuinely pull against each other; the honest response is to say which you chose and why, not to pretend the tension is absent.
A scenario about a breakdown requested from fields that were never built for it, flashcard practice on what six common fields actually record, and a knowledge check on missing values.
Pick one category you use in reporting, find the form or rule that defines it, and write one sentence naming what it records and one naming what it cannot.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
