11 minutes
What you ask, and what happens to the answer A field on a form is a promise about what happens next. This lesson covers the five questions that have to be answered before the field exists, and what the state already owes a person when it asks.
What you’ll be able to do Apply five questions to a proposal to collect identity information, and state what the Minnesota Government Data Practices Act requires when the state asks a person for private information about themselves. Compare the responses to this question and explain your choice: What is the first move? Document a next step for What you ask, and what happens to the answer: Take one identity question already in use in your unit’s forms, surveys or systems and try to answer the five questions about it. If you cannot answer one of them, you have found the work. A field is a promise, not a container A field on a form is not neutral. It is a promise that somebody thought about what the answers are for, that the answers are safe where they are going, and that the person filling it in knows what they are agreeing to. When a field arrives because a new system offered it, none of those promises has been made.
The five questions below are the design work, not a compliance step at the end, and for most fields they take about twenty minutes. Any one of them left open is a reason to wait rather than a reason to stop forever. The usual result is not “do not ask.” It is “ask differently”: a private channel instead of a mailed form, a stated reason in plain words instead of a bare field, or reporting at a level where no single person can be picked out.
There is a genuine cost on the other side too. A division that collects nothing about who its programs reach can only report that it has not seen a difference. That will not hold the first time somebody asks whether a program works as well for everyone, and it leaves the people most likely to be missed invisible in exactly the places where decisions are made.
The five questions, in the order they matter Why are we asking? Name the decision, report or change the answers make possible. “It would be good to know” is not a purpose.
What changes because of the answers? If nothing in the program would be done differently, the question collects risk and returns nothing.
Is the answer genuinely optional? A person must be able to skip it, in every channel, without the form stopping and without being treated differently.
Who will see it? Name them: this unit, a contracted provider, a county, a public report, an audit file, anyone who makes a data request.
How long does it stay, and where does it stop? A field with no end point turns one moment’s answer into a permanent disclosure.
What is already required, and who decides it The notice the state owes a person When a state agency asks a person to supply private or confidential information about themselves, the Minnesota Government Data Practices Act requires a notice: why the information is being collected, how it will be used, whether the person may refuse, what happens if they supply it or refuse it, and who else is authorized to receive it. That is an obligation, not a courtesy. It is also exactly what a person needs in order to decide.
Classification is not a matter of preference Government information about individuals is classified by law as public, private or confidential. A unit does not choose the classification because a field feels sensitive, and it cannot promise secrecy it has no authority to give. The responsible authority and the department’s data practices office make that determination. Ask them before designing around an assumption.
Information about staff travels a different route Information about employees sits under personnel data rules and the department’s own human resources policies, not the route that applies to people receiving services. A staff member’s identity is theirs. A manager who is told something in confidence is not holding a record, and should not create one. Questions about personnel records go to human resources.
Discrimination is a separate question with a separate door The Minnesota Human Rights Act lists sexual orientation and gender identity among its protected characteristics. Whether something amounts to unlawful discrimination is decided by the Minnesota Department of Human Rights and by the department’s equal opportunity and legal offices. It is not decided by a learning module, a workgroup or a supervisor’s reading of a policy.
Ask it, do not ask it, or change the design? A voluntary statewide experience survey explains why it asks about sexual orientation, says an answer is optional, and publishes results only at a level where no one can be picked out.
Choose a category Safe to ask Do not ask it yet Change the design, not the question A new intake screen includes a gender identity field because the system offers one, and nobody can say what the answers will be used for.
Choose a category Safe to ask Do not ask it yet Change the design, not the question A person’s used name is typed into a free-text note because the record holds only a legal name, so every notice prints the other name.
Choose a category Safe to ask Do not ask it yet Change the design, not the question A county-level breakdown would show a single person in one category, identifying them to anyone who knows the county.
Choose a category Safe to ask Do not ask it yet Change the design, not the question A grant application asks community organizations to report the identities of the people they served, with no explanation of who will see the list.
Choose a category Safe to ask Do not ask it yet Change the design, not the question A voluntary, anonymous staff experience survey asks about identity, reports only for groups large enough to protect individuals, and is run by a unit that cannot link answers to employment records.
Choose a category Safe to ask Do not ask it yet Change the design, not the question Check matches Reset Answer the five before the field goes live What you can change You control whether a question reaches a form with its purpose, its optionality, its audience and its end point already written down.
What to watch for Do not let a field arrive because a system offers it or because another survey has it. A borrowed question does not bring its conditions with it.
Your next step Write the five answers into the same document that requests the change, so the next person can read them without asking you.
A private reflection, for you alone. Whose expertise is missing from the decision to add this question? What would safety and accessibility mean here beyond a legal minimum? Nothing you write here is collected, seen or kept.
Carry this forward Five questions decide whether a field belongs on a form: why we are asking, what changes because of the answers, whether the answer is genuinely optional, who will see it, and how long it stays.
Under the Minnesota Government Data Practices Act, information the government keeps about individuals is classified by law, and when the state asks a person to supply private information about themselves it must tell them why it is being collected, how it will be used, whether they may refuse, what happens if they answer or refuse, and who else may receive it.
Optional has to be optional in practice. A blank that stops the form, a phone script with no way past the question, or an answer that changes how a worker treats the person is not a choice.
Collecting nothing is also a decision with effects. It leaves the division able to say only that it has not seen a difference, which is a statement about the questions asked rather than about the people served.
Small counts identify people. One or two people in a category in a county report is a name to anyone who lives there, whatever the cover of the report says.
A scenario about fields switched on because a system offered them, sorting practice on when to ask, and a knowledge check on what the state has to tell a person when it collects private information.
Take one identity question already in use in your unit’s forms, surveys or systems and try to answer the five questions about it. If you cannot answer one of them, you have found the work.
Browse and download only. Course notes are not typed or saved on this page.
Mark this lesson completeReset 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.