The ULPI desk Conditions Priority Capacity Bottlenecks Analytics Audit trail
The ULPI desk

Run production like a manufacturing floor.

Ultimate Loan Production Intelligence sits on top of Encompass and your LOS and runs the work. Conditions become assigned tasks, the pipeline ranks itself every morning, and a bottleneck comes with the path out of it.

Tasks and owners Priority Capacity Analytics
Book a call
F Production board Ranking
218 active loans · 6 pods · synced from Encompass 40s ago
Intake 41
Ortega $740K · 1d
Nakamura $1.2M · 2d
Whitfield $505K · 1d
Processing 77
Bhatt $860K · 4d
Delgado $395K · 6d
Okonjo $1.4M · 3d
Underwriting 63
Marsh 01
$980K · lock 3d
Petrov $615K · 8d
Alvarez $720K · 5d
To close 37
Iversen $1.1M · CD out
Reyes $430K · funds Fri
312 open tasks · 9 unassigned · 4 files at SLA risk
Work first today Marsh · appraisal condition Lock expires in 3 days · one task blocks four
Path proposed
Sample pipeline. Figures illustrative.
The corner of a brick and metal building against a deep blue sky
01 Production today

The LOS holds the file. It doesn’t run the work.

A loan is a manufacturing job with forty steps, six people and a clock on it. The system of record tracks the file’s status. What it doesn’t track is who owes what, what is blocking what, and which of two hundred files should be touched first this morning.

The pipeline lives in six places A status in the LOS, a spreadsheet the manager keeps, a chat thread, and whatever each processor is holding in their head.
A condition list isn’t a work list Twenty-one conditions with no owner, no due date and no order sit on the file until somebody reads them again.
Blockages surface at the standup A file stuck since Monday is raised on Thursday, and the four days are already spent by the time anyone can act.

Every day a file waits is a day of capacity you have already paid for.

02 Conditions to tasks

Every condition becomes a task with a name on it.

A condition arrives from underwriting as a sentence. ULPI turns it into work: who does it, what it depends on, when it is due, what evidence clears it — and it clears itself when the document that satisfies it lands.

Source
Underwriting conditions, investor stipulations, checklist items and anything your team adds by hand
Owner
Routed by role, licence, pod and current load — to a person, not to a queue nobody watches
Dependencies
Tasks know what they block and what blocks them, so the file has a critical path rather than a list
Clock
Due dates derived from the lock, the contract date and your own service levels, not typed in per file
Evidence
A task names the document that satisfies it and closes when that document arrives and passes review
Handoffs
Stage moves are a consequence of the work being done, so status is never something someone forgot to update
Write-back
Cleared conditions and status changes go back into Encompass or LendingPad as they happen
03 Priority

The pipeline puts itself in order every morning.

Ranking reads the clocks that actually cost money — lock expiry, contract date, investor cutoff, service level — against what is blocking each file and how long it has been waiting. Every position comes with the reason it holds that position.

Ranked queue · underwriting pod 2 63 files, top 5 shown
01 Marsh · $980K Lock expires in 3 days Blocking 4
02 Okonjo · $1.4M Investor cutoff Thursday 2 tasks open
03 Bhatt · $860K Waiting on borrower 6 days Agent chasing
04 Alvarez · $720K Appraisal in, review due Ready to work
05 Petrov · $615K No clock inside 10 days Can wait
Why 01 is first One appraisal condition holds four downstream tasks and a lock that runs out Friday.
Re-ranked hourly Sample pipeline, figures illustrative
04 Capacity

Who is doing what, at all times.

Load is measured in open tasks and the hours they usually take, not in file counts. Overload is visible before the day it turns into a missed service level, and work can be moved with the file’s history attached.

Pod 2 · today Load against usual throughput
R. Castellanos Underwriter
19 tasks · over
J. Whitmore Processor
14 tasks
A. Duong Processor
9 tasks
M. Feld Closer
6 tasks
Suggested move: 3 conditions from R. Castellanos to A. Duong · Sample pod. Figures illustrative.

A manager should not have to ask three people what they are working on to answer one question.

05 Bottlenecks

A blocked file arrives with the way out of it.

