# Pre Underwriting Review at the Lender's Setup Desk

- Author: TrueBankFlow (https://www.truebankflow.com)
- Published: 2025-05-11
- Updated: 2025-05-11
- Category: Loan desk operations
- Canonical: https://www.truebankflow.com/blog/pre-underwriting-review

> How a lender's pre underwriting review at the setup desk checks completeness, eligibility and statement quality before an underwriter is assigned.
A pre underwriting review is the check a lender's setup desk runs on a submitted file before any underwriter is assigned. It confirms the required documents are present, the loan fits the program's basic eligibility rules and the bank statements are complete and readable. Files that pass go to the queue. Files that fail go back with one list.

## What is a pre underwriting review at the setup desk?

A pre underwriting review at the setup desk is an intake step done by setup staff, sometimes called loan setup or file review specialists, on the day a file is submitted. It ends with one of three outcomes: accept into the underwriting queue, suspend with a list of missing items, or return because the loan does not fit the program.

The review exists to protect underwriter time. An underwriter who opens a file and finds three months of statements missing has lost the time it took to open, read and write back. A setup reviewer can catch the same gap in minutes, before the file uses a place in the queue.

Setup is not underwriting. The reviewer does not calculate qualifying income, decide whether a deposit is acceptable or weigh compensating factors. They check that the material an underwriter needs is there, in a usable form, and that nothing in the file plainly rules out the program. The line between those tasks needs to be written down, and the last section of this guide covers where it usually falls.

Lenders with underwriters in several locations rely on this step more, because a clean, consistent file is what lets anyone on the team pick it up. The guide to [running a remote underwriting team](/blog/remote-underwriting-team) covers how distributed teams share work once files reach the queue.

## Completeness checks in a pre underwriting review

Completeness checks in a pre underwriting review confirm that every document the program requires is in the file, signed where it must be, current enough to use and matched to the right borrower. A setup reviewer works from a document list per program, not from memory, and marks each line present, missing or unusable.

A typical list for a bank statement purchase file covers:

- **Application and disclosures:** a signed application, credit authorization and the lender's required disclosures.
- **Credit:** a credit report within the program's age limit.
- **Income documents:** the full lookback of statements for each account used, business ownership proof, and the expense method the program uses, such as a CPA letter or a profit and loss statement.
- **Asset documents:** recent statements for every account used for down payment, closing costs or reserves.
- **Property and transaction:** the purchase contract with all addenda, and an appraisal order or the appraisal itself.
- **Identity:** a government ID and any identity checks the lender requires.

Two habits make this step faster. Use the same document names as the broker's checklist, so a missing item can be named in words the broker recognizes. And check dates as well as presence: a statement older than the program allows is as missing as no statement at all.

## Eligibility screening during pre underwriting review

Eligibility screening during pre underwriting review tests the file against program rules that have yes-or-no answers: loan amount limits, loan-to-value, minimum credit score, property type, occupancy and state availability. These are facts the reviewer can read off documents. Anything that requires weighing evidence belongs to the underwriter.

Good screening questions are binary:

- Is the loan amount within the program's minimum and maximum?
- Is the loan-to-value at or below the maximum for the credit score and occupancy?
- Does the middle credit score meet the program floor?
- Is the property type allowed, and is the property in a state the program covers?
- Does the lookback period submitted match the program the broker chose, 12 or 24 months?

A file that fails a binary rule goes back with the reason, quickly. Telling a broker on day one that a loan-to-value is two points over the limit saves them a week and gives them time to restructure. Holding the file for an underwriter to discover the same fact a week later is one of the quieter sources of [mortgage closing delays](/blog/mortgage-closing-delays).

Leave borderline cases alone. If the program allows a higher limit with reserves, the reviewer flags it for the underwriter rather than deciding whether the reserves qualify.

## How does pre underwriting review test bank statement quality?

Pre underwriting review tests bank statement quality by confirming the statements are the bank's own documents, cover every month without gaps, include every page, carry the right account holder and balance from one month to the next. A statement set that fails any of these cannot support an income figure, so it goes back before an underwriter starts.

The checks, in the order a reviewer usually runs them:

1. **Source format.** The statement is a bank-issued PDF or a scan of the printed statement, not a screenshot, a transaction export or a retyped list.
2. **Period coverage.** Months run consecutively for the full lookback, with the most recent one inside the program's age limit.
3. **Page completeness.** The page numbering on each statement runs without a gap. Blank final pages still count.
4. **Account holder.** The name on the statement matches the borrower or the business the borrower owns.
5. **Balance continuity.** Each month's ending balance equals the following month's beginning balance. A mismatch means a missing statement or a missing page.
6. **Legibility.** Amounts and dates can be read on every page. Faded scans and cropped margins are returned.

The reviewer can also note, without judging, the items an underwriter will want to see first: deposits far larger than the usual pattern, NSF fees and overdrafts, and transfers from accounts not in the file. TrueBankFlow reads statements by layout, runs a balance check before averaging, and flags out-of-pattern deposits, NSF fees and overdrafts with their dates and statement lines, which turns that note into a printout the underwriter can open alongside the file.

Business loan files use the same checks with a longer list of accounts. Lenders funding operating businesses often want every operating account, and the guide to [commercial loan underwriting](/blog/commercial-loan-underwriting) explains what the underwriter then does with those statements.

## A pre underwriting review worksheet for one bank statement file

A pre underwriting review worksheet records each setup check, its result and the action taken, so the underwriter and the broker can both see why a file was accepted or suspended. The example below is for a fictional 12-month bank statement purchase file. All values are examples.

| Check | Example result | Action |
| --- | --- | --- |
| Signed application and credit authorization | Present | None |
| Credit report age | 18 days | None |
| Loan amount and loan-to-value | $512,000, 80% | Within program limits |
| Middle credit score | 701 | Meets floor |
| Lookback months, business checking ending 3390 | 12 of 12 present | None |
| Page completeness | November statement reads 1 of 5; pages 1 to 3 present | Suspend: request pages 4 and 5 |
| Balance continuity | October ending equals November beginning; November ending balance prints on the missing last page | Recheck when pages 4 and 5 arrive |
| Account holder | Business name matches articles of organization | None |
| Source format | Bank PDFs, except June, which is a screenshot | Suspend: request bank PDF for June |
| Expense method | CPA letter present, dated within 60 days | None |
| Asset statements | Personal savings, 2 months, all pages | None |
| Items noted for underwriter | One deposit of $19,400 in August, about three times the monthly norm; 2 NSF fees in March | Noted, not judged |

Outcome: suspended with two items, the November pages and the June statement, sent to the broker in one message on the day of submission. The reviewer's note on the August deposit goes into the file so the underwriter sees it first. It does not go to the broker yet, because asking for an explanation is the underwriter's call.

## Where pre underwriting review oversteps

Pre underwriting review oversteps when setup staff start making credit judgments: deciding a deposit is not business income, rejecting a letter of explanation, or calculating qualifying income for the underwriter to accept. Those calls carry credit authority, and a setup reviewer usually holds none. The fix is a written list of what setup decides and what it only notes.

Common overreach:

- **Requesting explanations.** Asking the borrower about a large deposit before the underwriter has seen the file often produces a letter that answers the wrong question.
- **Recalculating income.** A setup figure that differs from the broker's starts an argument the underwriter then has to settle.
- **Returning borderline files.** A file near a limit that the program allows with conditions should reach an underwriter.

There are also cases where a file should skip the full setup step. A resubmission that only adds a few cleared items can go straight back to the original underwriter. A file already reviewed by the same lender in a prior submission, with no new documents, needs a light check rather than a full one.

Setup findings are also worth sending back upstream. When the same broker submits files with screenshots in place of statements three times in a month, a short note with the examples and the program's document list changes the next submission more than any number of suspense notices. Keep a running tally of suspense reasons per source, share it with the account executive who manages that broker, and review it together each quarter. The tally also tells the lender which parts of its own document list are unclear, since a reason that appears across many unrelated brokers usually points to wording on the lender's side rather than to careless submitters.

Measure the step itself. Track the share of files suspended at setup, the most common reasons, and how often an underwriter finds a completeness gap that setup passed. If statement checks are taking most of your setup time, [see how TrueBankFlow handles them](/get-started).