The problem — manual intake at scale
Each application required a staff member to receive the submission, check for completeness, verify income documentation, cross-reference eligibility rules for the specific program, record the determination, and notify the applicant. With 15+ minutes per application and hundreds of submissions per cycle, a single lottery program could consume weeks of staff time.
Errors were common — missing documents went unnoticed, duplicate submissions were not caught, and audit documentation was produced manually after the fact. Applicants called constantly for status updates because there was no portal. The before state was predictable: heroic staff effort, thin audit trails, and households waiting on answers that lived in someone's inbox.
Program rules varied by development, income band, and preference category — but staff were re-applying the same logic by hand every cycle. AUOTAM's discovery phase documented those rules as configurable data: what could be checked automatically, what required a named reviewer, and what had to remain explicit in the audit record when policy judgment applied.
What AUOTAM built
AUOTAM designed and shipped a structured digital intake and processing system covering the full application lifecycle — not a brochure site with forms bolted on, but an operational system with states, queues, and reviewer gates that match how housing programs actually decide.
Rollout followed a pilot program first: intake and completeness checks live for one lottery window, then eligibility screening and staff queues, then applicant self-service and full audit exports. That sequencing let housing staff validate outcomes against prior manual runs before the next program line moved onto the platform.
- Digital intake portal replacing paper and email submissions, with mobile-responsive forms applicants could complete from any device
- Automated completeness validation — the system checked for required documents and data fields immediately on submission, requesting missing items automatically without staff intervention
- Eligibility screening engine — configured to each program's specific income limits, household size requirements, and preference weights, running automated checks against submitted data
- Lottery draw management — randomized, auditable draws with documented methodology and exportable results for HUD review
- Waitlist management — automatic placement, priority weighting, and position tracking
- Applicant status portal — residents could check application status, upload additional documents, and receive automated updates without calling the office
- Staff review interface — reviewers saw only the applications that required human judgment, with flagged exceptions, complete documentation, and a structured decision interface
- Full audit trail — every eligibility determination, lottery draw, and waitlist movement recorded with timestamp, reviewer, and methodology for HUD compliance
The outcome
Across 20,000+ applications: median automated review time under 4 seconds per application, down from approximately 15 minutes manual — roughly a 225× reduction in median wall time for the automated portion of reviews.
Staff time shifted from data entry and manual review to exception handling and applicant support. Audit documentation generated automatically for every determination — no post-hoc manual assembly. Applicant status calls to the office reduced significantly as the self-service portal handled routine inquiries.
Automated runs handle pattern-matched eligibility cases. Policy-sensitive decisions and exceptions remain with human reviewers. The eligibility engine and audit posture are unchanged — only the delivery mechanism changed.
Duplicate submissions and incomplete packets were caught at intake rather than during manual review, which reduced rework queues and shortened time-to-first-response for households. Lottery and waitlist events produced exportable records aligned to how programs already describe methodology to oversight bodies.
The 15-minute-to-4-second comparison is median wall time for automated eligibility runs on pattern-matched applications; complex cases still route to reviewers with full context attached, so staff judgment stays in the loop where statute and local policy require it.
What this means for small PHAs
Most small Public Housing Authorities do not have a dedicated IT department or a budget for enterprise software contracts. The AUOTAM system was built specifically for lean operations — staff onboarding was straightforward, the applicant portal worked on mobile without a native app, and the system could be maintained without a software engineer on call. HUD compliance documentation was a byproduct of the system's normal operation, not an additional manual step.
The same pattern applies beyond a single state: any public or regulated intake program that combines self-service, expert review, and compliance pressure benefits when exceptions are first-class objects — logged, attributable, and reviewable — instead of side conversations in email.
Who this is for
This case study is most relevant for small to mid-size PHAs processing 200+ applications per lottery cycle manually, nonprofit housing operators managing waitlists across multiple programs, state and local housing agencies replacing spreadsheet-based lottery systems, and organizations preparing for HUD reviews that need documented audit trails.
If you are evaluating vendors, ask for a walkthrough of exception handling and audit exports — not only applicant-facing screens. Those operator paths determine whether automation actually holds up when volume spikes or policy interpretation shifts mid-cycle.
What shipped
- Digital intake, completeness checks, and eligibility screening per program rules
- Lottery draws, waitlist management, and applicant self-service status portal
- Staff review queues, exception handling, and HUD-ready audit trail exports
If your housing program is processing applications manually and you want to understand what a scoped system would cost and how long it would take to implement, book a 30-minute workflow review.
How we write case studies
Every published story follows the same editorial bar: context, constraints, shipped work, and honest metrics. Read the full methodology if you want to compare how we document outcomes to typical vendor marketing pages.