eqLend is a mortgage orchestration platform that runs inside ICE Mortgage Technology’s Encompass. It automates the clerical layer of loan manufacturing — the assembly, classification, condition generation and data entry that sits around a credit decision — while leaving the decision itself with your underwriter.
The four layers
Every eqLend deployment is some combination of these. They share one rules layer and one document layer, which is what allows a correction made in processing to change what underwriting and QC see on the next loan.
| Layer | What it does | Who feels it |
|---|---|---|
| Document intelligence | Classifies each document as it arrives, extracts the data inside, and ties it to the condition it satisfies. | Processing |
| Task framework | Generates the document and task list a loan actually requires, and keeps it current as the loan changes. | Processing, sales |
| Condition Engine | Generates the initial condition set before submission and fills condition data from documents. | Underwriting |
| Quality control | Turns post-closing findings into active upstream rules. | QC, compliance |
The sequence on a single loan
- A loan reaches the disclosure or rate lock stage. eqLend reads loan application data, automated underwriting findings, and — where applicable — the FHA scorecard, and generates the initial condition set.
- The document and task list is generated from loan-level detail: product, investor, occupancy, property type, borrower structure. Not a template that gets pruned down.
- As documents arrive, each is classified, tied to the condition it satisfies, and its data extracted.
- Where an extracted value contradicts the LOS, eqLend surfaces the mismatch. The processor confirms the correct value and it writes through to the LOS.
- Underwriting opens a file that is already assembled and pre-conditioned, and validates conditions rather than building them.
- Post-closing, QC findings are converted into rules that fire earlier on every loan that follows.
The feedback loop
The property that distinguishes eqLend from a rules engine you configure once: confirmations are captured, not just applied. When a processor confirms an exception, or an underwriter tightens a condition, or QC records a defect, that judgment becomes a rule in the engine. The system gets more accurate as a function of use rather than as a function of vendor releases.
This is why the platform is described as orchestration rather than extraction. The extraction layer answers what does this document say. The orchestration layer answers what should happen next, in this shop, on this loan — and that answer is owned by the lender.
What eqLend does not do
- It does not make credit decisions. Conditions are generated and data is assembled; approval remains an underwriter action.
- It does not replace your LOS. Encompass remains the system of record.
- It does not lock you to one data-extraction vendor. See Document intelligence.