12 minutes
Writing and reviewing communication before it goes out Learn to review a draft communication, a talking point, or a social post for generalization risk before it reaches the public, using a short checklist rather than instinct alone.
What you’ll be able to do Review a draft piece of program integrity communication for generalization risk, and revise it so responsibility stays scoped to the individuals or organizations involved. Compare the responses to this question and explain your choice: What is the most useful edit before this post goes out? Document a next step for Writing and reviewing communication before it goes out: The next time you draft or review any program integrity communication, run it through the checklist in this lesson before it is sent or posted. Catch it at the draft stage Generalization risk is far easier to prevent than to correct after publication. Once a post, a headline, or a talking point is out, a correction rarely reaches everyone who saw the original, and the correction itself can draw more attention to the generalization than the original piece did. The practical response is to build a short review step into the drafting process itself, applied before anything goes out, rather than relying on the original author to catch their own drift.
The riskiest spots are usually the shortest ones. A full article or a complete internal memo has room to stay precise. A headline, a subject line, a one-sentence summary for a supervisor, or a social post has to compress, and compression is exactly where a community reference can substitute for a longer, more accurate description of who was actually involved.
A short pre-publication checklist Does the headline or first sentence name individuals or organizations, or does it name a group?
If a community, nationality, or shared trait is mentioned, is it necessary to the point being made, or could the sentence work without it?
Would this sentence read the same way if the people involved had a different background?
Has someone other than the original drafter reviewed it specifically for this risk?
Build in a second reader for this specific risk What you can change You control whether a draft goes out after one person's review or after a second reader has checked it specifically for generalization risk.
What to watch for Do not rely on the original drafter to catch their own generalization risk; familiarity with a draft makes this exact kind of drift harder to see.
Your next step Add one line to your team's communication review process: a second reader checks specifically for whether the language stays scoped to individuals and organizations.
Where generalization risk hides Headlines and subject lines
The most compressed part of any communication, and the most likely place a community reference substitutes for a longer, accurate description.
Talking points
Written for speed in a live conversation, which can shortcut the individual-scoped detail a fuller answer would include.
Social posts
Short by design, shared widely, and rarely followed by everyone who saw the original if a correction is needed later.
Carry this forward Generalization risk is easiest to catch and fix before a communication is published, not after; a short checklist applied at the draft stage catches most of it.
The riskiest phrases are often the shortest ones: a headline, a subject line, or a one-sentence summary compresses detail in a way that can accidentally shift the subject from named individuals to an unnamed group.
A second reader, especially one not close to the drafting, catches generalization risk more reliably than the original author reviewing their own work.
A scenario reviewing a draft social media post for generalization risk, and a checklist for pre-publication review.
The next time you draft or review any program integrity communication, run it through the checklist in this lesson before it is sent or posted.
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.
