Built by CoWorQ · Mortgage lending

LUPA

Loan Underwriter Prep Agent

Prepares mortgage files for underwriting, with every number traceable.

LUPA classifies borrower documents, calculates income and assets with cited guidelines, and sends only flagged items to a human reviewer.

CoWorQ built LUPA for mortgage lending. It follows the same governed pattern as QRION, and it is ready to deploy today. Interested? Talk to us and we’ll set it up for your business.

What is LUPA?

LUPA is a loan underwriting preparation workflow that CoWorQ built for mortgage operations. Agent steps classify borrower documents, extract fields with links back to the source page, calculate qualifying income and assets with guideline citations, and draft precise requests for missing items. Each number carries its lineage from field to calculation to rule to condition. Items that need judgment, such as a large unexplained deposit, go to a human reviewer, and the file moves forward only after that review.

See it in action

LUPA demos

LUPA overview.Why loan processors lose hours to document preparation, and how LUPA works alongside them.
Transcript

Every day, mortgage lending teams handle mountains of loan data. Applications, disclosures, and endless supporting documents pour in, overwhelming physical and digital desk space.

Highly trained loan processors are losing four to six hours every single day to mindless document preparation. The first roadblock is the sheer number of portals. A processor has to manually navigate across five to 12 different disconnected lending websites just to access the required files. Each of those portals enforces strict biometric two factor authentication for every single login. Once inside, processors face tedious copy and paste data extraction. Then they rely on complex mental lookup tables based on loan category and state just to figure out where to route the extracted files.

The mortgage industry is currently paying specialized talented humans to act as error prone data transfer machines. This chart visualizes the damage of human cognitive overload. We see a three to five percent transcription error rate and a 10 to 15% routing error rate. Relying on shared inboxes loses emails, pushing SLA violations up to 30%. The broader tech industry often suggests throwing fully autonomous AI at the problem, but those systems fail in this specific environment. An autonomous AI cannot pass biometric two FA checks, and using large language models for repetitive web scraping burns through operating budgets rapidly.

The industry requires a collaborative, intelligent coworker rather than a complete machine replacement. That coworker is LUPA, the Loan Underwriter Prep Agent built by CoWorQ. LUPA operates as a human in the loop orchestration system. It is specifically built to amplify the processor's output rather than replace their role. Here is how it works. The human processor logs in using their own biometric authentication. This allows LUPA to securely capture a secure temporary session token.

This attended automation model merges strict bank level security with digital execution speed. With access granted, LUPA answers the deterministic automation phase. 90% of this workflow requires precise execution, not AI guesswork. Hidden background browsers automatically navigate the approved lending websites, instantly scraping the necessary loan data.

This routing tree shows the next step. A rules engine sorts loan documents based on category and state, dropping files into correct destination buckets without custom code. When an email response returns, it triggers the smart assistance phase, bringing us to targeted AI. Lupa deploys large language models specifically for fuzzy matching, reading the unstructured text of the return documents to verify they match the original request.

This surgical, highly restricted use of AI keeps the system's operating costs predictably low, sitting comfortably under $200 a month per processor.

This dashboard shares the operational outcome. The processor's role immediately shifts from a data entry clerk to a high level workflow manager armed with clear pipeline visibility. Lupa proactively tracks response times and automatically escalates delays before strict SLAs are missed. This widget highlights the impact on the daily clock.

Manual processing time is slashed by 70%. Alongside that time savings, routing errors fall to under 1% and SLA violations drop to under 5%. These metrics represent a significant reduction in the mental load associated with manual routing and data entry. Those operational wins translate into 27,000 to $40,000 save in annually per processor.

The orchestrator model pays for itself rapidly, hitting the breakeven point with just a three to four person team. Over a three year horizon, operations managers need a 600 to 800% return on their investment. Small and mid sized lenders finally have the intelligent infrastructure required to scale loan volume without linearly adding headcount. Human talent is freed from low value execution, allowing them to focus on customer strategy and relationship building.

