Terms as they are used in this documentation. Where a term has a specific meaning in Encompass, that meaning is preserved.
Pre-conditioning
Generating a loan’s condition set before it is submitted to underwriting, based on lender-owned rules. Distinct from underwriting: no credit judgment is made.
Condition Engine
The eqLend component that generates conditions and fills condition data from classified documents.
Task framework
The component that generates and maintains the document and task list a loan requires, and the borrower needs list.
Needs list
The borrower-facing list of what is required and when, driven by lender-owned rules.
Document bucket
A classification grouping that ties an incoming document to the condition it satisfies.
Mismatch
A conflict between a value extracted from a document and the corresponding value in the LOS, surfaced for a processor to confirm.
Exception
A case a rule did not anticipate. When a processor confirms one, the confirmation becomes a rule.
Feedback loop
The cycle in which confirmed exceptions, refined conditions and QC findings become permanent rules that fire earlier on subsequent loans.
BPMN
Business Process Model and Notation — the visual standard used to model workflows, so a process is readable by operations staff rather than only by engineers.
Silent delivery
A deployment mode in which automation surfaces entirely through existing Encompass screens, with no new interface for users.
Role screens
Purpose-built eqLend screens designed around a specific role’s work, portable across Encompass Desktop, Encompass Web and the standalone Employee Portal.
Employee Portal
eqLend’s standalone environment for users who need to work a queue without a full Encompass session, including outsourced teams.
Overlay
An investor requirement stricter than agency guidelines, implemented as part of the lender’s rule set.
eFolder
The Encompass document repository where loan documents and attachments are stored.
Enhanced Conditions
ICE Mortgage Technology’s native condition framework within Encompass. eqLend generates conditions and condition attributes externally and delivers them into Encompass through the Encompass API, so what a user works is a native Encompass condition record. Which specific condition object types are written is documented on the Condition Engine page.