When something stops moving, ULPI reads why, and proposes the path that unblocks it — a document to chase, a rule to re-read, a task to reassign. Where the path is a message, an agent can write it and send it by text or email.

Bhatt · day 6 Waiting
Borrower hasn’t sent the CPA letter
Two requests by email, no reply, no phone attempt logged.
Path: text the borrower on the mobile the 1003 lists, copy the broker, and offer the CPA a form to complete instead of a letter.
Marsh · day 2 Blocking 4
Appraisal review sits behind one condition
Four tasks and a Friday lock expiry sit downstream of it.
Path: move the review to the underwriter with capacity today, and start the three tasks that don’t depend on its outcome now.
Pod 2 · this week Pattern
The same condition keeps coming back
Eleven files this month cleared, then reopened for the same stip.
Path: the request wording asks for the wrong document. Change it at intake and eleven files a month stop turning around twice.
Agents Every action has a setting Chasing a document, confirming an appointment, acknowledging a broker — each one is set to propose, draft for approval, or send on its own. You choose per action, per team, and change it whenever.
Document chase, borrower Sends
Broker status update Drafts
Anything with a number in it Proposes
Outreach · today Pod 2
09:12
Text to borrower · Bhatt CPA letter request, second attempt
Sent
09:41
Email to broker · Okonjo Two conditions outstanding before Thursday
Approve
10:03
Text to borrower · Iversen Signing confirmed, Friday 2pm
Replied
Every message is written to the loan file. Sample activity, illustrative.
06 Analytics

Measured the way a plant is measured.

Because the work is tasks rather than statuses, the numbers are real: how long each stage takes, how many times a file is touched, where the queue is aging. Cut by pod, underwriter, broker, product or investor, and sent to your warehouse.

Cycle time 17.4 days Application to funding
Touches per loan 23 Human actions, all roles
Conditions cleared 186 / day Across 6 pods
Pull-through 78% Locked to funded
Days in stage Median · last 30 days
Intake
1.8
Processing
5.6
Underwriting
7.2
Conditions
2.8
Closing
1.0
Underwriting is the constraint. Sample data, illustrative.
Where the queue is aging
SLA breaches, this week 7
Files idle over 3 days 14
Oldest open task 9d
Rework, same condition twice 11
By pod By broker By investor Warehouse export

You cannot shorten a cycle time you have never actually measured.

07 On top of your LOS

A layer on the LOS, not a replacement for it.

Encompass stays the system of record. ULPI reads the loan, runs the work around it, and writes conditions, statuses and milestones back. Nothing is migrated and no one has to stop using the tool they know.

Encompass
Two-way Encompass Conditions, milestones and field data read live; cleared conditions and status changes written back as the work happens.
LendingPad
Two-way LendingPad The same loop, with your own condition names and stage definitions carried across unchanged.
API Webhooks CSV
Everything else Your other systems Pricing, doc prep, e-sign, the CRM and the warehouse line up against the same task record through the API.
08 Audit trail

Every action on the file, with a name and a time.

People and agents write to the same record. An examiner, an investor or your own QC can read what was done, by whom, on what basis, and what the file looked like at that moment.

Loan 4471 · Marsh 217 entries
When
Who
What
12 Aug · 09:12
Agent · outreach
Text sent to borrower requesting CPA letter, template 04, approved by J. Whitmore
12 Aug · 10:48
R. Castellanos
Condition 12 cleared against appraisal p.4, written back to Encompass
12 Aug · 11:02
ULPI · priority
File moved to rank 01: lock expiry within 3 days, 4 dependent tasks open
12 Aug · 11:20
A. Duong
Appraisal review reassigned from R. Castellanos, reason: capacity
12 Aug · 14:37
System
Borrower uploaded CPA letter; task 18 closed on matching evidence
Entries are append-only Agent actions record the template and the approver Sample file, illustrative

Automation is only defensible if it leaves a record a person can read.

A house set back behind a wooden gate among pines
09 Book a call

Give us one month of your pipeline.

We’ll come back with where the days actually went — stage by stage, pod by pod — and the three bottlenecks that cost you the most of them.

No integration, no commitment, about a week.