Learn how mortgage processors manage loan condition aging, set practical SLAs, and clear stalled PTD/PTF items before files miss lock or closing deadlines.
Open loan conditions do not become closing emergencies overnight. They age. A VOE that sat untouched for four days, an HOI binder that bounced twice, or a title cure with no next-touch date quietly push the file past the desk's internal SLA—and often past the borrower's rate lock buffer. Processors who treat condition aging as a daily metric clear more files on time than desks that only react when underwriting re-suspenses the loan.
This guide shows mortgage processors and loan officers how to define condition aging, set practical SLAs, run a simple aging report, and intervene before stalled items become delay fees, lock extensions, or last-minute fire drills.
Condition aging is the time an open condition has spent without meaningful progress. Meaningful progress is not a status flip in the LOS. It is a documented next action: a borrower ask with acceptance criteria, a vendor follow-up with a due date, or an underwriting clarification that unblocks the item.
Processors often confuse file age with condition age. A loan can be twenty days in process while a critical PTD item is only three days old—or the reverse. Aging management focuses on each open condition's clock, not the overall milestone calendar alone.
When those four fields are visible on every open item, aging stops being a gut feel and becomes a queue you can work.
Most shops already track application-to-close and underwriting turn times. Fewer track how long individual conditions may sit before someone must escalate. That gap is where good files quietly stall.
Condition SLAs do not need to be punitive. They are service levels for the processor desk: how long a document chase, third-party order, or underwriting clarification should remain without a next step. Soft SLAs drive follow-up. Hard SLAs drive escalation to the LO, LOA, or operations lead.
Pick numbers that match your channel mix and volume. The point is consistency: every open condition should have an expected age ceiling and an owner who owns the clock.
Spreadsheet tabs and buried LOS filters fail when volume spikes. Processors need a short daily list: what is aging, who owns it, and what the next ask is. Whether you build that list in your LOS, a shared tracker, or a dedicated tool like Conditionly, the structure should stay simple.
Sort by red SLA first, then yellow, then critical-path greens. Do not sort only by loan number. Aging is a risk queue, not an alphabetical one.
Keep the ritual short. Long status meetings recreate the spreadsheet problem inside a calendar invite.
Individual red items are fires. Patterns are process debt. Review aging weekly by condition type and owner.
Processors who share a one-page aging pattern summary with ops leads get staffing and template fixes. Processors who only escalate single files get temporary relief and the same red list next Monday.
Aging tools only help if the desk has a standard response. Use a light playbook so every processor escalates the same way.
Never reset aging because someone "looked at" the file. Reset only when the next action completed or the condition was legitimately reissued with new criteria.
Condition aging fails when everyone assumes someone else is chasing. Agree on a simple split:
Loan officers do not need a forty-column tracker. They need a short list of aging risks on their pipeline—especially items that threaten locks or closing dates. Push that summary daily or when an item turns yellow so LOs are never surprised at CTC.
Teams that already use Conditionly for loan condition tracking can treat aging and SLA status as part of the same daily queue—so processors see what is stalling without rebuilding the report by hand each morning.
Once a week, spend fifteen minutes on desk-level health—not loan-level firefighting:
That rhythm turns aging from a scramble into an operating habit. Files still hit surprises—borrowers change jobs, insurance carriers stall—but the desk stops discovering those surprises only after the SLA (or the lock) is already gone.
Loan condition aging is the quiet predictor of delayed closings. Define what "aged" means, put SLAs on condition types that matter, work a short daily risk queue, and escalate yellow and red items with a shared processor–LO playbook. Do that consistently and you clear more conditions while they are still cheap to fix—before they become lock extensions, suspense loops, or closing-week chaos.
If your desk is still reconstructing open conditions from inboxes and spreadsheets, a focused condition-tracking workflow—whether you build it internally or use a purpose-built tool like Conditionly—makes aging visible enough to manage. Start with the red list tomorrow morning. The SLA you protect is the closing you keep.
