Overview
This release makes income calculation and the pre-underwriting summary more dependable. When documentation does not support a qualifying income figure, Autopilot will now request what is missing rather than produce a figure from insufficient information.
Also in this release: Navigator, the conversational assistant for loan officers, is now available to beta participants.
How Autopilot capabilities are turned on
Core Autopilot capabilities, including Navigator, is a toggle in Lending Config Center.
Two exceptions: Per-tenant toolsets and dynamic toolset discovery on the MCP server are enabled by emailing support@blend.com. Any capability still in beta is switched on by your Blend account team on request.
TABLE OF CONTENTS
- Action required
- This week’s headline: More dependable income calculations and pre-underwriting summary
- Additional fixes
- Greater control and capability
- New AI-powered workflows
Action required
Who needs to act | What changed | What to do |
|---|---|---|
Loan officers, processors, and teams reviewing Autopilot output | Autopilot now withholds a qualifying income figure when the documentation does not support one. These files may show an outstanding borrower request where an income figure previously appeared. | Brief loan teams that this is intentional and does not indicate a failure. To discuss the previous behavior, contact your Blend account team. |
Owners of custom document integrations | Borrower chat transcripts now use the Blend document type CHAT_TRANSCRIPT instead of OTHER. Integrations that filter on OTHER will no longer find them. | Replace any transcript filter using OTHER with CHAT_TRANSCRIPT. Integrations that enumerate document types should account for the new value. |
Owners of Blend MCP integrations | blend_get_disclosure_status now reports the disclosure package status instead of the status of the package's borrower tasks. Field routing is also strict: a field ID that Lending cannot route is now explicitly refused instead of being silently dropped. | Review logic that reads disclosure status or writes by field ID. |
More dependable income calculations and pre-underwriting summary
Update | What changed | Why it matters | What you may notice |
|---|---|---|---|
Insufficient income documentation | A borrower with a paystub but no recent W-2 or verification of employment now receives a document request instead of a base-income figure. | Qualifying income sets DTI, drives eligibility, and establishes the threshold for large-deposit review. An unsupported figure that appears complete is less likely to be rechecked. | More outstanding borrower requests and some files with no income figure where one previously appeared. |
Date-specific document requests | Recency requests now state a cutoff date, such as "Paystubs dated on or after August 3, 2026," instead of requesting "the most recent 30 days of paystubs." Existing requests written in the old format, including requests entered manually, are converted to a cutoff date when read. Autopilot compares the newest printed pay date with the cutoff and states both dates in its reasoning. | A number of days can refer either to the period covered by a document or the date on which it was issued. A specific date removes that ambiguity. On one production loan, paystubs 33 days older than the application satisfied a 30-day request, leaving $10,000 in monthly qualifying income supported by documentation the rule excludes. | More precise wording in borrower document requests and more explicit recency explanations. |
Document rejection explanations | When an upload is rejected, borrowers are told whether the document is blurry, incomplete, or unreadable instead of receiving a general error. | Borrowers can correct the problem instead of resubmitting the same file or waiting for the loan team to contact them. | Fewer repeat uploads of unusable documents and fewer questions about what needs to be corrected. |
Fannie Mae guideline citations | Pre-underwriting summary and income calculation now resolve guideline lookups against a registered Fannie Mae guideline map at the fragment level. A nightly check compares Autopilot's copy with the published corpus and flags discrepancies automatically. Income evaluation now refuses to produce a figure when authoritative guideline text is unavailable. | Citations point to authoritative agency text rather than a paraphrase or stale copy. | More precise guideline references and, in some cases, a refusal where Autopilot previously produced a figure. |
Additional fixes
Income calculation
Update | What changed |
|---|---|
Hours worked | Hours are read from the paystub instead of being inferred from a standard workweek. On one loan, the assumption produced $10,400 in monthly income instead of the correct $11,500. |
Paystub reconciliation | Earnings are read by column and reconciled against the gross printed on the document. If the figures do not agree, Autopilot rereads the document once with the discrepancy identified. Previously, an hours column could be interpreted as dollar amounts. |
Employer-paid benefits | Employer-paid benefit premiums, including long-term disability premiums, are no longer counted as qualifying wages. |
W-2 employer matching | A W-2 year is now scoped to the employer that issued it. |
Employment history | Employment records are read as a history, allowing Autopilot to identify and explain employment gaps. |
Declared and verified income | Declared and verified income are reconciled without double-counting. Declared income that a run did not verify is no longer silently removed. |
Monthly qualifying income | Monthly qualifying income is always stated, including when the final worksheet step annualizes the figure. |
Rental income | Rental income is handled by property. Declared rental income is shown, figures are deduplicated by property, and rent ending at closing is excluded. |
Pre-underwriting summary
Update | What changed |
|---|---|
Missing sections | The summary no longer loses a section. A repeated output pattern was incorrectly treated as truncation, and a technical error caused the income, credit, and executive brief sections to fail during beta. Both causes are fixed. |
Complete loan history | The summary now reports the full file instead of only the 20 most recent runs. Previously, longer histories could lose the income calculation, describe documented income as unverified, and reduce compliance counts and the document log. |
Credit inquiries | Credit inquiries now appear in the summary. A request stopped by a guard is reported as blocked instead of being shown as requiring no explanation. |
Grounded results | The summary no longer states guideline results that cannot be supported by retrieved guideline text. |
Guidelines and document processing
Update | What changed |
|---|---|
Freddie Mac guidelines | Freddie Mac guideline text is available again after a processing issue that began May 27. Autopilot now validates guideline content before serving it, and the existing guideline corpus remains available if a content refresh fails. |
Oversized PDFs | Oversized borrower PDFs are downscaled and processed instead of failing during review. |
Damaged files | Corrupted and truncated uploads return a file-integrity message, distinguishing a damaged file from a poor-quality image. |
Borrower follow-ups and communication
Update | What changed |
|---|---|
Large-deposit requests | Large-deposit requests are held until the income picture is final, preventing requests about deposits that later prove irrelevant. |
Refused follow-ups | Follow-ups refused by Lending are no longer recorded as sent. |
Wrong-document reissues | A reissued follow-up for the wrong document now states what it replaces instead of being reduced to a suggestion the borrower never sees. |
Borrower-specific language | Borrower-facing messages refer to the borrower's actual loan product and identify the assigned loan officer. |
Blend MCP
Update | What changed |
|---|---|
Session consistency | Blend MCP no longer returns 404 Session not found. Sessions are pinned to a single server instance while the transport is reworked. |
Greater control and capability
Capability | What changed | Availability or next step |
|---|---|---|
Lender-specific income overlays | Lender-specific income rules are delivered directly into Autopilot's calculation step. They take precedence over the agency baseline when the two conflict and remain active if a loan moves into a VA or FHA program. For example, two lenders may apply different policies for deriving prior-year variable income when both a paystub and W-2 are available. Both can receive the result required by their policy without a product release. | The default is the agency baseline with no overlay. To add or change an overlay, contact your Blend account team. |
Blend MCP tool scoping | Blend MCP users can scope toolsets by tenant so an agent sees only the appropriate tools. Tool discovery can also be dynamic instead of static. | Dynamic tool discovery and per-tenant default toolsets are off by default. Email support@blend.com to enable them. Scope: per tenant. |
More efficient Blend MCP reads | High-volume reads now support field projection and pagination. Newly catalogued fields include property value, down payment, and borrower phone fields. Purchase loans previously fell through to refinanceValue. Tool-surface telemetry and an updated developer guide are also available. | Field projection, pagination, and the newly catalogued fields are already active for all Blend MCP users. |
Chat transcript document type | Borrower chat transcripts now file as CHAT_TRANSCRIPT rather than OTHER. The full conversation is assembled into one cumulative document instead of being filed in parts. | Not enabled by default. Contact your Blend account team to turn on chat transcripts for your tenant. If you pull documents from Blend into another system, replace any transcript filter using OTHER with CHAT_TRANSCRIPT before enabling. |
New AI-powered workflows
Navigator: a conversational assistant for loan officers
Beta
Navigator allows a loan officer to ask questions about a loan in plain language and direct Autopilot to take action. It operates inside the loan file, and every action is scoped to that loan.
Questions that do not change the loan are answered without approval. Routine, high-confidence follow-ups can proceed directly, consistent with existing Autopilot follow-ups. Anything that changes the loan or reaches the borrower requires an approval card that explains the consequence before the loan officer proceeds.
Live in beta
Capability | Example ask | How it behaves |
|---|---|---|
Ask about a loan | "Where did the qualifying income come from?" | Answers come from the system of record and Autopilot's completed work, with the filed document, timestamp, or guideline reference behind every figure. Where Autopilot has not reviewed something, Navigator says so rather than producing a plausible number. |
Ask for several things at once | "Request the bank statements and update the loan purpose." | A document request and loan update can be completed in the same request, in the order asked. One pass instead of two, with one approval round instead of two. |
Price a loan and select a product | "What products is this loan eligible for?" | Eligibility comes from the pricing engine itself, not a static list. Selecting a product changes the loan's rate, points, closing costs, and proposed housing expenses and cannot be undone. The approval card states those changes before the loan officer approves them. |
Lock a rate | "Lock it at the selected terms." | Navigator proceeds only after confirming that product selection has been executed. It does not rely on a loan officer's statement that the approval went through. |
Pull credit | "Run credit on the co-borrower." | Missing consent and borrower details prompt for the missing information instead of causing the request to fail. Before execution, Navigator states the consequence: a hard inquiry that can affect the borrower's credit score. The approval card includes the report's pull date, so a loan officer can tell whether the DTI they are seeing is current. When an AUS cannot run because a credit report is missing, Navigator says so specifically. |
Submit to AUS | "Send this to DU." | Navigator submits to Desktop Underwriter, Desktop Originator, or Loan Product Advisor, depending on the lender's configuration. Findings come back attributed verbatim, without being summarized into a verdict. |
Request a pre-underwriting summary | "Re-run pre-underwriting summary on this file." | Navigator starts a fresh, focused run on the file and tells the loan officer it will take about five minutes. |
Reach the borrower | "Ask them for the last two bank statements." | Navigator drafts email, texts, and document requests. Everyone waits for the loan officer's approval before it goes out. The approval step names the recipients. |
Send disclosures, order title, issue a preapproval | "Send the initial disclosures." | These actions are available where the lender has configured them. Navigator checks first and fails closed rather than offering an action that will fail when it runs. |
See how it got there | "Show me the income calculation." | Run cards show the arithmetic and where the changes were actually applied. For longer tasks, status updates appear as work runs rather than leaving the loan officer with a spinner. |
Built-in boundaries
Navigator:
Does not make or announce a final credit or pre-underwriting decision.
Does not describe a loan as approved, denied, or declined.
Does not provide legal, tax, or accounting advice.
Does not use protected-class attributes in a decision or rationale.
Does not make an unqualified commitment about a rate, program, or approval.
Does not expose one borrower's information to another recipient.
Masks account numbers except for the last four digits.
Presents verified facts and asks the loan officer how to proceed when judgment is required.
Availability
Detail | Information |
|---|---|
Status | Off by default. Available in beta tenants. |
Enablement | You do not need to contact the account team. There is no separate deployment and nothing for loan officers to install. |
Scope | Per environment. Once enabled, Navigator appears in the loan file for users who already have access to that loan. |
Prerequisites | Pricing, credit, AUS, disclosures, title, and preapproval actions require the corresponding capability to be configured. Navigator checks configuration and declines the action when the prerequisite is unavailable. |
Authentication | Enabling Navigator no longer requires tenant-level OAuth. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article