Scope boundary: housing codes, inspection authority, complaint channels, correction periods, and record requirements vary by jurisdiction and housing program. Confirm the current local process before accepting or sending any packet.

Map packet sections to review tasks

Issue and location

Tenant-entered room, surface, fixture, or building-area labels provide orientation. They are not agency classifications or findings.

Condition chronology

Occurrences, repair requests, responses, visits, attempted work, and recurrence can be read in order and checked against source records.

Captures and descriptions

The packet includes every recorded capture in the opened unit vault. Images and operator descriptions can help identify what needs in-person observation, but a file cannot establish conditions outside its frame.

Integrity appendix

Hashes, signatures, timestamp status, and custody checks describe the package’s technical state. They do not turn tenant observations into official findings.

Disclosure statement

The export should state its whole-unit scope, whether sealed originals were omitted, how shared-copy metadata and location were handled, and that custody identities were omitted so the reviewer can identify follow-up needs.

Source separation

Tenant statements, imported documents, contractor records, and agency reports should retain clear source labels rather than appearing as one voice.

Questions for an agency intake design

  • What is the official starting point? A required portal, phone line, form, case number, consent, or inspection request should not be bypassed by sending a packet.
  • Can the agency receive the file safely? Confirm file-size limits, allowed formats, malware controls, accessibility needs, records retention, and whether email is permitted.
  • How are urgent hazards triaged? A static packet must not delay the department’s emergency, life-safety, gas, fire, electrical, structural, or public-health procedures.
  • How will source and date be confirmed? Ask who made each record, when the condition was observed, whether it persists, and which locations require access.
  • How are findings returned? Keep official inspection results, notices, orders, photographs, and correction deadlines identified as agency-created records.

Do not universalize one inspection standard

HUD’s National Standards for the Physical Inspection of Real Estate (NSPIRE) apply within specified HUD programs and publish deficiency criteria by inspectable area. They are useful context for those programs, but they are not a universal local housing code.

For HUD-assisted housing, federal complaint and public-housing-agency paths may also matter. USAGov’s tenant-rights directory explains that the appropriate state agency, HUD channel, or legal-help route depends on the property and dispute. A local department should link its own current forms and standards rather than treating this page as intake guidance.

The housing complaint and inspection records guide shows how to preserve agency records while keeping portal status, official findings, and current tenant observations separate.

Review a synthetic packet

  1. Open the human-readable packet. Use the synthetic HTML example and note which sections support or interrupt intake.
  2. Identify every claimed source. Flag any label that could be mistaken for an inspector observation, tested condition, diagnosis, or official determination.
  3. Compare against required intake. List missing fields, controlled vocabularies, location details, accessibility needs, and safe-transfer constraints.
  4. Inspect disclosure and integrity language. Check that omission and technical status are understandable to nontechnical staff.
  5. Keep the decision narrow. Record whether the format deserves further synthetic testing; do not infer production fitness from a sample review.

No case submissions: the project repository and website are public. Do not send tenant names, addresses, photographs, complaints, inspection material, or other case information to the project.