The file your disclosure desk wishes every loan officer (LO) sent.
We built the workspace to produce one artifact: a complete, validated, disclosure-ready loan file in your loan origination system (LOS). Every control in it serves that file: the consent gates, the services tray and the hard-gated launch button.
What’s inside
The full Uniform Residential Loan Application (URLA)
Every section of Form 1003: borrowers and co-borrowers, employment and income, assets and liabilities, real estate, declarations with their follow-ups, military service, and the complete demographic addendum with subcategories. Your loan officer captures it once. We serialize it to Mortgage Industry Standards Maintenance Organization (MISMO) 3.4 and write it back to your LOS field by field, with a receipt of exactly what landed where.
One services tray
Soft and hard credit, address standardization, flood determination, closing fees and the automated compliance review, all ordered from one place. We track each order with a durable transaction reference, so a billable service never fires twice, and we show everything open in a single “what’s outstanding” view.
Consent discipline
A hard credit pull needs each person’s own authorization, the same strict standard the borrower journey holds itself to. If there’s no authorization, there’s no pull. The workspace won’t order it.
A launch that refuses
“Launch eDisclosures” hard-gates on the required services. Outstanding flood? Unclear compliance review? The button tells the LO exactly what’s missing and stays disabled until the file is clean. We built the gate to fail closed: see how the compliance gate works.
Continuity with the self-serve journey
Borrowers don’t respect channel boundaries, so we don’t either. A self-serve application that stalls shows up in the workspace pipeline with everything the borrower entered intact: values, consents, service results and disclosure state. The LO continues the file and never has to restart it. A borrower the LO starts can also finish self-serve, on their own device, with their own consent trail.
Two disclosure postures, both supported
- Your disclosure desk sends: the LO submits the completed file to the LOS, your internal team owns initial disclosures, and the write-back receipt shows exactly which fields queued.
- The LO sends their own docs: the workspace generates the package and delivers it for borrower e-signature, and we record the send dates to disclosure tracking. It’s the same gate either way.
Where the LOS connection stands today. We’ve built loan create and field-level read/write with receipts against the LOS’s published contracts. We’ve built service orders and disclosure delivery to those contracts too. They run simulated, and we label them as simulated, until you connect your sandbox.