How to Automate Encompass
Encompass automates the loan file itself. Business rules fire on field changes, thirteen milestones move a file from Started to Completion, the eFolder holds every borrower document, and Mortgage Analyzers read uploaded paperwork and raise exceptions. Watching the pipeline and chasing what sits on other companies' websites is still manual.
The loan file is where a mortgage actually happens
Encompass, from ICE Mortgage Technology, is a loan origination system that a large part of American mortgage lending runs on, covering retail, consumer direct, HELOC, wholesale and correspondent lending from one record.
A loan file in it is not a description of the deal. It is the deal. The borrower's income, the appraisal, the title work, the disclosures and their timestamps, the conditions and the closing package sit in one place, and that is the file an auditor reads two years later.
Which is why so many hands touch it. A loan officer takes the application. A processor gathers documents. An underwriter clears conditions. A closer builds the package. Compliance watches the dates.
Mortgage is also one of the few businesses where being late is a legal event rather than an inconvenience. A disclosure has a deadline attached. A rate lock expires on a stated day. Miss either and the cost is immediate and somebody's fault.
Chasing a loan means refreshing somebody else's portal
Ask a processor what the morning consists of and it is rarely underwriting.
It is opening the appraisal company's portal to see whether the report came back. Checking the title company's own site for the prelim. Emailing the insurance agent about the binder again. Signing into the verification service to find out whether the employer answered. Looking at the county recorder to see whether the payoff posted.
Then it is back into the loan file to type in what each of those sites said, so the record matches the world.
The loan officer's version has the same shape: opening files one by one to see whose lock is running down, whose conditions are open, and which borrower has gone quiet.
None of it is difficult or skilled. It is a person with eleven tabs open, doing the round again tomorrow because every answer changed overnight.
Business rules and milestones already move the file
Encompass automates a great deal of what happens inside the loan file, and a lender who has not configured it fully should start there before adding anything.
Business rules are the engine. Field triggers fire when a value changes, milestone completion rules stop a file advancing until its requirements are met, and persona access rules decide who may even see a field. Thirteen milestones ship out of the box, running from Started through Processing, Approval and Funding to Completion, and the newer task-based workflow breaks those stages into assignable work. The eFolder keeps every borrower document in one place, with sending and receiving on the same screen. In the Underwriting Center, ICE Mortgage Analyzers read uploaded documents, compare what they extracted against what the loan file says, and raise the differences as exceptions for a person to clear.
That is real automation, and it is more than most shops turn on.
What all of it shares is that it acts on the file. A rule fires when a field changes in Encompass. A milestone completes when work inside Encompass is finished. Where a partner built an integration, the outside world arrives on its own. Where nobody built one, and for the local title company, the county recording site and the agent writing the homeowners policy nobody did, a person opens a browser.
The pipeline can be read before the morning meeting
Work in mortgage starts in the loan file and then goes looking for other people. Read the file on a schedule, then go and fetch the outside answers, and the picture changes.
Every lock expiring inside five days, listed by how soon, so an extension is a decision instead of a discovery. Conditions still outstanding across the pipeline, grouped by whose document is holding each file, with a request drafted for each borrower. Appraisals ordered but not scheduled, checked on the appraisal company's own portal, so the order that quietly went nowhere surfaces in a day rather than a fortnight.
Loans closing this week run against the closing checklist each morning, with what is still open named per file. Files whose initial disclosures are approaching a deadline flagged while a compliance officer still has room to act.
Then the work that only exists after funding. Yesterday's funded loans, so the referring agent is thanked while the closing is fresh. Past borrowers whose rate now sits well above the market, listed for a loan officer who would never otherwise look.
Every one of those is reading and assembling. Not one of them is a decision.
Preparing a file is not the same as filing it
Even when nothing has changed since Tuesday, the vendor portal needs checking again before the file can move. In a regulated business that has always meant a licensed employee doing the checking.
WebRun is an agent that works a real Chrome browser, signed in as you. It opens Encompass the way your processors do, opens the appraisal, title and verification sites beside it, and brings back a list with the loan numbers attached.
The line is firm. It reads and it prepares. Nothing is disclosed, submitted, sent to a borrower or written into a loan record without a qualified person approving it, because in mortgage the record is the evidence.
The workflows below are already built, and each one names what it opens.
Questions people ask
Will it send disclosures or change a loan file?
No. It reads Encompass and the sites around it, then prepares a list or a draft. Sending a disclosure, clearing a condition or writing a value into a loan record stays with a licensed person, because that record is what an auditor reads.
Do we need the Encompass SDK or a developer?
No. It works the Encompass interface signed in as your own user, so it sees exactly what that user is permitted to see. There are no API keys, no partner integration and no change to your persona setup.
Is it safe to let it near borrower data?
It runs in your own private environment, signed in as your user, and sessions are not shared between tools. A workflow can be locked to an explicit list of domains, so it reaches Encompass and the vendor sites you named and nothing else.
8 ready-made Encompass workflows
Each one names the apps it touches and the exact steps it takes. Open one to read what it will do, then turn it on.
Want one of these running on your own Encompass?
Show WebRun the process once and it will run it on schedule, in your own private browser environment.


