Skip to content

Mortgage reverification workflow for post-closing QC

A reverification request is not a result. A defensible post-closing QC workflow separates the request, delivery evidence, response, reviewer conclusion, exception, and any approved waiver so no generated letter can be mistaken for independent verification.

What this guidance should change

Define the worklist from the QC plan

Start with the current written plan and controlling investor or agency requirements. Define which reverifications apply by product, channel, evidence type, and exception rather than creating the same generic task list for every loan.

Preserve the request

Record the verifier, requested evidence, request date, secure delivery method, due date, and the exact letter or payload sent. A request letter should be immutable after issuance; corrections should create a new version.

Keep status precise

Use distinct states for pending, requested, received, verified, exception, and waived. Each state needs an owner, timestamp, and source. 'Sent' or 'complete' alone hides whether third-party evidence was actually received and evaluated.

Define the worklist from the QC plan

Start with the current written plan and controlling investor or agency requirements. Define which reverifications apply by product, channel, evidence type, and exception rather than creating the same generic task list for every loan.

Preserve the request

Record the verifier, requested evidence, request date, secure delivery method, due date, and the exact letter or payload sent. A request letter should be immutable after issuance; corrections should create a new version.

Keep status precise

Use distinct states for pending, requested, received, verified, exception, and waived. Each state needs an owner, timestamp, and source. 'Sent' or 'complete' alone hides whether third-party evidence was actually received and evaluated.

Connect the result to disposition

Attach the response to the loan record, identify the compared source fact, and record the qualified reviewer's conclusion. Exceptions should flow into defect management and corrective action rather than disappear inside a task comment.

Put this guidance into a controlled operating record.

Translate each requirement or method into a named control with an owner, effective date, scope, required inputs, acceptable evidence, review authority, exception path, and retained output. Link the configured control to the current primary source or approved policy instead of copying a sentence into a checklist with no change history.

Test the workflow with one complete cycle. Another qualified reviewer should be able to identify the eligible population, reproduce the sample or calculation, open the cited evidence, understand the response and rationale, see who approved the disposition, and verify how the result reached corrective action and management reporting.

Guidance, software, and automation do not decide legal applicability or replace agency, investor, institutional, or counsel judgment. Record the source review date, monitor changes, version the control, and preserve which rule and evidence state produced every report.

Why this page exists

Keep decisions human and evidence explicit.

Practical guidance tied to the review evidence a lender needs to preserve.

Primary references

Confirm requirements against current source material.

Requirements and vendor capabilities change. These sources were reviewed July 31, 2026. Confirm current source material, product scope, commercial terms, and your approved QC plan before changing a production process.

From evidence to conclusion

Put the guidance inside a complete review record.

Run five post-close reviews with the source evidence, calculations, dispositions, and reporting kept together.

Contact the team See exact pricing