8 minutes
The name-and-privacy loop A repeatable method: ask the name, write the circle, fix the form, support the life, document, review.
What you’ll be able to do Identify the practical implication of “The name-and-privacy loop” and apply it to one live DHS decision connected to LGBTQ+ Inclusion in Disability Services. Compare the responses to this question and explain your choice: What should happen before the work is locked? Document a next step for The name-and-privacy loop: Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed. The method has to survive a Tuesday shift change. If it needs a binder, the old name on the door will win.
How do you know it is working? Six moves: ask the name they use; ask who may know; put it on the door and the meeting; fix the form; support relationships without broadcasting; review when someone new is hired or a family wants a veto.
In this lesson you will Run the name-and-privacy loop on one person you already serve.
Write a circle that a night shift can actually follow.
Use questions that do not force a coming-out speech.
Avoid the usual pitfalls: one house briefing, a frozen legal name, and a family veto.
A method is what you do when the shift changes. Write the name and the circle so Tuesday-night staff do not invent a briefing.
The name-and-privacy loop 1. Ask — the name they use Privately, with the device if they need it. Name, pronouns, how to say it. Do not require a speech. Do not correct their word.
2. Ask who may know Which staff, which family, which housemates, which clinic. Different people may get different information. Write it.
3. Put it where daily life happens Door, meeting, MAR-as-used, how we call them in the waiting room. Legal name only where the document requires it.
4. Fix the form If the form cannot hold the name, add a line. If the waiting-room script deadnames, change the script. The form is staff work.
5. Support the life without broadcasting Dating, community, clothes, a partner at the table. Ordinary safety. Not a house announcement.
6. Review — new staff, new veto, new ask When someone is hired, when a family pushes, when they change the circle. An undated “everyone knows” is outing waiting to happen.
The circle is a control, like a med pass. If it is not written, the house meeting will invent one.
Where in the loop? Ask privately what name they use.
Choose a category Ask name / circle Daily life / form Support / review Change the waiting-room call so it matches.
Choose a category Ask name / circle Daily life / form Support / review Support a date without a house announcement.
Choose a category Ask name / circle Daily life / form Support / review Write which family members are not to be told.
Choose a category Ask name / circle Daily life / form Support / review Rebrief when a new DSP starts.
Choose a category Ask name / circle Daily life / form Support / review Check matches Reset Last lesson: practice on one person already on your caseload, and how to repair a name or an outing that outlived their say.
Put this lesson to work What you can change You control whether the name-and-privacy loop changes a live DHS process connected to LGBTQ+ Inclusion in Disability Services or remains information on a page.
What to watch for The team completes the learning, keeps the same default, assigns no owner, and never checks who carries the burden.
Your next step Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed.
Fictional working example
Follow a stated preference through the daily record In this fictional example, Alex asks staff to use Alex in daily contact and asks them not to announce a private conversation to the household.
1
Confirm the request → Ask Alex which name to use in this contact and what information may be shared with whom.
Examine this handoff Do not infer preferences from appearance or make one conversation a blanket consent. Explain any relevant limits through the appropriate process.
2
Correct the usable record → Use the relevant record process so the daily contact list reflects the confirmed name.
Examine this handoff Distinguish a daily display from records with separate requirements. Confirm the right process rather than silently changing unrelated records.
3
Share only what the work needs → Give the next staff member the confirmed contact preference without broadcasting the private account.
Examine this handoff Check authority and need before sharing. A household relationship does not by itself answer who should receive private information.
4
Check at a transition When a new staff member joins, confirm that the contact preference still works for Alex.
Examine this handoff A change in staff is a reason to check the handoff, not to require Alex to retell a personal history.
Try it with the work What is the difference between correcting a daily name field and sending a household-wide announcement?
Draft a minimal handoff containing the confirmed preference, relevant record and review trigger.
Carry this forward A repeatable method: ask the name, write the circle, fix the form, support the life, document, review.
You control whether the name-and-privacy loop changes a live DHS process connected to LGBTQ+ Inclusion in Disability Services or remains information on a page.
Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed.
Completion is shown by a scenario decision, a knowledge-check response, a completed sort and a saved one-minute commitment.
Choose one live work object, name a change or formal escalation, assign an owner, and set the date the result will be reviewed.
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.
