Field notes / Underwriting

Run a document condition sweep before the underwriter resubmission

A condition sweep that checks each open underwriting item, its source, and the resubmission package before the file goes back.

Editorial cover for “Run a document condition sweep before the underwriter resubmission”

Why the condition sweep matters

The underwriting condition sweep queue at The Mortgage Assistant is designed for a team that cannot rely on hallway updates. Each item carries a loan reference, an owner, a next action, and a date the evidence was last checked. The condition assistant prepares the file and the underwriter or operations owner makes the call that affects a borrower or a closing. Without that split, a routine follow-up quietly becomes an unauthorized commitment.

A underwriting condition sweep control at The Mortgage Assistant begins with a written trigger and a stop rule that survives a busy pipeline. When a file is ready for underwriter resubmission, the condition assistant opens the item in the condition sweep sheet and records the source, the loan reference, and the time observed. The underwriter or operations owner reviews the narrow question and records resubmit, hold, or request a clearer condition before the file advances to the next stage. That boundary matters when one coordinator covers forty loans and the loan officer is in appointments all afternoon.

What the condition record must show

Every underwriting condition sweep record should say who opened it, which document was checked, and what changed in the file. Record the condition list and version, the document supplied for each condition, and the resubmission date and reviewer, along with the date each was observed. Mark an absent document as absent instead of copying a value from a similar loan. The underwriter or operations owner should be able to follow the path in under a minute.

A useful condition sweep sheet entry is short and complete, with the condition list and version and the document supplied for each condition in one place. Write the date and time of the check, because a status can look current after the document has expired. The Mortgage Assistant asks the condition assistant to note the resubmission date and reviewer when the item crosses an underwriter, a title company, or a borrower request. A missing source is a valid entry that tells the underwriter or operations owner what to request next.

To translate this boundary into a scoped position, review our specialist service responsibilities and workflow examples.

Where the condition assistant stops

Access to the underwriting condition sweep file follows a least-privilege rule with an individual account for each assistant. The permission set stays inside the written scope, and the underwriter or operations owner reviews it when the assignment changes. The Mortgage Assistant records the review date with the file so the decision is not buried in an onboarding email. The condition assistant should never quote a rate, extend a lock, or clear a condition without written authority.

The condition assistant may prepare, check, record, and route, but cannot make the decision that changes pricing or a disclosure. The Mortgage Assistant posts that boundary beside the underwriting condition sweep queue so a new assistant does not inherit authority from an earlier file. When a request raises a compliance question, a privacy issue, or a borrower commitment, the case stops for the underwriter or operations owner. The pause is part of the control, not evidence that the queue is slow.

The daily condition sweep

A practical underwriting condition sweep routine begins with the source document, not the stage field in the condition sweep sheet. The condition assistant confirms the resubmission date and reviewer and records the result before moving to the next file. Items that cannot move are routed with a reason and a due date instead of sitting in the queue. The Mortgage Assistant measures conditions evidenced before resubmission, so the team can see whether the routine reduces open work or just moves it.

The Mortgage Assistant keeps the underwriting condition sweep queue small enough to finish, because a queue that never empties hides its oldest file. Each item gets one owner, one next action, and one review date, and the condition assistant updates the condition sweep sheet before the shift ends. A quick source check beats a status refresh, since the stage can be current while the document is absent. The routine should look the same every day so a substitute can pick it up without a briefing.

Source check: U.S. Department of Housing and Urban Development provides the public guidance used to test the assumptions in this workflow.

Conditions that need an underwriter decision

Some underwriting condition sweep items must stop rather than proceed, and a condition that conflicts with a prior approval is one of them. A missing document, two records that disagree, an expired approval, or an unavailable underwriter or operations owner is enough to pause the file. The Mortgage Assistant records the stop reason and the person who can release it, so the pause does not become a lost item. The condition assistant does not guess what the underwriter or operations owner would prefer when the evidence is incomplete.

When underwriting condition sweep touches pricing, a disclosure, a closing date, or a borrower commitment, the dependent action waits. The Mortgage Assistant records the pause reason and the time the issue was raised with the underwriter or operations owner. The condition assistant routes the question instead of resolving it, even when the answer looks obvious. That record is what lets the team explain a delay later without rebuilding the day from memory.

How to verify a resubmission

The close note records what was checked, who approved it, what changed, and what would reopen the file. The underwriter or operations owner should be able to read one record later and explain the close without contacting the condition assistant. The Mortgage Assistant keeps the close note with the condition list and version and the date the decision was made. That standard turns a routine task into evidence the team can defend.

Verification for underwriting condition sweep means checking that the file has a source, a business purpose, and a recorded decision. A sent email or a moved card proves activity, not that the destination field changed. The Mortgage Assistant reviews a small sample against the same definition each month, including one difficult file. If the destination cannot be checked, the item is not complete even when the pipeline says it is. The team can compare this workflow with our [mortgage support services](/services) and the [related operating guide](/blog/themortgageassistant-keep-an-appraisal-reconsideration-log-with-value-evidence).

Continue with our related guide to the next mortgage workflow and compare its handoff points with this one.

The weekly condition handoff

The underwriting condition sweep handoff should travel with the file so the next person sees the same facts the last person saw. The Mortgage Assistant asks for the source date, the current owner, and the next action on every open line. The note should separate a true delay from a file that is simply waiting on the borrower or the investor. That distinction helps the underwriter or operations owner decide where to spend the next hour.

A good handoff also records the files closed without a source, so the gap stays visible. A late document, an investor question, or a changed approval can reopen a closed underwriting condition sweep item. The Mortgage Assistant keeps the handoff to one page with the open files, the conditions evidenced before resubmission, and the exceptions waiting on the underwriter or operations owner. A short handoff that is actually read beats a long report that nobody opens.

The monthly condition review

Once a month, pull a small underwriting condition sweep sample and test the source, the decision, the execution, and the confirmation. Report the sample size and the exceptions, not only a percentage that hides the difficult files. The Mortgage Assistant includes one file that crossed owners and one that was reopened. The review should show whether the control works when volume is high.

The Mortgage Assistant uses the monthly underwriting condition sweep review to test one assumption about the file returns for a condition that was already available. Pick a file where a condition that conflicts with a prior approval, then trace the evidence back to the source and the reviewer. If the trace requires a private message, the record is incomplete and the fix belongs in the form or the rule. The review closes when the change is written down, assigned, and scheduled for a follow-up check.

Common questions answered

What should the team check first on underwriting condition sweep?

Start with the source record and the named owner. The Mortgage Assistant asks the condition assistant to record the condition list and version and the resubmission date and reviewer before the file moves, and the underwriter or operations owner keeps the release decision.

Which underwriting condition sweep decisions stay with the accountable owner?

The underwriter or operations owner owns every decision that changes pricing, a disclosure, a borrower commitment, or a closing date. The condition assistant prepares the evidence and routes the exception instead of resolving it.

How should underwriting condition sweep results be reviewed?

Review a small sample against the same definition each month. The Mortgage Assistant records the source, the decision, the close evidence, and one process change with an owner and a check date.

From field note to operating brief

Turn the workflow into a clear role brief

Bring the recurring work that consumes the most attention. We will help define its scope, evidence, handoff, and review points.

Book a free consultation