Short answers to the questions we are asked most often. Where an answer is not yet verifiable it is marked, rather than guessed at.
Does eqLend make credit decisions?
No. eqLend generates conditions, assembles files and fills condition data from documents. The credit decision remains an underwriter action. The design principle the platform does not break is that underwriters underwrite and technology assists.
Is this pre-underwriting?
No — the correct term is pre-conditioning. The engine determines what a file will be asked for, based on rules the lender owns, before the file reaches an underwriter. No credit judgment is made or implied.
Do we have to replace Encompass?
No. Encompass remains the system of record. eqLend runs inside your existing environment as an orchestration layer, reading loan data and documents and writing back conditions, tasks and corrected values.
Do our people have to learn a new system?
Not necessarily. In silent delivery mode nothing new appears — conditions, tasks and documents show up in the Encompass screens the team already uses. Purpose-built role screens are optional and can be deployed per role. See the Experience layer.
Do the conditions live in Encompass, or in eqLend?
Both, by design. Conditions and condition attributes are generated in the eqLend engine, outside Encompass, and then delivered into Encompass through the Encompass Developer Connect v3 APIs. Your team works native Encompass condition records in the screens they already use; eqLend keeps the rules that produced them. Nothing custom has to be maintained inside Encompass. See Condition Engine.
Do we have to move to Enhanced Conditions first?
No. eqLend writes to either standard Encompass conditions or Enhanced Conditions, according to your preference. Whichever condition model your underwriters and QC team work in today is the one conditions arrive in, so adopting eqLend does not require a framework migration as a prerequisite.
Who owns the rules?
The lender. Task, needs list, condition and QC rules are yours, expressed in your wording. See Rules, ownership and portability.
Are we locked to one document extraction vendor?
No. The extraction layer is deliberately vendor-agnostic. A provider can be replaced without rebuilding rules, because the rules sit above the extraction layer rather than inside it.
Does it work for our loan products?
Conventional, FHA, USDA, VA, Jumbo, High Balance, Bond, Renovation and Construction-to-Permanent, plus investor overlays implemented as part of your rule set. See Loan products and overlays.
What results have lenders seen?
In a Q1 2026 case study at a national Encompass lender closing 1,500 loans per month: roughly 30% fewer underwriter touches, 28% fewer days from submission to clear-to-close, and about 80% of clerical condition work removed, with 3,300 rules in production.
How long does implementation take?
TODO(verify) — this must be answered with a real phase list and typical durations before publication. See Implementation and onboarding.
Where does our data go?
TODO(verify) — see Security and data handling. This page must not be published until the answers are verifiable.