Underwriting turn times measure how long a file waits between submission and an underwriting decision. On bank statement and business files they stretch because the underwriter must rebuild income from months of deposits, source unusual credits and chase missing pages. Most lost days come from queue time and incomplete submissions, not from the review itself.
What counts as an underwriting turn time?
An underwriting turn time is the elapsed time between two dated events on a loan file, and the events a lender picks change the number. The common definition runs from complete submission to the first decision. Lenders that only track that one clock miss the time spent in queues and on conditions.
A file passes through several clocks, and each one answers a different question:
- Queue time runs from submission to the moment an underwriter opens the file. It measures staffing and assignment, not skill.
- Touch time is the hours an underwriter actually spends on the file. It is short on a clean W-2 file and long on a 24-month bank statement file.
- Initial decision time runs from submission to the first approval with conditions, suspense or denial. This is what most brokers mean when they ask about turn times.
- Condition turn time runs from the moment conditions come back to the moment the underwriter signs them off.
- Submission to clear to close covers the whole underwriting stage, including every round of conditions.
Count in business days or calendar days, but pick one and keep it. A file submitted on Friday afternoon looks two days slower in calendar days than in business days, and mixing the two in one report makes comparisons meaningless.
Write the definitions down. If one underwriter starts the clock at submission and another at assignment, the team report will show differences that come from bookkeeping, not from work.
Why underwriting turn times run longer on bank statement files
Underwriting turn times run longer on bank statement files because the income has to be built rather than read. A W-2 file gives the underwriter a salary on a pay stub. A bank statement file gives them 12 or 24 months of deposits that must be totalled, cleaned of transfers and one-time credits, and reconciled with the business story.
The extra work falls into a few tasks:
- Completeness checks. Every month and every page must be present, and each closing balance should match the next opening balance. One missing page can hold a file for days.
- Deposit totals. The underwriter adds up deposits per month, then removes transfers between the borrower's own accounts, refunds, loan proceeds and other credits that are not business income.
- Large deposit sourcing. Any deposit outside the normal pattern needs an explanation and often a document.
- Expense treatment. The program's expense factor, a CPA letter or a profit and loss statement turns gross deposits into qualifying income.
- Business checks. Ownership percentage, time in business and the business license or registration all need proof.
Business loans and merchant cash advance files add their own steps: NSF and overdraft counts, existing debt payments visible on the statements, and seasonal swings in revenue. Each of these is a question that someone has to answer from the statement lines.
The split of work between the processor and the underwriter matters here. When the processor confirms pages, accounts and obvious gaps before submission, the underwriter starts with analysis instead of document hunting. The guide to how loan processor and underwriter roles divide the work covers where that line usually sits.
One bank statement file and its underwriting turn time, day by day
A single file shows where underwriting turn time actually goes. The example below is a fictional 12-month business bank statement purchase loan. Every date and event is made up for illustration, and the day numbers are business days after the broker's submission.
| Business day | Event | Who held the file |
|---|---|---|
| 0 | Broker submits the file with 12 months of business statements | Setup desk |
| 1 | Setup finds month 7 has pages 1 and 2 of 4; file suspended | Broker |
| 3 | Missing pages arrive; file placed in the underwriting queue | Queue |
| 6 | Underwriter opens the file | Underwriter |
| 7 | Underwriter totals deposits, finds two transfers from a personal account and a $38,000 deposit in month 4 | Underwriter |
| 7 | Approval with 6 conditions issued | Broker and borrower |
| 12 | Borrower returns the conditions; the large deposit letter has no supporting document | Queue |
| 14 | Underwriter rejects the deposit condition | Borrower |
| 17 | Invoice and contract for the deposit arrive | Queue |
| 18 | Underwriter clears the remaining conditions; clear to close | Closing |
The same file gives three different turn times depending on the clock:
- Submission to initial decision: 7 business days.
- Queue time before first review: 3 business days after the file was complete, plus 2 days in suspense.
- Submission to clear to close: 18 business days.
The underwriter's touch time on this file was perhaps a day in total. The rest was waiting: on missing pages, on the queue and on a condition answered with half of what it asked for. Two fixes would have taken roughly a week off. A page count at the broker's desk would have removed the suspense, and a condition worded as "letter of explanation plus invoice or contract" would have avoided the rejected round.
How should a lender measure underwriting turn times across the pipeline?
A lender should measure underwriting turn times as a median and a high percentile per file type and channel, counted from dated events in the loan system. Averages hide the stuck files. A median of four days with a 90th percentile of fifteen days tells a different story from an average of six.
Cut the numbers by file type
Separate W-2 files, bank statement files, business loans and any other product with its own document set. Mixing a two-day salaried refinance with a ten-day 24-month bank statement file produces a number that describes neither. A lender that adds bank statement programs will see its blended turn time rise even if nothing got worse.
Cut by stage
Report queue time, initial decision time and condition turn time separately. A rising queue time points to staffing or assignment rules. A rising condition turn time points to weak condition wording or slow borrowers. The fixes are different, so the numbers should be too.
Cut by source
Brokers, branches and loan officers submit files of different quality. Track the share of files suspended at setup and the conditions per file by source. A source that sends incomplete files every week is a training conversation, and the data makes it a short one.
Use the system dates
Pull the dates from the loan origination system rather than from a spreadsheet someone updates by hand. Manual logs drift, and an underwriter who forgets to log an opening can make a fast file look slow. Credit unions and small lenders without a full reporting setup can still get far with an export of submission, assignment, decision and clear-to-close dates. The article on bank statement analysis for credit unions covers how smaller lending staffs fit statement review into member lending.
Steps that shorten underwriting turn times before the file is assigned
The steps that shorten underwriting turn times most happen before an underwriter sees the file. A setup check for completeness, a standard document list per program and a statement summary attached at submission remove the suspense and queue days that make up most of the delay.
A setup checklist for statement files
- Confirm every month in the lookback period is present for every account the borrower listed.
- Count pages against the "page x of y" footer on each statement.
- Check that each closing balance matches the next month's opening balance.
- Confirm the account holder name matches the borrower or the business.
- List deposits above a set threshold for the underwriter, with the date and amount.
- Note NSF and overdraft events per month.
Each line takes minutes, and each one that fails would otherwise become a condition days later.
Attach the arithmetic
The underwriter still makes the call on income, but they should not start by typing deposits into a spreadsheet. TrueBankFlow reads multi-month statements, lines up monthly deposit totals, and flags large deposits, NSF fees and overdrafts with the statement line behind each one, so the underwriter starts from figures they can check.
Write conditions that close in one round
A condition that names the exact document, the account, the month and the reason closes faster than "provide explanation for deposits." The example file above lost a week to one vague condition.
Assign by skill, not only by turn
Route bank statement and business files to underwriters who handle them every week. A generalist who sees one a month will be slower and will issue more conditions, and the queue time saved by round-robin assignment is lost on the review.
Underwriting turn time targets that make files slower
Underwriting turn time targets backfire when they reward the first decision instead of the final one. An underwriter measured on initial decision time can issue a quick approval with twelve conditions, and the file then spends two weeks in condition rounds. The headline number improves while closings get later.
Other habits that look fast and are not:
- Suspending instead of conditioning. Suspending a file for one missing page stops the clock in some systems. The report looks good and the borrower waits longer.
- Stopping the clock on weekends selectively. Business-day counting is fine, but only if it applies to every file and every report.
- Excluding "exception" files. Removing the hard files from the report hides exactly the cases that need attention. Report them separately instead.
- Rushing the statement review. Skipping the deposit sourcing to hit a number creates a condition later, or a defect that quality control finds after closing.
- One target for every product. A single goal for W-2 and 24-month bank statement files either punishes the underwriters who take the hard files or lets the easy files drift.
A sounder target pairs a turn time with a quality measure: initial decision within a set number of days, and conditions per file or condition rounds below a set level. Each number keeps the other honest.
When underwriting turn times call for more capacity
Underwriting turn times call for more capacity when queue time keeps rising while touch time, conditions per file and setup suspense rates stay flat. That pattern means the files are clean and the reviews are efficient, but there are more files than underwriter hours. Process fixes will not close that gap.
Signs the problem is capacity rather than process:
- Queue time grows week over week while the share of incomplete submissions does not.
- Underwriters carry more open files than the team's normal range for the product.
- Turn times spike with volume and recover when volume drops.
Lenders have three ways to add hours. They can hire and train, which takes months to pay off on bank statement files. They can move routine tasks such as page checks and deposit totals off the underwriter's desk to processors or software. Or they can send overflow to an outside firm, which the guide to contract underwriting for overflow and specialty files weighs against hiring.
Whichever route a lender takes, keep the measurement the same before and after. A change that moves the median but not the 90th percentile has helped the easy files and left the hard ones where they were.
If statement arithmetic is where your underwriters lose the most hours, request a TrueBankFlow setup and test it on files from your own queue.