Table of contents
A condition list can look healthy while a file quietly stalls. The count shows twenty open conditions, the team is busy, and nobody notices that four of them have waited eleven days. Aging turns that list into a priority signal. It shows which conditions are moving, which are waiting on someone, and which have lost their owner.
A weekly review is easier to sustain than a daily deep dive. It gives the team a fixed moment to compare age against the file's closing date and the lender's requirement. It also creates a record of what was decided, not just what was reviewed. This guide describes a practical format that works for a processing pod of three to ten people.
Pick the age that matters
Not every condition should age from the same starting point. An initial approval condition may age from the date the file entered processing, while a re-underwrite condition may age from the date the new document arrived. Choose a start date that matches the event the team is actually managing. Write the definition down and use it every week.
Show both the age in days and the time remaining before the deadline. A condition that is nine days old with two days left is more urgent than a condition that is twelve days old with three weeks left. The pair prevents the review from becoming a simple oldest-first list. It also helps the team explain why a newer condition is being handled first.
Exclude conditions that are waiting on a documented third party. If the appraisal desk has confirmed a date, the condition is not stalled; it is scheduled. Keep it on the list with a next-check date so the team does not forget it. The distinction keeps the review focused on work the team can influence.
Rank by consequence, not only age
A simple age sort can push a low-impact condition to the top while a closing blocker sits in the middle. Add a consequence field with a short set of values such as closing blocker, borrower action, underwriting decision, and routine follow-up. The field should be assigned when the condition is created, not guessed during the meeting. That early assignment gives the reviewer a consistent signal even when the file changes hands.
Closing blockers come first in the review even when they are younger than routine items. A missing signature on a closing document can stop funding, while a routine insurance update may wait a day. The ranking should reflect that difference. The team should agree on the values before the first review.
Review the ranking when a file changes stage. A condition that was routine during processing may become a closing blocker after the closing disclosure is issued. Update the field at the stage change and note who changed it. The review should catch stale rankings as well as stale conditions.
Build a one-page review sheet
The sheet should fit on one screen and contain the fields the team will actually use. Include the loan number, borrower, condition, start date, age, deadline, owner, consequence, and next action. Add a column for the last contact and the next check date. Keep free-text notes short enough to scan.
Do not build a second system of record. If the loan origination system already holds the condition data, export it or link to it. The review sheet is a working view, not a new source of truth. A duplicate record will drift within a week and the team will stop trusting it.
Sort the sheet by consequence and then by deadline, not by loan number. The order should match the conversation the team is about to have. Put the oldest stalled items in a separate block so they are visible without dominating the list. The loan processing support team can help design the export.
Assign a next action to every stalled item
Every item that appears in the review should leave with a next action, an owner, and a date. An action such as "follow up" is not specific enough. Say who will call, what they will ask, and when they will report back. A review that ends with a list of concerns has not changed the week.
If the next action belongs to the borrower, record the channel and the deadline. If it belongs to a lender or a title partner, record the contact and the escalation path. If the team does not know who owns the action, that is the finding for the meeting. An unowned condition is a stalled condition with a different label.
Set a recheck date for actions that depend on another party. The date should be short enough that a missed response is caught before the closing date. A three-day recheck on a closing blocker is reasonable; a weekly recheck on a routine item may be enough. The recheck date belongs on the same sheet.
Run the meeting in thirty minutes
Start with the closing blockers and the oldest stalled items. Spend the most time on the items where the next action is unclear. Read the owner and the date aloud before moving on. The spoken commitment is easier to remember than a row in a spreadsheet.
Do not use the meeting to review every open condition. The sheet already shows the routine items, and reading them aloud wastes the group's attention. Ask the owners to update the sheet before the meeting and bring only the exceptions. A short agenda protects the meeting from becoming a status recital.
End with a count: how many items are stalled, how many have an owner, and how many have a next date. Compare the count with last week. If the number of unowned items is rising, the problem is intake or assignment, not effort. The mortgage operations support lead can review the pattern monthly.
Review the definitions quarterly
Age definitions and consequence values can drift as the team changes lenders or stages. Review the definitions every quarter and after a major process change. Ask the processors which fields they no longer trust and which ones create debate. A field that needs a debate every week should be simplified or removed.
Keep a short change log for the review format. Record the date, the change, and the reason. A change log helps a new team lead understand why the sheet looks the way it does. It also prevents the team from reintroducing a rule that was removed for a good reason.
Use one or two examples to show the review working. A file that was rescued before closing and a file that stalled despite the review are both useful. The first shows the value, and the second shows where the definition missed a dependency. A weekly review improves when the team studies its own misses.
The Consumer Financial Protection Bureau's mortgage resources emphasize clear timelines for borrowers. An aging review supports those timelines by catching stalled conditions early. It also gives the team a shared language for the work that remains. Keep the review on the calendar even during a quiet week, because a missed week is when the oldest items disappear from view.