Most platforms force one interface on every role. eqLend separates what the automation does from where your team sees it, so the rollout can match the adoption reality of each department rather than the other way round.
Three modes
| Mode | What the user sees | Best when |
|---|---|---|
| Silent delivery | Nothing new. Conditions, tasks and documents appear in the Encompass screens the team already uses. | Adoption risk is the main concern, or a team has been burned by a prior implementation. |
| Purpose-built role screens | Dedicated screens designed around a role’s actual work — task queues, condition review, audit. | Throughput matters and the native screens require too many clicks. |
| Hybrid | Silent delivery for most roles, role screens where they earn their place. | Most production deployments. |
Portability
Role screens run in Encompass Desktop, Encompass Web, and eqLend’s standalone Employee Portal. The same screen definition and the same rules apply in each, so moving a user between environments does not change their process and does not require re-implementation.
The standalone portal matters for two groups in particular: staff who need to work a queue without a full Encompass session, and outsourced or contract teams — QC vendors, contract processors — who need scoped access to their work and nothing else.
TODO(verify) Confirm how portal access and permissions are scoped for external users, and whether Encompass personas govern that scoping or eqLend maintains its own. Procurement will ask.
Screens available today
- Mission Control — the loan-level workspace: My Tasks, Team Tasks, Conditions, Documents and Audit for a single file.
- Task dashboard — pipeline-wide task management with filters by team member, branch and task group, plus status and due-date overviews.
- Pipeline and loan view — loan-level detail with borrower, property, status and task state at a glance.
- QA and audit — deficiency tracking, audit responses and condition-level defect trending.
TODO(verify) “Mission Control” appears in the product UI but not in current marketing copy. Confirm whether it is an official product name to be used publicly, or an internal screen label. If official, it should be used consistently across the site.