How to build an underwriting submission packet

Underwriters don't reject files because you missed one document. They reject files because they can't find the document you already have.

A clean submission packet is two things: a predictable folder structure with consistent filenames, and a short index that tells the underwriter where everything is. Neither is complicated. Both get skipped constantly — and if you'd rather not build it manually, a one-click export automates the whole thing.

What underwriters actually hate seeing

Before getting into structure, here's what causes re-runs and conditions that have nothing to do with the borrower's actual situation:

Duplicate versions. If you have Smith_W2_final.pdf and Smith_W2_final_v2.pdf in the same folder, the underwriter has to figure out which one you meant. They'll often flag both and ask you to clarify.

Unlabeled files. scan0001.pdf is not a document label. If an underwriter has to open every file to figure out what it is, you're adding hours to their review.

Mixed doc types in a single file. A PDF that contains a paystub, two months of bank statements, and an LOE doesn't fit anywhere cleanly. It either gets split by the underwriter or reviewed out of context.

Missing pages. The most common condition on any file. Statement page 3 is blank? Still needs to be in the PDF. Underwriters count pages against the sequence.

Recommended folder structure

Use categories, not a flat list. A flat list of 40 PDFs with no folders is almost as hard to navigate as a disorganized email thread.

01_ID/
02_Income/
03_Assets/
04_Property/
05_LOEs_Explanations/
06_Disclosures/         (optional)
07_UW_Conditions/       (optional, for re-submissions)

This order roughly matches how underwriting reviews a file: start with who the borrower is, then income, then assets. Property docs come fourth because they're often the last items collected.

Naming conventions

The goal is that any file name should tell you three things without opening the file: who it's for, what it is, and what time period it covers.

A simple convention that works:

BorrowerLastName_DocType_DateRange.pdf

Examples:

• Smith_Paystubs_2026-01-01_to_2026-01-31.pdf
• Smith_W2_2024.pdf
• Smith_BankStatement_Chase_2026-01.pdf
• Smith_LOE_LargeDeposit_2026-01-15.pdf

If the file is a re-submission, add a version indicator rather than creating a second unlabeled copy:

• Smith_BankStatement_Chase_2026-01_v2.pdf

The submission index (cover sheet)

A one-page index at the front of the packet saves the underwriter from hunting for context. It doesn't need to be formatted nicely. It needs to contain:

• Borrower name(s) and loan number
• Loan type and occupancy
• Property address
• Income type summary (W2 / self-employed / K-1 / rental / other)
• Assets summary (where the down payment and reserves are coming from)
• Any known red flags with a brief explanation (gap in employment, large deposit, recent credit inquiry)
• Where specific items live, if the file is complex

That last item is the one most people skip. If the underwriter is looking for the LOE for a $9,000 deposit, a note that says "see 05_LOEs_Explanations/Smith_LOE_LargeDeposit.pdf" saves a phone call.

QC before you send

This takes five minutes and prevents most first-pass conditions:

• Open each statement and confirm all pages are present. Page count on the PDF should match the statement's page numbering.
• Check that dates match what's on the 1003 and AUS findings. A paystub with a February date won't work if underwriting expects a more recent one.
• Confirm there are no duplicate filenames in the same folder.
• Make sure LOEs are included for every large deposit and credit event that you know underwriting will ask about.
• Check that every document in the index actually exists in the folder.

Keeping the packet clean during conditions

When underwriting sends back conditions, the temptation is to add new files on top of what you already submitted. Resist this. Use the 07_UW_Conditions/ folder for the second submission, label each item with the condition number if you have it, and note in the index what changed from v1 to v2. A conditions tracker makes it easier to know which items are being resubmitted and which are still outstanding.

The underwriter reviewing your re-submission doesn't always have the prior packet open. Make it obvious what's new.