Skip to content

Fannie Mae D1-3 post-closing QC workflow

D1-3 is best implemented as a process with evidence, ownership, and timing—not as a static PDF checklist copied into a shared drive.

What this guidance should change

Translate the written plan

Document sets, sampling parameters, channel splits, reviewer authority, severity definitions, escalation, and reporting cadence should be explicit organization controls.

Keep calculation and judgment separate

A rules engine can identify a missing document or date variance. The reviewer determines whether source evidence cures it, whether it is a defect, and what corrective action follows.

Reverification is external evidence

A generated letter is only a request. ExactClose distinguishes pending, requested, received, verified, exception, and waived states so a workflow step cannot masquerade as a result.

Translate the written plan

Document sets, sampling parameters, channel splits, reviewer authority, severity definitions, escalation, and reporting cadence should be explicit organization controls.

Keep calculation and judgment separate

A rules engine can identify a missing document or date variance. The reviewer determines whether source evidence cures it, whether it is a defect, and what corrective action follows.

Reverification is external evidence

A generated letter is only a request. ExactClose distinguishes pending, requested, received, verified, exception, and waived states so a workflow step cannot masquerade as a result.

How to evaluate this workflow

Software can operationalize a lender-approved Fannie Mae QC plan, but the guide and the institution's current plan remain authoritative. Evaluate whether the system makes review scope, sampling, source evidence, reverification, findings, corrective action, and reporting observable without turning policy judgment into an opaque model output.

Buying criteria

  • Map configured controls to the approved QC plan
  • Retain current primary-source references
  • Distinguish a generated request from completed reverification
  • Version rules and report snapshots

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.

Run five reviews free See exact pricing