How Loandock connects to your LOS.
What Loandock reads, what it writes, and how your team controls access.
Loandock starts at pre-approval and works the file to clear-to-close.
What it reads and writes
- Reads:
- the loan's open underwriting conditions, the document list, and milestone state.
- Writes:
- documents into the file, attached to the specific condition they satisfy, and that condition's status set to fulfilled.
- Never touches:
- pricing, credit decisions, AUS findings, your business rules, or your milestone triggers.
Clearing conditions stays with your underwriter.
- 1
Your LOS
Open conditions and file documents remain in your instance.
- 2
Loandock
Reads the assigned work, checks what comes back, and records each action.
- 3
Your team
Reviews exceptions. Your underwriter clears conditions.
Access stays with your admin
Your LOS admin issues the access and assigns the role. You control the scope from the first day and can revoke it in one step. Loandock works inside the system you already run with the credentials you issue.
Actions stay traceable
Each automated action is logged with its timestamp, actor, and affected loan file. Borrower communications are logged too.
Your LOS remains the system of record
Loandock works the condition list in your underwriter’s wording. When a document is ambiguous or does not match the condition, it stops and puts the item on your processor’s list. Your underwriter clears conditions.
- US-hosted. The workflow runs in the United States.
- Borrower documents and messages move over encrypted connections in transit and are encrypted at rest in the working store Loandock uses to process the file.
- Your LOS stays the system of record, so the authoritative copy of every borrower file is yours, in your instance.
- Every automated action is logged with a timestamp, actor, and affected loan file. Borrower communications are logged and available for audit.
Read the data-handling, retention, and incident terms on the security page.