Short answer
A condition tracking SOP should define how new conditions are captured, who owns each item, when follow-up happens, what counts as stale, and when the file escalates to a senior processor. The SOP must also distinguish tracking work from underwriting judgment: support can organize and follow up, but your firm controls interpretation and final response.
What the SOP should control
The SOP should control the repeatable parts of condition management: capture, ownership, status, follow-up timing, and escalation. It should not pretend that every condition is simple. Some items require judgment, investor context, or a conversation with the broker or lender.
Common failure modes
- Condition lists are copied into notes without owners.
- Aging is reviewed only when a closing date gets close.
- Support staff update status without a clear QA check.
- Borrower and third-party blockers are mixed together.
- The founder becomes the only person who knows which items are urgent.
What to measure
Measure open conditions by age, stale conditions by owner, time from condition receipt to first action, conditions waiting on third parties, and number of senior escalations. These numbers help the owner see whether the issue is volume, training, process clarity, or a specific client workflow.
How Mithras supports condition tracking
Mithras can maintain trackers, prepare follow-up queues, organize supporting documents, and flag exceptions for review. The firm keeps final control over interpretation, lender communication rules, and any judgment-sensitive decision.
Workflow map
Condition capture
Record condition text, source, date, file, owner, and due signal.
Owner assignment
Separate borrower, broker, processor, lender, and third-party ownership.
Aging review
Review stale conditions before they create surprise closing pressure.
QA before update
Check notes, attachments, and escalation flags before status changes.
Practical checklist
- Capture conditions in a shared tracker within your required review window.
- Assign every item to a real owner and next action.
- Tag conditions that require senior interpretation.
- Review aging items on a fixed cadence.
- Require QA before lender portal updates or client-facing summaries.
Sources
About the writer
Priya Shah
QA and Workflow Systems Writer
Priya writes about QA checklists, condition tracking, escalation rules, and human-reviewed automation in mortgage processing.
Read more from Priya ShahFAQ
Can condition tracking be outsourced?
The tracking and follow-up preparation can often be supported, but interpretation and final QA should remain under your firm's control.
What makes a condition stale?
Each firm should define this by workflow, but stale usually means no clear owner, no next action, or no recent follow-up inside the expected cadence.
Should every condition have the same cadence?
No. Borrower documents, third-party items, and lender clarifications often need different follow-up and escalation rules.
Related insights
A mortgage processing QA checklist for condition updates
A field-level QA checklist processing firms can use before condition updates reach a lender portal, broker summary, or internal status report.
How to build a missing-doc tracker for mortgage processing
A practical missing-document tracking structure for small processing teams that want cleaner follow-up without losing borrower or broker visibility.
How lender portal updates create hidden processing workload
Why portal updates, LOS notes, email summaries, and tracker cleanup quietly consume capacity inside small mortgage processing firms.
Start with the workflow, not a generic pitch.
Tell us where files are getting stuck. We will look for one narrow place Mithras can help without taking control away from your team.
Start with one workflow