Build a Pre-Approval Document Checklist: scope and evidence
Build a Pre-Approval Document Checklist starts with a written boundary. Name the loan, the source, the owner, the evidence, and the point where the work must stop. A clear rule keeps coordination separate from lending and credit decisions.
The main risk is that a file can move forward with missing or unverified documents. Record the source and time before changing a status.
Capture the evidence
A usable record includes borrower, document, request date, source, reviewer, and status. Keep the source beside the record so another reviewer can reconstruct what happened.
The loan processing lead confirms the decision or exception. The coordinator can request approved documents, check completeness, and route lending questions, but should not fill a gap with an assumption.
Separate preparation from judgment
Decisions about credit and eligibility decisions remain with the authorized owner. Use three labels: proceed under the rule, pause for missing evidence, and escalate for a decision.
Run the review
Review missing documents, age, and resubmission. For example, a borrower uploads an outdated bank statement. Record what evidence was available and who owned the next step.
Pilot one workflow
Start with one loan type. Test the checklist on a small batch and review exceptions with the owner.
Use the related service scope and pipeline guide for context. Review CFPB mortgage guidance before changing a workflow.