Run a Condition Clearing Queue: scope and evidence
Run a Condition Clearing Queue starts with a written boundary. Name the loan, the source, the owner, the evidence, and the point where the work must stop. A clear rule keeps coordination separate from lending and credit decisions.
The main risk is that a condition can be marked cleared without the supporting evidence. Record the source and time before changing a status.
Capture the evidence
A usable record includes loan, condition, source, owner, due date, evidence, and status. Keep the source beside the record so another reviewer can reconstruct what happened.
The processing lead confirms the decision or exception. The coordinator can track conditions, check evidence, and route exceptions, but should not fill a gap with an assumption.
Separate preparation from judgment
Decisions about underwriting and lending decisions remain with the authorized owner. Use three labels: proceed under the rule, pause for missing evidence, and escalate for a decision.
Run the review
Review open conditions, age, and missing evidence. For example, a condition is cleared by a borrower email. Record what evidence was available and who owned the next step.
Pilot one workflow
Start with one condition type. Test the checklist on a small batch and review exceptions with the owner.
Use the related service scope and pipeline guide for context. Review CFPB mortgage guidance before changing a workflow.