The file your disclosure desk wishes every LO sent.
The workspace exists to produce one artifact: a complete, validated, disclosure-ready loan file in your LOS. Every control in it — the consent gates, the services tray, the hard-gated launch button — is in service of that artifact.
What’s inside
The full URLA 1003
Every section of the Uniform Residential Loan Application — 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. Captured once, serialized to MISMO 3.4, written 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 — ordered from one place, tracked with durable transaction references so a billable service is never double-fired, and surfaced as a single “what’s outstanding” view.
Consent discipline
Hard credit pulls require per-person authorization — the same strict standard the borrower journey enforces on itself. No authorization, no pull; the workspace physically will not 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 is missing and stays disabled until the file is clean. The gate is fail-closed by design — see how the compliance gate works.
Continuity with the self-serve journey
Borrowers do not respect channel boundaries, so the platform doesn’t either. A self-serve application that stalls appears in the workspace pipeline with everything the borrower entered intact — values, consents, service results, disclosures state. The LO continues the file; they never restart it. And a borrower the LO starts can finish self-serve, on their own device, with their own consent trail.
Two disclosure postures, both supported
- Disclosure desk sends: the LO submits the completed file to the LOS and the internal team owns initial disclosures — the write-back receipt shows exactly which fields queued.
- LO sends their own docs: the workspace generates the package and delivers it for borrower e-signature, with send dates recorded to disclosure tracking. Same gate, either way.