How often does a pre-approval file lose its original assumptions?

A pre-approval is a promise built on assumptions. The loan officer assumes an income level, an asset source, a property type, and a closing timeline. When the borrower applies, those assumptions should move into the file with the documents. Too often they are replaced by new numbers without a note, and the original reasoning disappears.

Assumption loss is hard to see in a normal pipeline review because the current file looks complete. The missing context only matters when a reviewer asks why the loan amount changed or why a program was dropped. This protocol measures how often the original assumptions survive into the application. It gives a team a way to improve the handoff without blaming the loan officer.

Question and scope

The study asks what share of pre-approval files lose at least one original assumption by the time the application is processed. Scope names the team, the loan officers, the loan types, and the period. A team might study purchase pre-approvals from three loan officers during a quarter. The result applies to that setting and should be reported with the scope.

Define the assumption set before sampling. Include the loan amount, the program, the rate range, the down payment, the asset source, and the occupancy type. Add any condition that the pre-approval letter states explicitly. The set should be small enough to check consistently and broad enough to catch a material change.

Decide what counts as a file. A file begins when the borrower applies and the application is created. A pre-approval that never converts is outside the study unless the team wants to measure conversion separately. The scope should say whether withdrawn files are included and how they are handled.

Defining assumption loss

Assumption loss occurs when a term recorded at pre-approval cannot be found in the application file, or when the application contains a different value without a note explaining the change. A missing term is a loss even if the new value is reasonable. A changed term with a documented reason is a revision, not a loss. The reviewer should check both the value and the note before assigning a category.

The note must be specific enough to explain the change. A note that says "updated" is not enough. The note should name the old value, the new value, the source, and the date. A reviewer should be able to follow the change without calling the loan officer.

Do not count a term that the pre-approval did not state. A pre-approval may leave the property address blank because the borrower has not chosen a home. A blank is not a lost assumption. The protocol should distinguish between a term that was never stated and a term that was stated and later disappeared.

Building the field checklist

Use a short checklist of fields that are both material and easy to verify. Legal name, loan amount, program, occupancy, income type, asset source, and down payment belong on the list. Add the pre-approval expiration date and any stated condition. These fields drive eligibility and disclosures.

For each field, record the pre-approval value, the application value, and whether a change note exists. Mark the field as preserved, changed with a note, changed without a note, or missing. The four states are more useful than a simple pass or fail because they separate a documented revision from a silent loss. A file with several documented changes may still be healthy, while one silent loss can undermine the original recommendation.

Pilot the checklist on five files before the main sample. Ask two reviewers to complete it and compare the results. If they disagree about a field, clarify the definition. A checklist that requires a debate every time will not be used consistently.

Sampling the pre-approval pipeline

Use a sample that covers each loan officer and each major loan type. A sample from one loan officer may reflect a personal habit rather than a team process. A rotating sample over a quarter gives a fairer picture without reviewing every file. Record the selection rule so the next study can repeat it.

Include files that converted quickly and files that took several weeks. A fast conversion may preserve assumptions because the loan officer is still close to the file. A slow conversion may lose them through handoffs. The comparison can reveal where the loss happens.

Exclude files where the borrower changed the loan request before applying. A borrower who decides to buy a different property may legitimately change the occupancy or the loan amount. The protocol should record the change and mark it as borrower-driven. A borrower-driven change is not a process failure.

Tracing the handoff

For each changed or missing field, identify where the change happened. It may occur during the application call, the document review, the underwriting review, or a later condition. The handoff point is more useful than the individual who typed the value. A pattern across files points to a process gap.

Record the evidence for the change. A borrower email, a revised pre-approval letter, or a note in the loan origination system can explain the change. If no evidence exists, the field is a silent loss. The evidence should be linked in the checklist, not copied into a separate document.

Review a few files with the loan officer and the processor together. Ask where the original assumption was recorded and how the next person was expected to find it. The conversation often reveals a note that lives in a personal inbox or a conversation that was never logged. The fix may be a field in the handoff template rather than more training.

Report the share of files with at least one silent loss, the share with a documented change, and the share with no change. Show the sample size and the period beside every number. A single loss rate without the categories can hide whether the problem is documentation or decision-making. Add one example of a documented change so the reader can see what good evidence looks like.

Break the share down by field and by handoff point. A high share of missing asset sources may point to the application call. A high share of changed loan amounts may point to a pricing conversation. The breakdown helps the team choose the first fix.

Pair the share with the consequence when it is visible. A lost assumption that changes the program may delay underwriting, while a lost assumption about a closing date may affect the borrower. The consequence helps the team prioritize the fields that matter most. A loss that never affects the file is still a finding, but it may not be the first one to fix.

What the number can change

A high loss share does not automatically justify a new form or more training. It may justify a required handoff field, a short assumption summary in the application, or a review checkpoint before underwriting. The study should list the changes that could reduce loss before it recommends additional capacity. The team should separate a documentation problem from a judgment problem.

The loan processing support team can test a handoff template on a small group and rerun the protocol. A template with the six key assumptions is easy to test because the team can compare the loss share before and after. The test should run long enough to cover a normal closing cycle. Keep the test group small enough that the rest of the team can continue the normal work.

If the share stays high after the change, the team may have a genuine capacity gap or a loan officer process that requires more support. The mortgage operations support lead can review the application call and the document review sequence. The result should distinguish a handoff problem from a workload problem. A measure that leads to the wrong fix is worse than no measure at all.

Limits and sources of error

The study measures recorded assumptions, not every conversation. A loan officer may have explained a change in a call that was never logged. The file may look like a silent loss when the borrower actually approved the change. Report the limitation and sample the communication log where possible.

The pre-approval letter may not contain every assumption. A letter may state a loan amount and a rate range but omit the asset source. The study can only measure what was recorded. A missing assumption in the letter is a separate finding about the letter template, not a loss in the file.

The sample may miss files that never converted. A pre-approval that was abandoned may contain the clearest example of assumption loss, but it is outside the application file. If the team wants to study conversion, define a separate scope and a separate evidence rule. Report the conversion rate beside the loss share so the reader knows how much of the pipeline the sample represents.

Review cadence

Repeat the study after a change to the pre-approval letter, the handoff template, or the application call. Use the same field checklist and the same sampling rule so the comparison is meaningful. A share that falls while the number of documented changes rises may mean the team is recording more, not losing less. A comparison across different checklists is not valid, so freeze the list before the second round.

Share the result with the loan officers and processors who created the files. Ask which assumption was hardest to find and which change was never documented. The discussion can reveal a field that nobody owns or a note that is stored in the wrong place. The next study should test one of those findings.

End with a single sentence that states the loss share, the period, and the handoff point the team can fix. A precise finding with a named owner is more useful than a long report. The goal is an application that carries the original reasoning forward. The sentence should name the change the team can make, not a cause outside its control.