What it does
A document automation for a mortgage brokerage. The loan type and the borrower's situation decide the checklist: salaried or self-employed, first home or refinance. Borrowers upload from their phone; each file is read, matched to the checklist and checked for dates, names and pages. Missing or unreadable items trigger a specific request, and the loan processor reviews the complete file before it goes to the lender.
The problem
Collecting documents took two to three weeks of emails, most files arrived incomplete or out of date, and processors spent their days working out what was still missing.
Approach
One checklist per loan, built from rules, so borrowers only see what applies to them. Every upload is read and checked against the checklist the moment it arrives. Requests say exactly what is wrong, "page 2 of the March statement is missing", instead of "please resend". The processor signs off the file before submission.
- Input
- AI step
- Rules or code
- Person decides
- Result
Screens
Swipe sideways to see the whole screen.
Client work is shown under confidentiality agreements: no client names, and screens are recreated with sample data.
Stack
- Borrower portal
- Document reading (Gemini API)
- Checklist rules
- Loan system sync
Impact
Typical for systems like this.
