When new underwriting conditions arrive mid-file

A revised condition list can arrive while documents are already on their way. Before contacting the borrower again, compare the new list with the requests in progress. Otherwise, an old reminder can keep running beside a new request that asks for something different.

The operational question is what changed and which existing actions that change affects. Keep the lender’s current instructions attached to that answer.

Preserve the previous working state

Retain the earlier condition list and the time your team received the revision, following your file procedures. Record which requests were open at that point and which responses had arrived. The previous list provides the context for messages already sent; it should not silently become the current instruction.

Distinguish an added condition from a changed requirement and a repeat of an existing item. Similar wording can still require different evidence. When the difference is unclear, have the responsible processor obtain clarification before asking the borrower to interpret it.

Review the affected requests

For each changed item, inspect the outgoing request, the latest response and the next scheduled follow-up. Decide whether the original request still applies, needs a correction or should stop. Keep the reason in the file so a covering processor does not restart it later.

Check documents already received before asking for another copy. They may answer part of the revised request, but their presence alone does not settle the requirement. The processor should review the evidence against the current instruction and retain any unresolved question.

Tell the loan officer what the revision changes in the processing plan. Describe the additional action or clarification needed without inventing a new closing commitment.

Illustrative change review

This is a sample file situation. Your team has requested a statement for a specified period. Before the borrower responds, a revised condition asks for a different period. The old request remains open.

The processor first confirms that the revision replaces the earlier request. The file note records the revised condition and the decision to stop the earlier reminder. The borrower message can then say: “The document request has changed. Please use the revised request for the statement period listed below. You do not need to send the statement from our earlier request unless we contact you again.”

Use that wording only after confirming the old request is no longer needed. If both periods are required, explain that directly instead. Record which message was sent so the next processor knows what the borrower was told.

Keep the revision visible through completion

Link incoming responses to the current condition and retain the request history. If the borrower answers the earlier message, acknowledge what arrived and explain the remaining request. A borrower who acted on your original instruction should not receive a generic “still missing” reminder with no explanation.

At the next file review, verify that affected reminders and assigned tasks match the revision. Updating a condition note while leaving an obsolete request active creates conflicting instructions.

For a software evaluation, introduce a revised condition after the sample request has gone out. Watch what changes in the file and which decisions your team still makes.

The borrower document collection guide covers the request-to-response work behind that test. Book a walkthrough to follow a document request through the file record.