Where HUD's REAC could be faster — and how we'd help.

• • Composite score is only computed AFTER submission — PHAs find out their status months later
• • No standardized self-assessment tool before submission
• • Disputes / appeals take 4-8 months to resolve
• • REAC field staff spend ~30% of time on data-entry corrections vs analysis

Public API that returns the same composite calculation HUD runs internally. PHAs self-check before submission; HUD field staff use it to pre-validate submissions. Surfaces the composite score before submission so disputes can be caught and corrected earlier.

Flags submission errors before they reach REAC. Frees up REAC analysts for case investigation rather than transcription work.

• • Contractor inspectors aren't on a unified data platform — manual transcription to REAC's intake
• • PHAs receive scoring reports as PDF, not structured data — can't easily appeal or trend
• • Repeat defects across portfolio aren't tracked — same issue scored at each property independently
• • Defect remediation deadlines are tracked manually post-inspection

Defect-tracking standard with structured outputs. We supply NSPIRE-aligned self-inspection tooling; HUD subscribes to anonymized defect-density data for portfolio-wide trend analysis.

Surfaces systemic defects (e.g., a specific manufacturer's smoke detector recurring across multiple PHAs) by aggregating defect-density data across the portfolio. Catches repeat defects earlier in the inspection cycle.

• • FDS submission is template-driven — every PHA's accounting team rebuilds it from scratch annually
• • Tie-outs between audited statements and FDS lines are reconciled manually (sometimes weeks of work)
• • FDS edit-check fails surface AFTER submission, blocking PHAs for days
• • REAC analysts validate ~20% of submissions by hand because the auto-edits miss common errors

Native FDS generation directly from PHA GL data. We feed the structured submission; HUD ingests via FASS API. Edit-check happens client-side before submission.

FDS submissions arrive pre-validated, with edit-checks run client-side before they reach HUD. Aims to reduce the rejects that drive the current ~12% reject rate and to shorten the wait for the PHAS-Financial score.

• • Submitted 50058s have a ~6% fatal-error rate (per HUD's own audit data)
• • Each fatal error blocks the family record — voucher payments can be delayed
• • Correction workflow requires re-submission cycles that take 30-90 days
• • Password expires every 60 days; multi-role coordinators juggle 4-6 credentials

Pre-submission validation engine published as a HUD-approved tool. PHAs running it submit clean records every time. Federation with HUD's auth so coordinators sign in once.

Validates 50058 records against every IMS/PIC error code before submission, targeting the fatal errors behind the current ~6% rate. Cuts the correction-resubmission cycle for records that pass validation. Single sign-on reduces password-reset TAC calls.

• • EIV access is gated by complex role provisioning + annual security training
• • Match results are PDF-only — no structured download
• • Discrepancy resolution is manual (compare PDF to tenant ledger by hand)
• • Findings cite EIV mismatches without giving auditors the underlying detail

Structured EIV match API for HUD-approved partners. We pull match data, reconcile against tenant ledger, surface only the genuine discrepancies. Audit trail attached to every flagged record.

Faster income-discrepancy resolution = less subsidy overpayment. Better data for the HUD-OIG (Inspector General) when investigating fraud patterns.

• • VMS submissions arrive on the same week each month — bottleneck on PHA accounting teams
• • No live forecasting — PHAs only see utilization risk after submitting and waiting for HUD to publish
• • Reserve calculations require manual cross-references between FDS and VMS data
• • Rescissions get appealed; the appeal process re-uses the same data

Real-time utilization API. PHAs sync continuously; HUD sees the same utilization that's powering their PHA dashboards. Monthly VMS becomes a snapshot of the live data, not a manual export.

HUD field staff catch underutilization in week 2 of a month, not week 5. PHAs at rescission risk get help before the rescission rather than appealing afterward.

• • Draw form is a text-input PDF; data entry is error-prone
• • Authorized balance vs. drawn balance reconciliation done manually
• • Multiple ACLBs (Account Class Lines) require separate draws — process overhead
• • Treasury sweeps don't notify the PHA until next business day

Structured-draw API. PHAs submit draws as JSON, HUD validates, Treasury settlement happens same-day. Authorized-balance API gives PHAs real-time view.

Replaces error-prone PDF data entry with validated JSON draws, catching draw errors before submission. Enables same-day Treasury settlement where the settlement path supports it.