On this page
A condition that appears after underwriting can sit unnoticed while the file looks finished. The processor assumes the underwriter will send a clean list, the underwriter assumes the processor saw the note, and the closing date keeps moving closer. A same-day rule gives every new condition a first touch before the next business morning. The rule works only when the team defines what counts as new and who owns the first look.
Why post-underwriting conditions drift
Work after underwriting often arrives through a different channel than the original condition list. An underwriter may add a note in the loan origination system, send an email, or leave a comment in a review queue. If no one owns that channel, the condition waits until someone opens the file again. The delay is usually a routing gap rather than a disagreement about the requirement.
The gap widens when the team measures only the age of the original condition list. A newly added condition can be three days old while the average for the file looks healthy. Counting new conditions separately shows whether the post-underwriting handoff is keeping up. It also gives the processor a reason to check the review queue before the daily stand-up.
Define the same-day window
Write down the start and end of the window in local business time. A common rule is that any condition added before a set afternoon cutoff receives a first touch before the team closes for the day. Conditions added after the cutoff receive a first touch before noon the next business day. The exact hours matter less than applying them consistently.
The first touch does not have to be a full resolution. It can be a review of the requirement, an acknowledgment in the system, and assignment to a preparer. What matters is that the condition has an owner and a next action before the window closes. A first touch that leaves the item unassigned has not changed its risk.
Sort new conditions by dependency
Some conditions need a borrower document, some need a vendor response, and some need only an internal correction. Sort the new items by what they are waiting on before deciding the order of work. A condition that needs a borrower call should go out early enough to reach the borrower during business hours. An internal correction can wait until the afternoon queue clears.
Do not sort by the date the condition appeared alone. A condition added this morning that blocks closing tomorrow deserves attention before an older item that is waiting on a slow vendor. The queue should show both age and dependency, because either one can make an item urgent. The mortgage operations support checklist can hold the sorting rule in plain language.
Assign a preparer and an approver
Every new condition needs two roles even when one person fills both temporarily. The preparer gathers the evidence and writes the response, while the approver decides whether the condition can clear. Keeping the roles visible prevents a specialist from marking work complete without a second look. It also makes the handoff clear when the original processor is away.
The specialist should know which conditions they may prepare and which must go straight to a reviewer. A missing signature page is usually administrative, while a change in income or assets may require a new underwriting decision. Write the boundary into the task brief rather than relying on the specialist to infer it from the condition text. Clear boundaries make the same-day rule safe to run at volume.
Handle conditions that need borrower contact
A new condition that depends on the borrower should leave the queue the same day with a dated request. Use the approved message template and state the document needed, the acceptable format, and the next checkpoint. Record the request in the communication log and on the condition itself. A message that exists only in an inbox cannot be counted or followed up.
If the borrower does not respond by the checkpoint, escalate to the owner rather than sending another identical reminder. The second touch should add a phone attempt, a clearer explanation, or a revised deadline. Repeated form messages train borrowers to ignore the request and hide the fact that the file is stuck. The borrower communication support workflow should define the escalation path.
Measure the rule after thirty days
Count new conditions, first touches inside the window, and items still unassigned at the end of the day. Add a small sample review of ten conditions to check whether the first touch was accurate. The CFPB's Regulation X recordkeeping expectations support keeping a dated trail, but the operational test is simpler. A reviewer should be able to see who touched the condition and what happened next.
Look for patterns rather than a single percentage. If most misses come from one underwriter's channel, fix the routing rather than asking the processor to check more often. If misses cluster on Fridays, adjust the cutoff or the staffing coverage. Share the pattern with the reviewers who create the conditions so they can see the effect of a late note. The rule should change the queue, not become another report that nobody uses.
Keep the measurement light enough to run every week. A count of new conditions, first touches, and open assignments is usually enough, plus one example of a good handoff and one that failed. Do not wait for a perfect data set before starting, because the first month will expose the fields the team forgot to track. Adjust the fields once, then leave them stable long enough to compare.