Mortgage loan file submission checklist
Use this practical audit before handing off a residential mortgage file. It helps loan officers catch incomplete or unusable documents, organize open questions, and prepare a cleaner submission package.
Best for: loan officers and small mortgage teams that want a repeatable pre-submission review without replacing their LOS, processor, or product-specific checklist.
Outcome: a concise file summary, a list of missing or questionable items, and a borrower follow-up draft for anything that needs clarification.
What this checklist is, and is not
This is an organization and communication layer for a loan file. It is not a universal underwriting checklist: required documents vary by lender, channel, loan product, borrower profile, and jurisdiction.
- Use it to: organize file context, spot obvious document-quality problems, and draft clearer follow-up requests.
- Do not use it to: calculate qualifying income, make approval decisions, interpret policy, or replace lender and investor requirements.
- Keep sensitive files protected: use your approved LOS and document systems. Do not paste borrower PII or source documents into an unapproved AI tool.
1. Capture the submission context
Start with the facts a processor or reviewer needs to understand the package. Keep the summary inside your approved notes system.
| Field | Fill in |
|---|---|
| Transaction | Purchase / Refinance |
| Loan product and channel | Conventional / FHA / VA / USDA / Non-QM; retail / broker / correspondent |
| Occupancy and property | Primary / second home / investment; property type |
| Target closing date | |
| Known complexity | Self-employed, job change, gift funds, multiple properties, nonstandard income, etc. |
| Open questions | Items that require processor, underwriter, or product-guideline confirmation |
2. Check document usability before submission
The first pass is simple: confirm that each expected item is present and usable. Frequent re-request triggers include:
- Screenshots instead of complete downloaded statements.
- Missing pages, including pages marked intentionally blank.
- Missing borrower name, account number, institution name, or statement period.
- Documents that are expired, illegible, cropped, or inconsistent with the file notes.
- Unexplained large deposits, employment changes, or other facts that need a human follow-up.
3. Copy the pre-submission audit prompt
Use this only with a sanitized list of file facts and document statuses. Do not paste borrower PII or source documents into an unapproved AI tool.
You are helping a mortgage loan officer organize a pre-submission file audit. Do not make underwriting decisions, calculate qualifying income, or claim that the file is complete. Only organize the information provided and identify obvious follow-up questions. File context: - Transaction and loan product: [fill in] - Occupancy and property type: [fill in] - Target closing date: [fill in] - Known complexity: [fill in] Document status list: [Paste a sanitized list such as "bank statement: all pages present, name visible, statement is 45 days old"] Return: 1. A short file-summary paragraph. 2. A table with: item, status, obvious quality issue, and next human action. 3. A separate list titled "Confirm with processor or underwriter." 4. A borrower-friendly follow-up draft for missing or unusable items. Use cautious language. Do not state that any document satisfies a guideline.
4. Prepare the handoff
- Reconcile the audit against the actual file and your product-specific checklist.
- Remove resolved items and confirm that every open question has an owner.
- Separate borrower follow-ups from questions for the processor or underwriter.
- Save the final summary in your approved LOS notes or team system.
- Send only the borrower requests that you have personally reviewed.
Example audit output
File summary: Purchase file targeting a June closing. The document list appears organized, but two items need borrower follow-up and one item needs processor confirmation before submission.
- Bank statements: re-request complete downloaded statements; screenshots and two pages are missing.
- Pay stub: request a current, legible copy because the uploaded file is cropped.
- Gift funds: confirm the required documentation and sequence with the processor.
The output is a work queue, not a statement that the file satisfies underwriting requirements.
Related Tool Navigator guides
- AI document collection workflow for mortgage pros
- Borrower document request checklist template
- Mortgage AI stack
- Best AI tools for loan officers
This template is an organizational aid, not underwriting guidance. Follow your lender, investor, regulator, and company requirements, and review every output before use.