The gap between submission and ready-to-review
Ask most loan officers what slows their pipeline and they will tell you underwriting turnaround. But if you trace the active time on a file, a different pattern appears. The single most common source of delay in the files we have worked through is not a credit complexity or an appraisal question. It is a piece of paper that was never submitted.
A borrower sends in three bank statements when the program requires four. A pay stub is dated 40 days ago and the lender's guidelines say within 30. Section 5 of the 1003 is blank. The W-2 is there for the current year but not the prior year. These are not judgment calls. They are checkable facts about whether a document exists and whether its date falls within an acceptable window.
The problem with current practice is that these checks happen in the middle of the review cycle. A processor starts working through the file, gets several pages in, and discovers a bank statement is missing month two. They pause, contact the borrower, wait. Two days later the borrower sends a new batch, some of which duplicates what was already submitted. The processor reorganizes, continues, and finds something else. Each round of contact adds days to the timeline.
What completeness checking at intake means in practice
Checking completeness at intake means running the check the moment documents arrive, before any human review begins. The output is a gap list, not a judgment about the application. Here are the types of checks that matter most:
- Date coverage for bank statements. Most purchase programs require the two or three most recent months of full statements, with no gaps in the coverage period. A stack of three statements that covers months 1, 2, and 4, missing month 3, fails this check even though three statements were submitted. The completeness pass reads the statement period dates from each page and verifies the sequence is continuous.
- Paystub recency. The most recent pay stub needs to be dated within a program-specific window, commonly 30 days of application. Maestro reads the pay date from the stub and compares it to the application date. Stubs outside the window get flagged before anyone starts reviewing income numbers.
- W-2 year coverage. Most programs require W-2s for the two most recent tax years. If a borrower submits a single W-2 and it covers only the current year, the prior year is missing. That is a condition waiting to happen at underwriting.
- 1003 section completeness. The Uniform Residential Loan Application has required sections that must be completed before a file can proceed. Section 1 (borrower information), Section 3 (financial information real estate owned), and the declaration questions are common sticking points. Blank required fields appear in the gap report rather than at the underwriter's desk.
- Tax return schedules for complex income. A self-employed borrower submitting a 1040 needs Schedule C. A borrower with rental income needs Schedule E. If the base return is present but the schedule is missing, the completeness check surfaces that gap immediately rather than after a processor has spent 40 minutes reorganizing the file.
Why a single, consolidated contact matters
The standard workflow produces multiple rounds of borrower contact. The first round catches the obvious gaps. The second catches what the first missed because the processor had not yet worked far enough into the file to know what was needed. Sometimes there is a third round.
Each round adds at least a day to the timeline, often more, because borrowers are not sitting at their desk waiting for document requests. Consolidating all gaps into one request, sent at the moment of intake, means the borrower gets one list and the processor gets one batch of corrections rather than a drip of partial responses.
This matters for the borrower experience as much as for operational efficiency. A borrower who receives a four-item list on Monday and provides everything by Wednesday is in a different mental state than a borrower who gets one request, responds, then gets another request three days later, then another. The origination process already carries enough complexity for borrowers. Multiple contact rounds on something as mechanical as document completeness compounds that difficulty unnecessarily.
The limits of automated completeness checking
It is worth being precise about what completeness checking does and does not cover. It covers document existence, date windows, and basic required-field presence. It does not cover document authenticity or whether the information a document contains is accurate.
Similarly, the completeness check works from general industry-standard requirements. If a specific lender program requires stricter documentation than the baseline (some non-QM products have additional requirements), those program-specific rules need to be configured separately. The base layer catches the industry-standard minimums that apply to the large majority of conventional applications. Lender-specific parameters build on top of that foundation.
We also want to be clear that completeness checking is not the same as consistency checking. Whether the income numbers across documents reconcile, or whether a large deposit on a bank statement requires sourcing documentation, is a separate analytical layer. Completeness tells you what is present. Consistency tells you whether what is present agrees. Maestro runs both, but they are distinct outputs and it matters which problem you are trying to solve at a given point in the workflow.
Where this fits in the origination workflow
The completeness report lands alongside the uploaded documents in the loan officer's or processor's queue. Before they open the first PDF, they can see the gap list. If there are items on the list, they contact the borrower immediately rather than starting review, discovering the gap mid-stream, and then contacting.
In the cases where the file is complete, the report confirms it, and the processor can begin review knowing they will not be interrupted by a missing document. That confirmation has value too. A processor who knows the file is complete reviews differently than one who is mentally tracking which documents they still expect to arrive.
The goal is to make the first meaningful action on a file the actual review, not the scavenger hunt that precedes it. Conditions issued by underwriters cost time because they require going back to the borrower and resubmitting. Conditions for missing documents that could have been caught at intake are the most avoidable type. Catching them at the front of the process is what the completeness check is built to do.