Everything you need to understand, evaluate, and run eqLend: how the platform works inside Encompass, what each framework does for processing, underwriting and quality control, and how the rules that drive it stay yours.
Start here
- How eqLend worksThe four layers, and what runs where.
- Architecture and Encompass integrationWhere eqLend sits relative to your LOS.
- Experience layerSilent delivery, role screens, or both.
By department
- Task frameworkProcessing: task lists, needs lists, dashboards.
- Condition EngineUnderwriting: condition generation and validation.
- Quality controlAudit, defects, and the feedback loop.
Platform
- Document intelligenceClassification, extraction, mismatch detection.
- Rules, ownership and portabilityThe four rule sets and who owns them.
- Loan products and overlaysCoverage across products and investors.
Reference
- Frequently asked questionsShort answers to the questions we get most.
- GlossaryTerms used across these pages.
In progress
Two pages are drafted but not published, because publishing them before the facts are verified would be worse than their absence. Both are written and waiting on confirmation from eqLend engineering.
- Security and data handling — what eqLend reads, stores and writes back; hosting; access control; audit posture; subprocessors.
- Implementation and onboarding — deployment phases and durations, the starting rule set, division of labour, training and support.