Powering process. Empowering people.

LUPA: assigning loan conditions with AI.LUPA proposes who should handle each loan condition; the processor reviews and can change any assignment.
Transcript

Let's see how AI can help us cut time when assigning the condition to its perfect persona.

I am already logged in with UWM wholesale.

Let's pull the conditions and all loans.

Let's confirm.

The workflow has started. Here, it found two loans. Let's proceed with onboarding the loan.

For demo purposes, I am changing the emails here to my email.

All done. Let's onboard.

So we have 14 conditions for this loan.

Now assume we are five loans and each has 14 or so conditions.

It will take much longer to assign a persona to each loan, so let's use AI for that. The AI will review all historical assignments that support successful workflows, perform semantic analysis of the conditions for the persona we fetch, and apply its own intelligence to find the perfect persona for the condition.

It may take thirty seconds or up to a minute to analyze the conditions.

Here, it started assigning all personas. We see it assigned from closing to closer, from disclosure to the loan officer, from underwriter to its underwriter, and to the escrow agent as well.

We can review it and change it if we don't agree with this assignment. Once we change, we have a mark here to track. These are changed by us, and these assignments are made by AI.

So upon continuing the workflow, it will work the same, send the emails to the assigned persona for particular emails.

The problem

Where mortgage lending work gets stuck

  • Mixed-quality document stacks

    Paystubs, W-2s and bank statements arrive as scans of uneven quality. Processors sort, label and key in the same fields by hand on every file.

  • Calculations without lineage

    When an underwriter or auditor asks where an income figure came from, the answer is often buried in a spreadsheet with no link to the source page or the guideline applied.

  • Follow-up loops

    Missing documents and unexplained deposits turn into rounds of emails between processor, loan officer and borrower, each one written from scratch.

The workflow

Agent steps inside a governed process

Agents prepare the work. People decide where judgment matters. Every step is recorded.

  1. 1
    System step

    Application and documents received

    The loan file opens and paystubs, W-2s and bank statements are collected from the portal or upload.

    Role
    Intake
  2. 2
    Agent step

    Classify and extract

    An agent step labels each document and extracts fields, linking every value to its source page and snippet.

    Role
    Document agent step
  3. 3
    Agent step

    Calculate income and assets

    Qualifying income and assets are calculated with the guideline cited for each step, and unusual deposits are flagged.

    Role
    Calculation agent step
  4. Approval gate

    Reviewer clears exceptions

    A processor or underwriter reviews only the flagged items, such as a deposit that needs a source, and approves or requests documents.

    Role
    Processor or underwriter
  5. 5
    Agent step

    Draft borrower requests

    Conditions become precise questions and portal tasks for the borrower or loan officer, ready for a person to send.

    Role
    Communication agent step
  6. 6
    System step

    Package with full lineage

    The underwriting package records each field, calculation, rule and condition so the decision can be traced later.

    Role
    Record

Capabilities

What LUPA does

  • Document classification

    Sorts and labels borrower documents across mixed-quality scans, with each extracted field linked to its source page.

  • Cited calculations

    Applies income and asset math with the guideline reference shown next to each result.

  • Number lineage

    Every value traces from field to calculation to rule to condition, so reviewers and auditors can follow it.

  • Exception flagging

    Anomalies and possible fraud signals are explained and routed to a person, not decided by the agent.

  • Drafted follow-ups

    Writes specific requests and portal tasks for borrowers and loan officers, with TRID and RESPA requirements in view.

  • Governed learning

    Reviewer resolutions inform heuristics and thresholds, and changes ship only through governed releases.

The reusable pattern

Same shape, any process

LUPA shows the QRION document-to-decision pattern: extract with source links, calculate against cited rules, and send exceptions to a person. The same pattern fits claims, credit memos and invoice review.

How QRION runs any process

Want LUPA for your business?

It is ready to deploy today. Talk to us and we’ll set it up for your business.