February 1, 2027 is the mandatory compliance date for NSPIRE-V. The PHA inspection program HUD has been phasing in since the final rule was published replaces REAC's UPCS-V regime with a new evidence-driven workflow: photos, work orders, sign-offs, metadata, all submitted through HUD's Salesforce-based REMS portal. The portal validates the packet on the way in. Reject on metadata, reject on missing sign-off, reject on file naming — the packet bounces. Here is the schema the portal accepts on the first try, the common rejection reasons, and the block-the-move-in workflow that keeps you out of the 24-hour life-threatening clock.

Our biases, on the table. We are ExactEstate. The schema below reflects what we've seen accepted by the REMS portal in 2025–2026 production submissions. HUD's portal validations evolve; verify any specific rule against HUD's current REAC/REMS documentation. Email corrections@exactestate.com for any fix.

NSPIRE-V evolution from REAC, in plain English

REAC's UPCS-V regime scored properties on a point basis against a fixed defect dictionary. NSPIRE-V is a structural rethink: defects are categorized by severity (life-threatening, severe, moderate, low) with timeclocks attached. A life-threatening defect (LT) starts a 24-hour remediation clock when the inspector logs it. A severe defect starts a 30-day clock. The standard inspection runs against the unit, building exterior, and site, and the inspector documents each defect with photos and metadata.

The shift that matters: under UPCS-V, the report was the artifact. Under NSPIRE-V, the evidence packet is the artifact — photos, work orders, sign-offs, metadata, all tied to specific defects, all packaged together, all submitted through a portal that validates the structure on ingest.

The Federal Register citation, sourced

The NSPIRE final rule was published in the Federal Register as document 2025-19070. NAHRO's February 2026 communication to its membership confirmed February 1, 2027 as the mandatory compliance date for all PHAs and inspected programs. Pre-Feb-2027 inspections may run under transition-period rules; on and after Feb 1, 2027, NSPIRE-V is the regime.

The evidence packet schema, on one page

This is what we generate, in the structure HUD's portal validates on submission:

• Property metadata. PIC property ID, building ID, unit ID, inspection date (ISO 8601), inspector ID, inspector role.
• Defect record. Defect category code (LT / severe / moderate / low), defect type from the NSPIRE dictionary, location-in-unit (kitchen / bath / bedroom / etc.), location-on-property (building exterior / site), narrative.
• Photo evidence. One or more photos per defect. EXIF metadata preserved (timestamp, geolocation if enabled). File naming: {PIC_ID}_{UNIT}_{DEFECT_SEQ}_{PHOTO_SEQ}.jpg. JPG, not HEIC. Photos must be sized to portal limits.
• Work order tie. Each defect linked to a work order ID. Work order has a status (open / in-progress / closed), a remediation timestamp, and a closing photo.
• Sign-off. Inspector signature (digital), supervisor sign-off, date stamp. For LT defects, the 24-hour clock starts at the inspector signature timestamp.
• Submission packet. All of the above bundled as a ZIP archive with a manifest JSON. The portal parses the manifest and validates the bundle structure before accepting.

Common rejection reasons (and the fix)

The block-the-move-in workflow

The expensive failure mode is a new tenant moving into a unit that fails inspection. Under NSPIRE-V, if a unit has an open LT or severe defect at the time of move-in, the operator carries both the audit liability and the resident-safety liability. The mitigation is a workflow rule that blocks the lease activation: until the unit's inspection record is closed-clean (no open defects above moderate, all LT defects remediated and closed), the lease cannot activate.

Operators we've worked with had this workflow in Excel before. The Excel version failed on a leasing rush week when a property manager moved a tenant in over an unresolved exterior LT defect — not because they didn't care, but because the inspection record and the lease record were in different systems. The PMS-native version of this rule is the fix: the lease activation step asks the inspection record before it opens the unit.

ExactEstate's NSPIRE-V module, in plain English

The module ships in the base product. The inspector workflow runs in a responsive mobile UI: inspector logs the defect, captures photos with EXIF preserved and auto-renamed to the schema, the system auto-creates the work order, the inspector and supervisor signatures flow inline. The packet builder runs server-side and produces a portal-ready ZIP with a manifest JSON validated against the current portal schema. The block-the-move-in rule is a workflow toggle in the lease activation step. The 24-hour LT clock has an escalation alarm at T+18h.

What the inspector sees on the phone: a defect list scoped to the unit they're inspecting, the camera button that auto-tags, the supervisor-sign-off button that fires the signature request. What the back office sees: the manifest preview, the rejection-reason simulator that pre-validates against current portal rules, the pre-submit checklist.

Pre-Feb-2027 checklist for PHAs

1. Inventory your inspections workflow today. If it's REAC UPCS-V or a transition-period workflow, capture the data shape before the regime change.
2. Pull a sample of recent inspections and dry-run the NSPIRE-V evidence-packet schema. Where does the data live? What's missing? Who would sign off?
3. Test the photo capture pipeline. If field staff are using personal phones with HEIC defaults, change the device settings now, not on Feb 1, 2027.
4. Build the work-order tie. Every defect needs a WO ID. If your system doesn't auto-create the WO on defect creation, change the workflow.
5. Build the sign-off workflow. Inspector + supervisor, with timestamps. Block packet finalization until both sign.
6. Build the block-the-move-in rule. Inspection record gates lease activation. No Excel.
7. Set the 18-hour LT escalation alarm. A 24-hour clock with no early warning is a failure mode.
8. Dry-run a portal submission with HUD's test environment. Validate the manifest. Validate the file naming. Validate the bundle size.
9. Train field staff. The phone workflow is the rate-limiter on Feb 1.
10. Pick a Feb 1 partner. Either your current PMS ships this in base product, or you have a third-party submission tool. Get the contracts in writing before December 2026.

One CTA, no upsell

If you want to walk through the NSPIRE-V module against your portfolio's structure, book 20 minutes. We'll show the inspector phone workflow, the manifest preview, the block-the-move-in rule, and the 18-hour escalation alarm in your tenant.

Cross-references: NSPIRE Salesforce-Portal-Ready Evidence Packet for the prior writeup; HOTMA Vendor Scorecard for cross-vendor compliance readiness; EIV Reconciliation for the 15-day clock workflow.

Sources

• NSPIRE final rule, Federal Register document 2025-19070.
• NAHRO February 2026 communication confirming February 1, 2027 as the mandatory compliance date.
• HUD REAC/REMS portal documentation (verify current portal schema at submission time; HUD updates the schema in minor versions).
• 2025–2026 production submissions reviewed by ExactEstate's compliance team; specific rejection reasons reflect actual portal responses observed in that window.

— The ExactEstate compliance team