Published September 22, 2026
Research question
How can a manufactured-home community document criminal-history screening without treating a vendor score or a record match as an automatic decision?
Bottom line
HUD guidance does not turn criminal-history screening into a clerical yes-or-no exercise. It warns against overbroad policies, arrest-only conclusions, irrelevant or stale records, inaccurate matching, and decisions that ignore mitigating information. A sound control file separates the approved policy from the report, documents identity matching and policy scope, provides a correction and explanation path, records individualized review, and preserves the final reason. This is an administrative evidence workflow, not a substitute for legal review of federal, state, local, or program-specific rules.
Method and evidence standard
This study reviewed current public guidance from the named federal agencies on September 21, 2026. It translates source requirements and recommendations into an administrative control file for manufactured-home community operations. It does not test a particular community, vendor, applicant, appliance, tax return, or incident. It does not treat agency guidance as a substitute for the controlling statute, regulation, contract, state law, local ordinance, program rule, or professional advice.
Verified facts below are attributed to the source that states them. The proposed fields, queues, review steps, and role boundaries are MobileHomeBiz analysis based on those sources. Where a duty depends on facts not available to the administrator, the workflow records the uncertainty and routes it to the qualified owner. That distinction matters: a complete checklist can show disciplined administration, but it cannot certify legal compliance, technical safety, tax treatment, or fair-housing legality.
Policy before person
The community should approve its written screening policy before reviewing an applicant. Keep the effective date, decision owner, stated purpose, covered transaction types, excluded records, lookback rules, individualized-review factors, accommodation route, and state or local overlays. Do not quietly change the standard because a particular file feels uncomfortable. When a policy revision is approved, retain the prior version and apply the correct version to each case. This version control lets a reviewer distinguish consistent application from hindsight.
Record accuracy and identity matching
HUD's applicant-screening guidance emphasizes accurate records and warns against name-only or wildcard matching. The case record should show what identifiers were used, what ambiguities remained, and whether the screening provider corrected or confirmed the match. Administrative staff should never resolve a possible match by guessing from race, age, address, or other proxy information. Arrest information, dismissed matters, convictions, civil records, and unresolved cases are not interchangeable labels. Preserve the source category exactly and route questions to the authorized reviewer.
Nature, severity, recency, and relevance
HUD materials criticize policies that fail to distinguish the nature, severity, or age of conduct. A structured review form can prompt the decision maker to identify the specific policy provision, the relevant record, its date, why it is connected to a legitimate housing concern, and what mitigating information was considered. The form should not calculate an automatic score unless that method has been independently approved and reviewed. A completed form proves that fields were filled; it does not by itself prove that the decision was lawful.
Applicant notice and response opportunity
HUD's 2022 implementation material recommends providing the record, identifying the portion that may support an adverse decision, and allowing correction or explanation before the final decision. Track the preliminary notice, secure delivery, response deadline, applicant submission, verification requests, reviewer reassessment, and final notice. Staff should use plain language and accessible communication methods. Sensitive records should not be emailed casually or exposed to personnel who do not need them.
Individualized assessment file
Where the approved process calls for individualized assessment, capture rehabilitation evidence, tenancy history, age at the time of conduct, circumstances, time passed, references, and other authorized factors without inviting irrelevant protected-class information. Note what was actually reviewed and why it changed or did not change the proposed outcome. If information cannot be verified, label it unverified rather than false. If an accommodation request arises, move it into the restricted accommodation workflow and pause the ordinary decision path as directed by policy.
Audit for consistency
A periodic audit should compare similarly situated cases, policy versions, record categories, review times, opportunities to respond, and decision reasons. Look for vendor recommendations adopted without review, records outside policy scope, unexplained overrides, missing applicant responses, and decisions made before corrections arrived. Aggregate patterns can identify process questions, but they require careful expert interpretation. Do not publish applicant-level details or use a small sample to claim discrimination is absent.